Issue 423818 in chromium: Chrome remote desktop shows a black screen

[chro...@googlecode.com]

Status: Untriaged
Owner: ----
Labels: Type-Bug Pri-2 Cr-Services-Chromoting OS-Linux OS-Chrome

New issue 423818 by ma...@chromium.org: Chrome remote desktop shows a black
screen
https://code.google.com/p/chromium/issues/detail?id=423818

(Sorry if this is a duplicate; couldn't find anything on crbug.)

I set up Chrome remote desktop, Host Ubuntu 14.04 + Chrome stable channel,
Client Chromebook + Chrome beta channel (38).

I'm able to connect the client to the host, but then I see just a black
screen with the CRD menu (send keys etc.) and an X-shaped cursor.

Users seem to be having the same problem too:

https://productforums.google.com/forum/#!topic/chrome/tLxABgTmXUw

I have the repro case here, I'm willing to debug if somebody tells me
how :) I cannot use a self-built chromium on either of those computers
though.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Updates:
Status: Duplicate
Mergedinto: 230418

Comment #1 on issue 423818 by ma...@chromium.org: Chrome remote desktop

shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

Argh, found a duplicate... so going to reopen that instead.

[chro...@googlecode.com]

Comment #4 on issue 423818 by hbeng...@chromium.org: Chrome remote desktop

shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

Host logs are at /tmp/chrome_remote_desktop_[YYYYMMDD]_[HHMMSS]_*. These
files are timestamped with the host start time, please provide the one
corresponding to the time frame of the issue.

[chro...@googlecode.com]

Updates:
Cc: rmso...@chromium.org

Comment #5 on issue 423818 by jamie...@chromium.org: Chrome remote

desktop shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

Here's the log, with some personal information redacted. It looks like the
problem is these lines at the bottom:

[1016/200750:WARNING:chromium_port_allocator.cc(121)] Received error when
allocating relay session: 403
[1016/200750:WARNING:chromium_port_allocator.cc(121)] Received error when
allocating relay session: 403
[1016/200750:WARNING:chromium_port_allocator.cc(121)] Received error when
allocating relay session: 403
[1016/200750:WARNING:chromium_port_allocator.cc(121)] Received error when
allocating relay session: 403
[1016/200750:WARNING:chromium_port_allocator.cc(121)] Received error when
allocating relay session: 403
[1016/200750:WARNING:chromium_port_allocator.cc(121)] Received error when
allocating relay session: 403
[1016/200750:WARNING:chromium_port_allocator.cc(121)] Received error when
allocating relay session: 403
[1016/200750:WARNING:chromium_port_allocator.cc(121)] Received error when
allocating relay session: 403
[1016/200750:WARNING:chromium_port_allocator.cc(121)] Received error when
allocating relay session: 403
[1016/200750:WARNING:chromium_port_allocator.cc(121)] Received error when
allocating relay session: 403

403 is "Forbidden", but I'm not sure why you'd be getting this. Renato, can
you suggest anything?

Attachments:
chrome_remote_desktop_20141016_030729_m1f6Ny 10.3 KB

[chro...@googlecode.com]

Updates:
Status: Assigned
Owner: lambros...@chromium.org

Comment #7 on issue 423818 by jamie...@chromium.org: Chrome remote

desktop shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

Lambros, this looks like the lightdm-session vs. gnome-session problem
we've been seeing a lot internally. Can you follow up with instructions to
fix it?

[chro...@googlecode.com]

Updates:
Owner: lambros...@chromium.org

Comment #9 on issue 423818 by ma...@chromium.org: Chrome remote desktop

shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

Thanks; I did the following:

1) changed the ownership of the .cache/dconf and files within. End result:

$ ls -l .cache/dconf/
total 4
-rw------- 1 marja marja 2 Okt 18 14:01 user

$ ls -ld .cache/dconf/
drwx------ 2 marja root 4096 Okt 18 14:01 .cache/dconf/

$ ls -ld .cache
drwx------ 24 marja marja 4096 Okt 13 21:40 .cache

2) Created ~/.chrome-remote-desktop-session. End result:

