![]() ![]() It’s always a good idea to test the remote desktop connection while you still have access to the remote computer to make sure there are no unexpected hitches. Once you enter the password or approve the connection, you can begin working on the remote desktop. (Image credit: Ubuntu)Īt this point, you’ll either be prompted for a password on your control computer or with a notification on the remote desktop, depending on how you configured the screen sharing settings. To connect to a remote desktop, open Remmina, select VNC, and enter the IP address of the remote computer. Then click on the Screen Sharing button that appears below to configure the screen sharing options. ![]() You can turn it on by clicking the On/Off toggle at the top of the window. Then navigate to the Sharing tab in the left-hand menu in the system settings.īy default, screen sharing is turned off on Ubuntu. Open the system settings window by clicking on the tools icon in the top right corner of the screen. The first thing you need to do is to enable remote desktop sharing on Ubuntu. That is beyond the scope of this guide, as it requires modifying the remote desktop network’s firewall settings. ![]() If you’re on a different network, you’ll need to set up port forwarding. You will need to be on the same local area network as the remote computer when connecting to a remote desktop using this IP address. You can find the IP address by right-clicking on the network icon in the upper right corner of the desktop and selecting Connection Information. Note that you’ll also need the IP address of the computer you want to connect to remotely. Remmina will install all required packages for you to use the remote desktop software. Somehow this setup does not like resizing, therefore I forced a single size by setting DEFAULT_SIZES_XORG to "1920x1080".Installing Remmina on Ubuntu. With the nvidia driver: 'Section "Device"\n' ' Identifier "Chrome Remote Desktop Videocard"\n' Replace the dummy driver: 'Section "Device"\n' We are doing all this so that we can use the nvidia drivers. To "-config", os.path.basename(config_file.name)Īnd because we are not root we must give users write permission to this folder. X wants to receive a relative path so we have to change "-config", config_file.name Add the following line between the prefix and suffix line: dir="/etc/X11/", Suffix=".conf", delete=False) as config_file:Ĭonfig_file.write(gen_xorg_config(self.sizes).encode())Īt this moment the config file is created in /tmp, so let's move that. Looking through the sourcecode of /opt/google/chrome-remote-desktop/chrome-remote-desktop we see the following: with tempfile.NamedTemporaryFile( This page explains that the config file must be placed in /etc/X11/ or /usr/etc/X11/. Now X server is complaning that the -config must be a relative path. If you are like me and don't care about logging you can edit /opt/google/chrome-remote-desktop/chrome-remote-desktop and remove the following line (around line number 581): "-logfile", "/dev/null", Now X server is complaining that the -logfile is only available when the server is run as root (i.e, with real-uid 0). To fix above error you can edit /etc/X11/nfig and set allowed_users = anybody. Why is X server not started by root? Because the chrome-remote-desktop service starts a separate display for each user in the name of that user. Let's enable it by adding the following line to the /etc/environment file: CHROME_REMOTE_DESKTOP_USE_XORG=1Īfter restarting the service I got the following error Only console users are allowed to run the X server In there we find that we can use the CHROME_REMOTE_DESKTOP_USE_XORG environment variable to make google-remote-desktop launch an Xorg display with the dummy driver. The code behind the chrome-remote-desktop service is in /etc/init.d/chrome-remote-desktop, which in turn runs /opt/google/chrome-remote-desktop/chrome-remote-desktop ( sourcecode). So let's see if we can make google-remote-desktop make use a normal x server (spoiler: yes!). This showed that the current display was started using xvfb. This lead me to this question and this command: ps -ef | grep X. If the X11 server associated with dpy does not own display, or if permission to access it has already been acquired by another entity, the call must return the error code VK_ERROR_INITIALIZATION_FAILED. It all started with this page that tells us I do not reccommand this for sensitive systems I figured out a way to get it to work but it is pretty hacky. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |