Setting up remote desktop for ubuntu install#
NX> 700 Install log is: /usr/NX/var/log/nxinstall.log. NX> 700 Using installation profile: Ubuntu. NX> 700 Installing: nxclient version: 6.9.2. Preparing to unpack nomachine_6.9.2_1_b … (Reading database … 168607 files and directories currently installed.) You’ll see the output like this Selecting previously unselected package nomachine. wget Īfter the file downloaded, install it by typing sudo dpkg -i nomachine_6.9.2_1_b
Setting up remote desktop for ubuntu download#
You can also run the following command to download it as I’m doing from CLI. deb package for Ubuntu, So download it from their official website. After this, the session will automatically start on boot thanks to the init script, and chrome will have directly launched a session for you just now - so you should now be able to connect through a CRD client.Install wget sudo apt -y install wget Step 2: Download NoMachine Remote Desktop ToolĪs NoMachine remote desktop tool is available in. Under "My Computers", hit "Enable remote connections". Start Chrome, install the "Chrome Remote Desktop" app, run it. Ssh -L 5901:localhost:5901 run your preferred VNC client to connect to localhost:5901. On the client, log into the server using a VNC client over SSH forwarding. # log in remotely and bootstrap chrome (see later) Wherever your shell profile is, add an appropriate resolution selection:Įxport CHROME_REMOTE_DESKTOP_DEFAULT_DESKTOP_SIZES=1024x768 Set up your desired resolution in your shell profile If ~/.chrome-remote-desktop-session is missing or containing bad information, the attempt to connect to the remote desktop will fail without a clear cause. Sudo usermod -a -G chrome-remote-desktop $USER You may need to add yourself to the group (unclear if this happens correctly automatically): Sudo dpkg -i chrome-remote-desktop_current_bĪt the time of this writing, the package installer seems to fail to create the chrome-remote-desktop group, so add it: At least it was good enough to fool me :)ĭownload the package linked from and install it: When originally writing this I thought it was lossy and pixel perfect nonetheless, but I’ve been informed it’s not. I don’t know technical details, but likely their use of some kind of modified VP9 codec has to do with this. It seems faster than any other remote desktop option I have tried. It handles hi-dpi displays correctly, and passes through keyboard combinations correctly (e.g., it stops CTRL-N from opening a new local window). It works natively on ChromeOS, and works well. Why Chrome Remote Desktop instead of $OTHER_OPTION? It determines which users should have CRD running based on which users are part of the chrome-remote-desktop Unix group. Sudo /etc/init.d/chrome-remote-desktop restart Once set up however, CRD is completely headless and is controlled using an init script. Initial setup still requires a non-headless environment: A running Chrome (until someone or Google makes a tool that generates the necessary on-disk state in your home directory for authorizing remote access). If it is running, you are connected to the in-progress session. When you connect, a session is started if one is not already running. This is similar to the classic vncserver mechanic. The Linux version of chrome remote desktop (henceforth, CRD) doesn’t allow clients to connect and control an existing X session rather, there is a dedicated X session specific to CRD. This documentation (under "Enable remote access to your computer"): The two main sources of information I found are:Īn old product forum post: !topic/chrome/8PMxG69VJ6o The upstream documentation is a little bit scattered, not always entirely complete, and the Ubuntu package provided needs some poking to work. Setting up Chrome Remote Desktop on Ubuntu # Originally posted by `scode` at no longer available.
0 kommentar(er)