$ cat ~/.chrome-remote-desktop-session
#!/bin/sh
export DESKTOP_SESSION=ubuntu
export XDG_CURRENT_DESKTOP=Unity
exec /usr/sbin/lightdm-session 'gnome-session --session=ubuntu'

3) Restarted.

But it still doesn't work (still get the black screen when trying to log in
from Chromebook). I attached the new log. It whines about some X errors,
and "Received error when allocating relay session: 403" is still there.

Attachments:
chrome_remote_desktop_20141018_140146_nZ5Lt3 8.3 KB

[chro...@googlecode.com]

Updates:
Labels: -OS-Chrome

Comment #10 on issue 423818 by lambros...@chromium.org: Chrome remote

desktop shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

Hmm, interesting. I get the same failure if I remove the RANDR-patched Xvfb
package.

Is this on a Google corp machine? If so, can you install the xvfb-randr
package, and restart the service?
sudo apt-get install xvfb-randr
sudo /etc/init.d/chrome-remote-desktop restart

(Removing OS-Chrome - the problem is host-side)

[chro...@googlecode.com]

Comment #11 on issue 423818 by ma...@chromium.org: Chrome remote desktop

shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

No, this is on a private machine.

[chro...@googlecode.com]

Comment #13 on issue 423818 by tomasz.k...@gmail.com: Chrome remote desktop

shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

tried installing cinnamon:

sudo apt-get install cinnamon

with:

#!/bin/sh
exec /usr/sbin/lightdm-session /usr/bin/cinnamon2d

in ~/.chrome-remote-desktop-session

but then on:
sudo /etc/init.d/chrome-remote-desktop restart

server won't restart:

sudo /etc/init.d/chrome-remote-desktop restarLaunching X server and X
session.
Starting Xvfb on display :20
Xvfb is active.
Launching X session:
['/bin/sh', '-c', '/home/tomek/.chrome-remote-desktop-session']
Launching host process
['/opt/google/chrome-remote-desktop/chrome-remote-desktop-host', '--host-config=-', '--audio-pipe-name=/home/tomek/.config/chrome-remote-desktop/pulseaudio#8303220f39/fifo_output', '--ssh-auth-sockname=/tmp/chromoting.tomek.ssh_auth_sock', '--signal-parent']
wait() returned (16722,35584)
Session process terminated
Terminating X server
wait() returned (16724,256)
Host process terminated
Failure count for 'host' is now 3
Host exited with status 1.
Terminating X server

[chro...@googlecode.com]

Updates:
Status: Duplicate
Mergedinto: 366432

Comment #16 on issue 423818 by lambros...@chromium.org: Chrome remote

desktop shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #17 on issue 423818 by dmu...@chromium.org: Chrome remote desktop

shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

I'm getting this now

[chro...@googlecode.com]

Comment #18 on issue 423818 by lambros...@chromium.org: Chrome remote

desktop shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

Sorry to hear about the black screen problems. It appears that the version
of Xvfb that comes with Ubuntu Trusty does not support OpenGL (GLX).
A workaround is to use the version from Precise:
http://packages.ubuntu.com/precise/xvfb
(maybe try the ones from Utopic or Vivid to see if they've fixed the
problem?)
Another workaround is to use a more lightweight desktop such as Xfce, and
to not run any OpenGL programs.
Yet another workaround is to build your own Mesa OpenGL implementation
based on Xlib that doesn't rely on GLX support in the X server. I haven't
got this to work successfully.

[chro...@googlecode.com]

Comment #19 on issue 423818 by kevin.pe...@gmail.com: Chrome remote desktop

shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

I tried all of the suggestions in this post to no avail with Ubuntu 15.04
(no problem at all with 14.04 or 14.10). I have resorted to using LXDE,
which works fine, so I' guessing it is a problem specifically related to
lightdm and systemd.

[chro...@googlecode.com]

Comment #20 on issue 423818 by Christop...@gmail.com: Chrome remote desktop

shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

Remote desktop worked fine up to recently but now I got a full black
screen. I've tried to remove it and re-install but it did not help.
Any idea what can I do?

[chro...@googlecode.com]

