Arch Linux User Repository

I maintain the latest built package at:

https://github.com/frealgagu/archlinux.chrome-remote-desktop/releases/

Thanks @frealgagu for packaging this, @nightuser for the existing session patch and @Brinsky for the instructions.

I've compiled both instructions with screenshots and added it to my blog if anyone is having issues with the install. Otherwise, just follow the instructions in the comments by @Brinsky from 2019-12-06 13:58.

Here's how I got this working with the new web app (remotedesktop.google.com):

1. Build and install the package
2. run crd --setup
3. (Optional) Configure execution of your preferred window manager in ~/.chrome-remote-desktop-session
4. Go to http://remotedesktop.google.com/headless
5. Click "next" and "authorize" through each instruction
6. Copy/paste and run the provided "Debian" command, which should look like the following: DISPLAY= /opt/google/chrome-remote-desktop/start-host --code="<UNIQUE_CODE>" --redirect-url="<https://remotedesktop.google.com/_/oauthredirect>" --name=
7. Set up a name and PIN
8. Wait for successful output containing "Host ready to receive connections."
9. Run crd --start

Thanks @Bittersourness!

If anyone is having trouble with dbus and KDE with a message like this (FYI @grayjoc): dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead startkde: Could not sync environment to dbus. You have to add "export $(dbus-launch)" before startkde in ~/.chrome-remote-desktop-session: # You will have to uncomment one of the following lines for CRD to work # Remove the # and select ctrl-X to finish. # export $(dbus-launch) exec /usr/bin/startkde # exec /usr/bin/openbox-session # exec /usr/bin/openbox-kde-session And that's it, you will see your desktop like a boss! :D

Appears to have 404d as of today.

There is a missing dependency: xorg-xrandr. Without it, I got the following error: xdpyinfo: unable to open display ":20". After installing it via pacman, CRD works for me.

@dgerdem There could be any number of reasons for that, CRD is gnarly and not at all easy to set up. I doubt dbus is the actual problem as it usually catches all the problems that go before it. Check that your firewall isn't blocking it, check that your host system is allowing connections, see whether it works on another client, such as a Chrome/Chromium instance on the host system itself... Sorry I can only offer the general advice you've probably tried ten times already.

