Chrome-remote desktop manjaro

I have a problem with setting up this package.

After installation and running crd --setup the webapp shows me to "set up remote access". However when I try to do it I get No response received to getCredentialsFromAuthCode message after 30000 milliseconds. [tried that multiple times while doing other steps described below].

I did change the exec command [I'm using KDE Plasma on Manjaro] to exec /usr/share/sddm/scripts/Xsession "/usr/bin/startkde" and Size file to my resolution [1920x1080].

I'm not sure if I should set the webapp first or start the service. While starting the service I get:

chrome-remote-desktop.service - "Chrome Remote Desktop host daemon" Loaded: loaded [/usr/lib/systemd/user/chrome-remote-desktop.service; disabled; vendor preset: enabled] Active: inactive [dead] Sep 10 10:31:23 BARTOSZ-PC3 systemd[976]: Started "Chrome Remote Desktop host daemon". Sep 10 10:38:19 BARTOSZ-PC3 systemd[976]: Starting "Chrome Remote Desktop host daemon"... Sep 10 10:38:19 BARTOSZ-PC3 crd[61840]: [0910/103819.694222:INFO:remoting_user_session.cc[691]] Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20190910_1> Sep 10 10:38:19 BARTOSZ-PC3 user-session[61851]: pam_unix[chrome-remote-desktop:session]: session opened for user baatochan by [uid=1000] Sep 10 10:38:19 BARTOSZ-PC3 crd[61840]: [0910/103819.698337:WARNING:remoting_user_session.cc[613]] Failed to read from message pipe. Please check log to determine host status. Sep 10 10:38:19 BARTOSZ-PC3 crd[61840]: Log file: /tmp/chrome_remote_desktop_20190910_103819_okEMcp Sep 10 10:38:19 BARTOSZ-PC3 user-session[61851]: pam_unix[chrome-remote-desktop:session]: session closed for user baatochan Sep 10 10:38:19 BARTOSZ-PC3 crd[61853]: The daemon is not currently running Sep 10 10:38:19 BARTOSZ-PC3 systemd[976]: chrome-remote-desktop.service: Succeeded. Sep 10 10:38:19 BARTOSZ-PC3 systemd[976]: Started "Chrome Remote Desktop host daemon".

And the log contains one line:

[0910/103819.698360:WARNING:remoting_user_session.cc[467]] Child terminated by signal 5

When running it with crd --start I get:

[0910/104319.642341:INFO:remoting_user_session.cc[691]] Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20190910_104319_Im0hKu' [0910/104319.646161:WARNING:remoting_user_session.cc[613]] Failed to read from message pipe. Please check log to determine host status. Log file: /tmp/chrome_remote_desktop_20190910_104319_Im0hKu

and the log contains the same message.

Reading the comments here I checked the pam.d dir and there is the correct file created by the "installer".

Tbh don't know what to do now to move on with the set-up and I would be really grateful if someone could help me.

I updated my graphics card to nvidia, and updated GDM, gnome. I followed the post to use display :0 as my chrome-remote-desktop and it worked fine. but when I recently tried it, again I started seeing errors like this, can someone help

2018-09-08 23:47:04,227:INFO:Using host_id: 529e63f8-0684-5932-d0a4-5bfa5866cf66 2018-09-08 23:47:04,228:INFO:Launching X server and X session. 2018-09-08 23:47:04,244:INFO:X server is active. 2018-09-08 23:47:04,623:INFO:Launching X session: ['/bin/sh', '/home/xyz/.chrome-remote-desktop-session'] 2018-09-08 23:47:04,625:INFO:Launching host process 2018-09-08 23:47:04,625:INFO:['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/xyz/.config/chrome-remote-desktop/pulseaudio#20383fe03b/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.xyz.ssh_auth_sock', '--signal-parent'] 2018-09-08 23:47:04,627:INFO:wait[] returned [6740,0] 2018-09-08 23:47:04,627:INFO:Session process terminated 2018-09-08 23:47:04,640:INFO:Failure count for 'session' is now 1 2018-09-08 23:47:04,640:INFO:Terminating host 2018-09-08 23:47:04,641:INFO:Failure count for 'X server' is now 0 2018-09-08 23:47:04,641:INFO:Failure count for 'host' is now 0 2018-09-08 23:47:04,641:INFO:Waiting before relaunching 2018-09-08 23:47:06,643:INFO:wait[] returned [6739,0] 2018-09-08 23:47:06,644:INFO:Waiting before relaunching 2018-09-08 23:47:09,630:INFO:Launching X server and X session. Traceback [most recent call last]: File "/usr/lib/python2.7/logging/__init__.py", line 892, in emit self.flush[] File "/usr/lib/python2.7/logging/__init__.py", line 852, in flush self.stream.flush[] IOError: [Errno 32] Broken pipe Logged from file chrome-remote-desktop, line 1685 2018-09-08 23:47:09,648:INFO:X server is active. Traceback [most recent call last]: File "/usr/lib/python2.7/logging/__init__.py", line 892, in emit self.flush[] File "/usr/lib/python2.7/logging/__init__.py", line 852, in flush self.stream.flush[] IOError: [Errno 32] Broken pipe Logged from file chrome-remote-desktop, line 534 2018-09-08 23:47:09,798:INFO:Launching X session: ['/bin/sh', '/home/xyz/.chrome-remote-desktop-session'] Traceback [most recent call last]: File "/usr/lib/python2.7/logging/__init__.py", line 892, in emit self.flush[] File "/usr/lib/python2.7/logging/__init__.py", line 852, in flush self.stream.flush[] IOError: [Errno 32] Broken pipe Logged from file chrome-remote-desktop, line 705 2018-09-08 23:47:09,800:INFO:Launching host process Traceback [most recent call last]: File "/usr/lib/python2.7/logging/__init__.py", line 892, in emit self.flush[] File "/usr/lib/python2.7/logging/__init__.py", line 852, in flush self.stream.flush[] IOError: [Errno 32] Broken pipe Logged from file chrome-remote-desktop, line 1692 2018-09-08 23:47:09,800:INFO:['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/xyz/.config/chrome-remote-desktop/pulseaudio#20383fe03b/fifo_output', '--server-supports-exact-resize', '--ssh-auth-sockname=/tmp/chromoting.xyz.ssh_auth_sock', '--signal-parent']

This package is not working in GNOME 3.28. I followed the instruction of this post but it is still not working.

Here's the config of .chrome-remote-desktop-session:

export $[dbus-launch] # exec classic gnome-session --session gnome-classic exec gnome-session # exec gnome-session

Here's the output of crd --start:

Seems like you haven't activated CRD in your browser. Please do that before trying to run the server.

Here's the output of crd --restart:

The daemon is not currently running [0604/203645.811960:INFO:remoting_user_session.cc[688]] Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20180604_203645_zOair2' Cleanup. Log file: /tmp/chrome_remote_desktop_20180604_203645_zOair2

The log file /tmp/chrome_remote_desktop_20180604_203645_zOair2 says that:

Failed to load config: [Errno 2] No such file or directory: '/home/hzxie/.config/chrome-remote-desktop/host#.json' 2018-06-04 20:36:45,947:INFO:Cleanup. [0604/203645.952871:WARNING:remoting_user_session.cc[464]] Child exited with status 1

Here's the output of systemctl status --user chrome-remote-desktop:

chrome-remote-desktop.service - "Chrome Remote Desktop host daemon" Loaded: loaded [/usr/lib/systemd/user/chrome-remote-desktop.service; enabled; vendor preset: enabled] Active: inactive [dead] Condition: start condition failed at Mon 2018-06-04 20:25:07 CST; 8min ago ConditionPathExistsGlob=/home/hzxie/.config/chrome-remote-desktop/host#*.json was not met

I also tried to Enable Remote Connection from the Chrome application, but I got the following message after setting 6-digit PIN:

Enabling remote connections for this computer...

After about 20 min it finally timed out and I got this:

Failed to start remote access service.

Who can help me out? Thank you so much!

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: [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: [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 //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: /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.

@caleb You might have a good argument, but I still think that you can deal with the extra dependency of using nano than others dealing with vi. It's one thing to have to face an editor that is prehistoric to most users, it's another to expect them how to find out how to use it during a complex install, or interrupt the install to sort out the editor. ETA: Ok, if and when I get around to it [probably on the next update], I'll try and remember to include an option to select between nano and the default editor. But understand that I'm not putting a high priority on this. ETA2: Ok I've re-reconsidered, and the answer is still no. Nano is in the core, so it should be in any arch installation unless someone actually decides to uninstall it for whatever reason. Including it as a dependency is more of a fail-safe than anything. The argument as to what "anybody running arch" is a really big assumption on your part, or did you take a survey? It is possible to install and run arch without thinking about or needing to change the $EDITOR or $VISUAL variables on a permanent basis. "Knowing roughly what's going on" isn't enough to use vi, and certainly not while installing a complex piece of software. Adding an option to change the editor would add more unnecessary complexity. The only reason vi is the default editor in Arch or any other distro I know of is probably because it's POSIX standard, which has no relevance here at all and doesn't bind anyone else to anything. Most text installers including Linux distros themselves that require editing use something other than vi because vi is a pig to use if you don't already use it as your standard editor on a regular basis. The advantages of usability for more unsophisticated Arch users and I've aimed this package so anyone can install it with a minimum of trouble, otherwise I wouldn't have bothered with the .install and CRD scripts far outweigh any actual advantages there might be [I can't think of any] of effectively leaving it at vi. If you can provide any real benefits from using the $EDITOR/$VISUAL or real disadvantages in requiring nano, I'd be more than willing to reconsider. Until then, my decision to use nano is final.

If you're getting that error message, it's because you haven't yet enabled CRD access to the internet in your browser. Which is a bit like trying to print something without switching the printer on. The server will then obviously not run, and will return that message. As I said before, if you're happy enabling and disabling CRD in the browser to start or kill the server, please, do that. It's probably even somewhat more secure than using the crd method or "systemctl --user start...", but I doubt the added security makes up for the inconvenience [and potential problems with screen res, pulse... etc.], at least for me. But as always, your installation, your machine, your scenario, you do whatever you want with it. "systemctl --user enable chrome-remote-desktop" starts the server at login. That's good if your host machine is only intended for use as a server without other peripherals attached, such as a server you have running on its own in the basement. Run as a desktop, you will run into conflicts with single-instance processes running in the server session but not in the desktop session. You can also call "crd --start" from start-up in your session manager with the exact same effect. "systemctl --user start chrome-remote-desktop" calls the Google chrome-remote-desktop script in the /opt directory in a very roundabout way, but does exactly the same thing as "crd --start", only "crd --start" gives you additional benefits [the pulse mess, screen resolution] that I didn't want to include in the systemd service. Simply typing "crd [--start]" is a little easier than typing out "systemctl --user start chrome-remote-desktop" or enabling connections to the internet from the browser every time you want to start the server, wouldn't you agree? Especially if you have to go somewhere with a client machine and just want to fire up the server before you leave, which is my usual usage scenario. There is no "always have to" in this. Please just use it whichever way you want, whatever suits your usage scenario. Are there any actual questions, recommendations or improvements you would like to put forward to me? I'm not sure where you're trying to go with this.

@Paviluf, That's all you need to get it set up and running initially, but how you continue using the Chrome Remote Desktop server depends entirely on how you want to use it. I can't speak for anyone else, but I only have the server running when I know I'll need it. Ok I suppose you can also allow and disallow the server in Chrome or Chromium every time you want to switch the server on or off, but that has its own problems your preferred screen resolution for the client might be ignored, and old pulse config files probably won't work [though I don't know, that might have been fixed since I wrote the crd script]. And possibly other problems, I don't know, I haven't tried using it like that. I just find it more convenient just to use the crd script, which is why I wrote it. Chrome Remote Desktop isn't like most applications that you run while sitting in front of the machine you're running the application on. This involves inherent and potentially serious security risks that neither Google nor anyone else can avoid, and only the user can mitigate. I can't predict all possible usage scenarios, much less test them. So if you find that ignoring crd and crd --start works for you, that's great, use it that way, but I can't tell you whether you'll be happy with that particular use or not. To avoid confusion, I only wrote the crd script, the package itself is from Google and was written for Ubuntu. I only repackaged it for Arch.

In order to get it working: 1. I manually created the chrome-remote-desktop group, and added myself to it. 2. I manually created the ~/.chrome-remote-desktop-session file with "exec startxfce4" in it. 3. I manually created the ~/.config/chrome-remote-desktop directory. 4. I manually changed the symlink for chromium using: "ln -s /etc/opt/chrome/native-messaging-hosts/ /etc/chromium" [@ishitatsuyuki is right] Also, I never used systemctl to start or enable the chrome-remote-desktop service; if I am not mistaken, the extension is supposed to invoke the python script. After all that, I was able to get it to show the "Enable remote connections" button. Clicking that button generates the host json file in ~/.config/chrome-remote-desktop. Now, connecting from another computer successfully starts xfce. But it starts it on :20, not :0, which I guess is expected, since the python script tries to get "a candidate display number for which there is currently no x server lock file". Although, it logs in using my user, chromium within the remote connection uses a blank profile, which gets created in ~/.config/chrome-remote-desktop/chrome-profile. I haven't tried to symlink that to ~/.config/chromium because the python script suggests to sign in and sync. I am not sure why remote assistance is allowed to use :0 while remote desktop needs to use :20... Perhaps package maintainer can fix the symlink and the groupadd.

Video liên quan