Comment #21 on issue 423818 by Christop...@gmail.com: Chrome remote desktop

shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

Just to add on which system I'm operating it:

CHROME VERSION
43.0.2357.134
Official Build
CHROMEOS_RELEASE_CHROME_MILESTONE
43
CHROMEOS_RELEASE_DESCRIPTION
6946.86.0 (Official Build) stable-channel x86-alex_he
CHROMEOS_RELEASE_NAME
Chrome OS
CHROMEOS_RELEASE_PATCH_NUMBER
0
CHROMEOS_RELEASE_TRACK
stable-channel
CHROMEOS_RELEASE_VERSION
6946.86.0
CLIENT_ID
cat: /home/chronos/Consent To Send Stats: No such file or directory
GOOGLE_RELEASE
6946.86.0

[chro...@googlecode.com]

Comment #23 on issue 423818 by dhruv...@chromotif.com: Chrome remote

desktop shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

I need to access my remote desktop which is Windows Server 2012 R2 using
Chrome Remote Desktop.

I have started CRD Service using my chrome account over there and try to
Access server on my local PC using same chrome account.

I can not see anything, Screen is Black Completely.

I can Access server using Remote Desktop Services (MSTSC)

Can anyone Provide me a solution?

[chro...@googlecode.com]

Comment #24 on issue 423818 by dhruv...@chromotif.com: Chrome remote

desktop shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

I need to access my remote desktop which is Windows Server 2012 R2 using
Chrome Remote Desktop.

I have started CRD Service using my chrome account over there and try to
Access server on my local PC using same chrome account.

I can not see anything, Screen is Black Completely.

Chrome Version on Remote R2 Server is 44.0.2403.157.

[chro...@googlecode.com]

Comment #25 on issue 423818 by jamie...@chromium.org: Chrome remote

desktop shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

This bug is closed and was specific to a Linux host. Since your problem is
on Windows, please file a separate bug (you can follow up with the bug
number here and I'll make sure it gets triaged appropriately). You can
speed up the process by including host logs with your bug report; to do
this, follow these instructions:

The OS includes logman.exe providing a simple way of recording ETW traces.
It is an ideal way to capture the host debug log from the user's machine.
Just follow the steps below:

* Run cmd.exe elevated: right-click on cmd.exe shortcut and choose "Run as
administrator".
* Start the trace with the following command:

logman create trace -ets "chromoting" -p
{2db51ca1-4fd8-4b88-b5a2-fb8606b66b02} 0xffffffff 5 -o %TEMP%\chromoting.etl

* Do stuff
* Stop the trace with the following command:

logman stop -ets "chromoting"

* Import %TEMP%\chromoting.etl to Sawbuck. Note that %TEMP% folder may be
different if logman and sawbuck are running under different users.

You should be able to attach the ETL file to your bug report.

[chro...@googlecode.com]

Comment #26 on issue 423818 by ErikR...@gmail.com: Chrome remote desktop

shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

I'm having these exact issues as stated above with the black screen in
linux.

I created a .chrome-remote-desktop-session file with
exec /usr/bin/gnome-session --session=cinnamon2d

but this produced the same errors as above posted by tomasz.k 13Jan15.

When I removed the .chrome-remote-desktop-session file, I was able to get a
connection, but with a black screen.
I closed the chrome remote desktop on the host, and then tried to reconnect
with my laptop.

It logged in, but said "cinnamon just crashed. You have now entered
fallback mode." I'm logged in to my computer, but in a different session
altogether!

The log showed:
Xlib extension "RANDR" missing on dispaly ":20"
No realy auth token found
Listening for gnubby requests on /tmp.chromoting.anon.ssh_auth_sock

Received error when allocating relay session :403

Any ideas?

[chro...@googlecode.com]

Comment #28 on issue 423818 by Christop...@gmail.com: Chrome remote desktop

shows a black screen
https://code.google.com/p/chromium/issues/detail?id=423818

Related to my problem (#20, #21), I've found the reason: the desktop that I
was trying to connect has a too high resolution of 2556 x 1440. When
decreasing to 1920 x 1080 then it is fine!