2/18/2023 0 Comments Chrome remote desktop not working> Downloading chrome-remote-desktop-.16.deb. => Making package: chrome-remote-desktop. Generating chrome-remote-desktop information. Installing xorg-server-xvfb (1.20.13-3).Ī restart is required for the changes to take effect.Ĭloning chrome-remote-desktop build files. Getting 404 issues when updating/installing the package again Preparing.Ĭhecking chrome-remote-desktop dependencies.ĭownload of xorg-server-xvfb (1.20.13-3) startedĭownload of xorg-server-xvfb (1.20.13-3) finished It in the browser window in default resolution.įor a more pleasant chromoting experience, just issue the command: crd -restart To do that, open in your chrome or chromium browserĪnd follow the instructions. To act as a server for this to work at all. Please remember that you will need to allow Chrome or Chromium Now entering the editor to make the appropriate changes to If you dont want a default size please leave it blank. Remember that this will affect all clients you use. home/corey/.config/chrome-remote-desktop/Size. Value with format x (e.g 1360x768) in file If you want to set a default size for all clients, please add a Now entering the editor to make the appropriate changes to your session file. home/corey/.chrome-remote-desktop-session That would be /home/corey/.config/chrome-remote-desktop and Disabling the PIN feature and reinstalling Chrome and the Remote Desktop app seems to have fixed the issue for many. Try running: crd -setup.``Īnd this is my log password for corey:Īdding user corey to group chrome-remote-desktopĬhecking that working directory and session file are present The Chrome Remote Desktop not working issue can occur due to a glitch in Chrome or the Remote Desktop app, an issue with the PIN feature, or even permission issues. I couldn't find the service rvice`` and when I ran/usr/bin/crd -start I get this messageSeems like you haven't set this up yet. Back in 2015, ChromeRDP was as simple as one-click install on Linux and it never gave me a single issue.Chrome remote desktop still thinks I haven't installed it even tho I have and has the extension installed on the Chrome. Unfortunately, you missed the easiest RDP software that ever existed by about 6 years. I wish I could be more help and I realize that this is not much of an answer, but I hope that explaining my struggles and how ChromeRDP finally broke completely (every successive update to date has made ChromeRDP more and more buggy on Linux) might help. Therefore, it is always a first helpful measure to. To date, I have yet to find any other suitable no-port-forwarding alternative RDP software. The Linux version of chrome remote desktop (henceforth, CRD) doesnt allow clients to connect and control an existing X session rather, there is a dedicated X. After updating the operating system or updating Chrome Remote Desktop, these changes can cause problems. it's a laptop), then (as far as I can tell) you're SOL. So, the solution is to just port forward. Anyway, I had countless issues with ChromeRDP prior to it breaking completely, including random disconnects, broken x sessions, freezing up the x session, black unusable desktop, randomly stopping working, the computer suddenly disappearing from the list of connectable computers, etc. Then, I gave up on ChromeRDP because it appears there is no solution to the problem (at least none I could devise). I'm running a server, so I can't open x to all local users, so I tried for an hour to find a fix to no avail. I patched it to make it connect to the existing physical screen, which worked previously (before the update), but it doesn't work now due to (what appears to be) xauthority issues. And finally, I have stumbled at the step usermod -a -G chrome-remote-desktop "$USER" of the mentioned thread Can't Configure Chrome Remote Desktop for it returns usermod: group 'chrome-remote-desktop' does not exist and I do not understand whether it is important (but it looks like logging does not work without this step).įor me, Chrome Remote Desktop recently updated and I was unable to start a xsession due to errors. Unfortunately, it has been just a part of the problem, CRD still fails to run. It helped me to actually start the service. So, I followed the second answer (again, not the accepted one) of. not running.Įxecuting sudo systemctl unmask rvice changed nothing. I executed service chrome-remote-desktop status and realised the CRD service was masked, i. I found an informative answer on how to start investigating the issue in the thread Can't Configure Chrome Remote Desktop (it is not the accepted answer, but the second one). Did not change a thing.Īlso, I tried to uninstall it with dpkg -purge. I found this advice: How can I "Turn On" Chrome remote desktop in Ubuntu 20.04?. exactly the same deb-file (this time with GUI tools: Qapt or Discover). Should I click the blue button it initiates downloading and installing. Then I launched it only to get this screen: After adding a couple of required dependencies it has set up smoothly. I need to be able to connect to computer running Lubuntu 20.04 with Chrome remote desktop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |