You are not logged in.

#1 2015-12-24 03:03:22

014
Member
Registered: 2015-11-11
Posts: 5

Black Screen in chrome-remote-desktop

Hello everybody,

I am trying to set up Chrome Remote Desktop so I can connect to my Arch desktop. The package I am using is here:
https://aur.archlinux.org/packages/chro … e-desktop/

When I connect from another device, say a laptop or a smart phone, I get a rendered mouse that I can move around on a black screen. I can resize this black screen, and that's it. Can someone give me suggestions to try after looking at the log file below from /tmp?

[b]cat chrome_remote_desktop_20151223_204043_p3v3ht[/b]
Exception IOError: (9, 'Bad file descriptor') in <bound method _TemporaryFileWrapper.__del__ of <closed file '<fdopen>', mode 'w+b' at 0x7fa3fdd1e6f0>> ignored
2015-12-23 20:40:44,000:INFO:Using host_id: 024e5dd3-75b8-0cf4-0cd7-4b7aade18758
2015-12-23 20:40:44,000:INFO:Launching X server and X session.
2015-12-23 20:40:44,011:INFO:Starting Xvfb on display :20
xdpyinfo:  unable to open display ":20".
2015-12-23 20:40:44,522:INFO:Xvfb is active.
2015-12-23 20:40:44,550:INFO:Launching X session: ['/bin/sh', '/home/username/.chrome-remote-desktop-session']
2015-12-23 20:40:44,552:INFO:Launching host process
2015-12-23 20:40:44,553:INFO:['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/username/.config/chrome-remote-desktop/pulseaudio#c3598c83f7/fifo_output', '--ssh-auth-sockname=/tmp/chromoting.username.ssh_auth_sock', '--signal-parent']
[1223/204044:INFO:remoting_me2me_host.cc(1609)] Starting host process: version 47.0.2526.18
Xlib:  extension "RANDR" missing on display ":20".
[1223/204044:INFO:remoting_me2me_host.cc(1255)] Policy does not require curtain-mode.
[1223/204044:INFO:remoting_me2me_host.cc(1180)] Policy enables NAT traversal.
[1223/204044:INFO:remoting_me2me_host.cc(1198)] Policy enables use of relay server.
[1223/204044:INFO:remoting_me2me_host.cc(1219)] Policy restricts UDP port range to: <no port range specified>
[1223/204044:INFO:remoting_me2me_host.cc(1273)] Policy sets talkgadget prefix: chromoting-host
[1223/204044:INFO:remoting_me2me_host.cc(1282)] Policy sets third-party token URLs: <no 3rd party auth config specified>
[1223/204044:INFO:remoting_me2me_host.cc(1301)] Policy enables client pairing.
[1223/204044:INFO:remoting_me2me_host.cc(1317)] Policy enables gnubby auth.
[1223/204044:INFO:remoting_me2me_host.cc(562)] Processing new host configuration.
[1223/204044:INFO:chromoting_host.cc(113)] Starting host
[1223/204044:INFO:remoting_me2me_host.cc(1076)] Policy sets host domain: 
[1223/204044:INFO:remoting_me2me_host.cc(1153)] Policy does not require host username match.
startkde: Starting up...
Service started, version: 6.2.0

** (process:6817): WARNING **: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject
[1223/204045:INFO:dns_blackhole_checker.cc(60)] Verifying connection to [url]https://chromoting-host.talkgadget.google.com/talkgadget/oauth/chrome-remote-desktop-host[/url]
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
kscreen: Failed to request backend: unknown error
Error found while setting up ShellCorona's KScreen:  "Failed to prepare backend"
[1223/204045:INFO:dns_blackhole_checker.cc(38)] Successfully connected to host talkgadget.
[1223/204045:INFO:signaling_connector.cc(169)] Attempting to connect signaling.
[1223/204045:INFO:oauth_token_getter_impl.cc(153)] Refreshing OAuth token.
Xlib:  extension "RANDR" missing on display ":20".
[1223/204046:INFO:oauth_token_getter_impl.cc(54)] Received OAuth token.
[1223/204046:INFO:signaling_connector.cc(109)] Received user info.
[1223/204046:INFO:signaling_connector.cc(55)] Signaling connected. New JID: 024e5dd375b80cf40cd74b7aade18758@chromoting.gserviceaccount.com/chromoting8155C05C
[1223/204046:INFO:remoting_me2me_host.cc(877)] Host ready to receive connections.
2015-12-23 20:40:46,776:INFO:Host ready to receive connections.
[1223/204108:INFO:chromoting_host.cc(283)] Client connected: emailaddress/chromotingFC7C125F
[1223/204114:INFO:pam_authorization_factory_posix.cc(128)] Local login check for username succeeded.
Xlib:  extension "RANDR" missing on display ":20".
[1223/204301:ERROR:jingle_session.cc(446)] Received error in response to transport-info message: "<cli:iq to="024e5dd375b80cf40cd74b7aade18758@chromoting.gserviceaccount.com/chromoting8155C05C" type="error" id="5105594249150804063" from="emailaddress/chromotingFC7C125F" xmlns:cli="jabber:client"><jingle sid="9212135599822335857" action="transport-info" xmlns="urn:xmpp:jingle:1"><content name="chromoting" creator="initiator"><transport xmlns="google:remoting:ice"><credentials channel="video" ufrag="Wq5g1+6GrZgaBEt5" password="Cy6x6rd0JQw94CS7TptPmpnP"/></transport></content></jingle><cli:error code="503" type="cancel"><service-unavailable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></cli:error></cli:iq>". Terminating the session.
[1223/204301:INFO:client_session.cc(381)] Client disconnected: emailaddress/chromotingFC7C125F; error = 1

