Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20180604_203645_zOair2' Here's the output of crd -restart:The daemon is not currently running Please do that before trying to run the server. Seems like you haven't activated CRD in your browser. Logged from file chrome-remote-desktop, line 1692 Logged from file chrome-remote-desktop, line 705 Logged from file chrome-remote-desktop, line 534 Logged from file chrome-remote-desktop, line 1685 23:47:09,630:INFO:Launching X server and X session.įile "/usr/lib/python2.7/logging/_init_.py", line 892, in emitįile "/usr/lib/python2.7/logging/_init_.py", line 852, in flush 23:47:06,644:INFO:Waiting before relaunching 23:47:04,641:INFO:Waiting before relaunching 23:47:04,641:INFO:Failure count for 'X server' is now 0 23:47:04,640:INFO:Failure count for 'session' is now 1 23:47:04,627:INFO:Session process terminated 23:47:04,228:INFO:Launching X server and X session. but when I recently tried it, again I started seeing errors like this, can someone help 23:47:04,227:INFO:Using host_id: 529e63f8-0684-5932-d0a4-5bfa5866cf66 I followed the post to use display :0 as my chrome-remote-desktop and it worked fine. I updated my graphics card to nvidia, and updated GDM, gnome. Please check log to determine host status. When running it with crd -start I get: Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20190910_104319_Im0hKu' Sep 10 10:38:19 BARTOSZ-PC3 systemd: Started "Chrome Remote Desktop host daemon".Īnd the log contains one line: Child terminated by signal 5 Sep 10 10:38:19 BARTOSZ-PC3 systemd: rvice: Succeeded. Sep 10 10:38:19 BARTOSZ-PC3 crd: The daemon is not currently running Sep 10 10:38:19 BARTOSZ-PC3 user-session: pam_unix(chrome-remote-desktop:session): session closed for user baatochan
Sep 10 10:38:19 BARTOSZ-PC3 crd: Failed to read from message pipe. Sep 10 10:38:19 BARTOSZ-PC3 user-session: pam_unix(chrome-remote-desktop:session): session opened for user baatochan by (uid=1000) Sep 10 10:38:19 BARTOSZ-PC3 crd: Daemon process started in the background, logging to '/tmp/chrome_remote_desktop_20190910_1> Sep 10 10:38:19 BARTOSZ-PC3 systemd: Starting "Chrome Remote Desktop host daemon". Sep 10 10:31:23 BARTOSZ-PC3 systemd: Started "Chrome Remote Desktop host daemon". Loaded: loaded (/usr/lib/systemd/user/rvice disabled vendor preset: enabled) While starting the service I get: rvice - "Chrome Remote Desktop host daemon" I'm not sure if I should set the webapp first or start the service. 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). (tried that multiple times while doing other steps described below). However when I try to do it I get No response received to getCredentialsFromAuthCode message after 30000 milliseconds. 2 08:56:36,402:INFO:Failure count for 'session' is now 1 08:56:36,402:INFO:Terminating X server Gdk-Message: 08:56:36.402: chrome-remote-desktop-host: Fatal IO error 11 (Resource temporarily unavailable) on X server :20.Īfter installation and running crd -setup the webapp shows me to "set up remote access". The XKEYBOARD keymap compiler (xkbcomp) reports: Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server 08:56:36,387:INFO:Launching X session: 08:56:36,389:INFO:Launching host process 08:56:36,389:INFO: Session output: /home/snipes/.chrome-remote-desktop-session: line 5: /usr/bin/startkde: No such file or directory 08:56:36,398:INFO:wait() returned (15630,32512) 08:56:36,398:INFO:Session process terminated Starting host process: version. Internal error: Could not resolve keysym XF86FullScreen Errors from xkbcomp are not fatal to the X server 08:56:36,334:INFO:X server is active. The XKEYBOARD keymap compiler (xkbcomp) reports: 08:56:35,826:INFO:Starting Xvfb on display :20 xdpyinfo: unable to open display ":20". No exchange needed, writing new config to mark as upgraded. No net_fetcher for performing AIA chasing. I see that it's trying to use display number 20 which isn't correct but I changed the display number to 0 and it still fails. Anybody having issues getting this working after updating chrome?
0 kommentar(er)