I'm kind of new to the Arch world. I'm trying to CRD working to enable remote access to my newly installed, up to date Manjaro installation. I got CRD installed, registered with my google account. Once CRD is started and I attempt to connect to it from an android phone, I get a black screen on the phone with a message box saying "Unable to contact settings server. Failed to connect to socket /tmp/dbus-(random letters): connection refused. Once I close that, it says unable to load failsafe session. I pasted the log below. Above the stunport.cc messages in the full log, it shows that the service is ready to accept connections, and it shows my connection attempt. Thanks! [0321/212425.631805:WARNING:stunport.cc(385)] Jingle:Port[0x30e97e530800::0:0:stun:Net[enp3s0:2600:8803:8403:x:x:x:x:x/64:Unknown]]: StunPort: stun host lookup received error 0 [0321/212425.636820:WARNING:stunport.cc(385)] Jingle:Port[0x30e97e530800::0:0:stun:Net[enp3s0:2600:8803:8403:x:x:x:x:x/64:Unknown]]: StunPort: stun host lookup received error 0 [0321/212425.639156:WARNING:stunport.cc(385)] Jingle:Port[0x30e97e6dac00::0:0:stun:Net[enp3s0:2600:8803:8403:x:x:x:x:x/64:Unknown]]: StunPort: stun host lookup received error 0 [0321/212425.664385:WARNING:basicportallocator.cc(724)] Discarding candidate because port is already done gathering. [0321/212425.672509:WARNING:basicportallocator.cc(724)] Discarding candidate because port is already done gathering. (xfce4-session:3741): xfce4-session-CRITICAL **: Unable to contact D-Bus session bus: Failed to connect to socket /tmp/dbus-D8BzAiZun8: Connection refused (xfce4-session:3741): xfce4-session-CRITICAL **: Unable to contact D-Bus session bus: Failed to connect to socket /tmp/dbus-D8BzAiZun8: Connection refused (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_connect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_connect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_connect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_connect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed gpg-agent[3825]: WARNING: "--write-env-file" is an obsolete option - it has no effect gpg-agent: a gpg-agent is already running - not starting a new one (xfce4-session:3741): xfce4-session-WARNING **: gpg-agent returned no PID in the variables (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed (xfce4-session:3741): xfce4-session-WARNING **: xfsm_manager_load_session: Something wrong with /home/admin/.cache/sessions/xfce4-session-AVARICE:20, Does it exist? Permissions issue? (xfce4-session:3741): xfconf-CRITICAL **: xfconf_init() must be called before attempting to use libxfconf! ** (xfce4-session:3741): CRITICAL **: dbus_g_proxy_call: assertion 'DBUS_IS_G_PROXY (proxy)' failed (xfce4-session:3741): GLib-CRITICAL **: g_propagate_error: assertion 'src != NULL' failed 2017-03-21 21:24:32,471:INFO:wait() returned (3733,0) 2017-03-21 21:24:32,471:INFO:Session process terminated 2017-03-21 21:24:32,472:INFO:Terminating X server chrome-remote-desktop-host: Fatal IO error 11 (Resource temporarily unavailable) on X server :20. chrome-remote-desktop-host: Fatal IO error 11 (Resource temporarily unavailable) on X server :20. 2017-03-21 21:24:32,477:INFO:wait() returned (3705,0) 2017-03-21 21:24:32,477:INFO:X server process terminated 2017-03-21 21:24:32,477:INFO:Failure count for 'X server' is now 1 2017-03-21 21:24:32,478:INFO:Launching X server and X session. 2017-03-21 21:24:32,488:INFO:Starting Xvfb on display :20 2017-03-21 21:24:32,536:INFO:X server is active. 2017-03-21 21:24:32,589:INFO:Launching X session: ['/bin/sh', '/home/admin/.chrome-remote-desktop-session'] 2017-03-21 21:24:32,591:INFO:wait() returned (3734,256) 2017-03-21 21:24:32,591:INFO:Host process terminated 2017-03-21 21:24:32,591:INFO:Failure count for 'host' is now 1 2017-03-21 21:24:32,591:INFO:Host exited with status 1. 2017-03-21 21:24:32,592:INFO:Launching host process 2017-03-21 21:24:32,592:INFO:['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/admin/.config/chrome-remote-desktop/pulseaudio#90e20e57fa/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.admin.ssh_auth_sock', '--signal-parent'] /usr/bin/startxfce4: X server already running on display :20 [0321/212432.605764:INFO:remoting_me2me_host.cc(1614)] Starting host process: version 56.0.2924.51 xrdb: "Xft.hinting" on line 19 overrides entry on line 6 xrdb: "Xft.hintstyle" on line 22 overrides entry on line 7 [0321/212432.623156:INFO:remoting_me2me_host.cc(1248)] Policy does not require curtain-mode. [0321/212432.623177:INFO:remoting_me2me_host.cc(1173)] Policy enables NAT traversal. [0321/212432.623187:INFO:remoting_me2me_host.cc(1191)] Policy enables use of relay server. [0321/212432.623193:INFO:remoting_me2me_host.cc(1212)] Policy restricts UDP port range to: <no port range specified> [0321/212432.623201:INFO:remoting_me2me_host.cc(1266)] Policy sets talkgadget prefix: chromoting-host [0321/212432.623211:INFO:remoting_me2me_host.cc(1275)] Policy sets third-party token URLs: <no 3rd party auth config specified> [0321/212432.623218:INFO:remoting_me2me_host.cc(1297)] Policy enables client pairing. [0321/212432.623223:INFO:remoting_me2me_host.cc(1313)] Policy enables security key auth. [0321/212432.623240:INFO:remoting_me2me_host.cc(558)] Processing new host configuration. [0321/212432.737159:INFO:chromoting_host.cc(107)] Starting host [0321/212432.739044:INFO:remoting_me2me_host.cc(1062)] Policy sets host domain: [0321/212432.739050:INFO:remoting_me2me_host.cc(1146)] Policy does not require host username match. [0321/212433.738170:INFO:dns_blackhole_checker.cc(60)] Verifying connection to https://chromoting-host.talkgadget.google.com/talkgadget/oauth/chrome-remote-desktop-host [0321/212433.933210:INFO:dns_blackhole_checker.cc(38)] Successfully connected to host talkgadget. [0321/212433.933236:INFO:signaling_connector.cc(184)] Attempting to connect signaling. [0321/212433.933243:INFO:oauth_token_getter_impl.cc(159)] Refreshing OAuth token. [0321/212434.210045:INFO:oauth_token_getter_impl.cc(55)] Received OAuth token. [0321/212434.210057:INFO:signaling_connector.cc(124)] Received user info. [0321/212434.714752:INFO:signaling_connector.cc(72)] Signaling connected. New JID: 590a80cb4d57f460503b32c6cc0abe0a@chromoting.gserviceaccount.com/chromoting835C7A47 [0321/212434.953906:INFO:remoting_me2me_host.cc(881)] Host ready to receive connections. 2017-03-21 21:24:34,954:INFO:Host ready to receive connections.

@grayjoc Sorry, can't help – I don't use KDE, so I can't test the error

@DaveB Hi, I'm currently experiencing the following errors when starting crd. When I try to connect remotely I get the last error message in an X window "could not sync environment to dbus". ... 2017-03-11 21:20:16,308:INFO:Starting Xvfb on display :20 xdpyinfo: unable to open display ":20". ... [0311/212016.907903:INFO:remoting_me2me_host.cc(558)] Processing new host configuration. startkde: Starting up... dbus-update-activation-environment: error: unable to connect to D-Bus: Using X11 for dbus-daemon autolaunch was disabled at compile time, set your DBUS_SESSION_BUS_ADDRESS instead startkde: Could not sync environment to dbus.

Stupid stupid mistake. Fixed now.

@Bittersourness I'm having the same issue, build works locally but not from AUR. I'm trying to fix it.