The version distributed by google is retained in /opt/ too as chrome-remote-desktop.verbatim.A mirror of this script is also maintained at /usr/local/bin/chrome-remote-desktop.github, and will let the user know if there are updates.

This version keeps a persistent version itself in /usr/local/bin/ in addition updating the one executed by Chrome in /opt/google/chrome-remote-desktop/.We are primarily just enforcing the use of existing instances of X and correct display values as reported by your system. odd scaling issues or flaky resolution changes.the remote desktop environment crashes or becomes mangled.none of the X sessions work, each immediately closing the connection to the client.The trouble comes when you are trying to remote in- some problems you may encounter include:

deb download with dpkg, set up a PIN, etc. Set up everything normally- install Google’s. the “server”, the client machine should not be installing anything, all it needs is a web browser).īefore patching anything or pursuing other forms of delightful tomfoolery, follow the installation instructions provided by Google. This stuff is only relevant for accessing your Ubuntu machine from elsewhere (e.g. This chrome-remote-desktop script extends and replaces the version automatically installed by Google in /opt/google/chrome-remote-desktop/chrome-remote-desktop. Fully automated patching for Chrome Remote Desktop on Ubuntu Budgie.Ĭhrome remote desktop is fantastic, but often clashes with Xorg nuances from a variety of desktop environments in Ubuntu. here’s the readme below, the repo is over here on Github if you’re keen. Thought I’d share my solution here, just in case this has been irksome to anyone else. Hey y’all, not sure if anyone else uses chrome remote-Īs distributed, it usually doesn’t work well (if at all) with Budgie and some other Ubuntu environments.

Chrome remote desktop ubuntu