Last edited by 014 (2015-12-24 15:06:54)

Offline

#2 2015-12-24 03:53:11

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,740

Re: Black Screen in chrome-remote-desktop

Moving to AUR Issues.
Also, please edit your post and use BBCode code tags around program output and file contents.
Also, that link is available below every message post box on the forums.

Thanks


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2016-03-03 19:41:32

014
Member
Registered: 2015-11-11
Posts: 5

Re: Black Screen in chrome-remote-desktop

This is what comes up with I try to start chrome-remote-desktop remotely from an SSH session:

systemctl --user status chrome-remote-desktop
chrome-remote-desktop.service - "Chrome Remote Desktop host daemon"
   Loaded: loaded (/usr/lib/systemd/user/chrome-remote-desktop.service; disabled; vendor preset: enabled)
   Active: activating (start) since Thu 2016-03-03 09:23:04 CST; 18s ago
  Control: 10848 (crd)
   CGroup: /user.slice/user-1000.slice/user@1000.service/chrome-remote-desktop.service
           10848 /bin/bash /usr/bin/crd --start
           10865 /usr/bin/python2 /opt/google/chrome-remote-desktop/chrome-remote-desktop --size=1920x1080 --start
           10877 /usr/bin/python2 /opt/google/chrome-remote-desktop/chrome-remote-desktop --size=1920x1080 --start
           12867 dbus-launch --autolaunch 73bfa5a7b5aa47369b96b06950c4a784 --binary-syntax --close-stderr

Mar 03 09:23:21 crd[10848]: X server process terminated
Mar 03 09:23:21 crd[10848]: Failure count for 'X server' is now 4
Mar 03 09:23:21 crd[10848]: Waiting before launching X server
Mar 03 09:23:21 systemd-coredump[12898]: Process 12895 (ksmserver) of user 1000 dumped core.

                                                 Stack trace of thread 12895:
                                                 #0  0x00007f33c65a8edb _ZN10QXcbScreen17updateRefreshRateEj (libQt5XcbQpa.so.5)
                                                 #1  0x00007f33c65ab4dc _ZN10QXcbScreenC1EP14QXcbConnectionP18QXcbVirtualDesktopjP33xcb_randr_get_output_
                                                 #2  0x00007f33c6594f5f _ZN14QXcbConnection12createScreenEP18QXcbVirtualDesktopjP33xcb_randr_get_output_i
                                                 #3  0x00007f33c6598593 _ZN14QXcbConnection17initializeScreensEv (libQt5XcbQpa.so.5)
                                                 #4  0x00007f33c6598bec _ZN14QXcbConnectionC1EP19QXcbNativeInterfacebjPKc (libQt5XcbQpa.so.5)
                                                 #5  0x00007f33c659e83d _ZN15QXcbIntegrationC1ERK11QStringListRiPPc (libQt5XcbQpa.so.5)
                                                 #6  0x00007f33d98293ad n/a (/usr/lib/qt/plugins/platforms/libqxcb.so)
                                                 #7  0x00007f33d4d4ce62 _ZN27QPlatformIntegrationFactory6createERK7QStringRK11QStringListRiPPcS2_ (libQt5
                                                 #8  0x00007f33d4d59052 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5)
                                                 #9  0x00007f33d4d59f8d _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5)
                                                 #10 0x00007f33d4a23126 _ZN16QCoreApplication4initEv (libQt5Core.so.5)
                                                 #11 0x00007f33d4a23196 _ZN16QCoreApplicationC1ER23QCoreApplicationPrivate (libQt5Core.so.5)
                                                 #12 0x00007f33d4d5bd79 _ZN15QGuiApplicationC1ER22QGuiApplicationPrivate (libQt5Gui.so.5)
                                                 #13 0x00007f33d531451d _ZN12QApplicationC2ERiPPci (libQt5Widgets.so.5)
                                                 #14 0x00007f33d93d240a kdemain (libkdeinit5_ksmserver.so)
                                                 #15 0x00007f33d9041710 __libc_start_main (libc.so.6)
                                                 #16 0x00000000004007a9 _start (ksmserver)

                                                 Stack trace of thread 12896:

Offline

#4 2016-06-28 00:51:48

Bztvuy
Member
Registered: 2016-06-28
Posts: 1

Re: Black Screen in chrome-remote-desktop

I am having the same issue as well.  Moreover, every time I try to connect it asks me for my PIN twice before showing me the black screen.

Offline

Board footer

Powered by FluxBB