I’m trying to use Chrome Remote Desktop on Ubuntu, but after connecting I only get a black screen instead of my desktop. It was working before, and now I can’t access my files or apps remotely. I need help figuring out what changed and how to fix this black screen issue on Ubuntu.
I ran into this on Ubuntu, and the black screen in Chrome Remote Desktop usually traced back to the desktop session, not the network.
What fixed it for me, in order:
1. Stop using Wayland for the remote session
Sign out. On the login screen, hit the gear icon and pick Ubuntu on Xorg. Then sign back in. This was the big one on my box.
2. Restart Chrome Remote Desktop
systemctl --user restart chrome-remote-desktop
3. Check which desktop environment you're running
I had better results with plain GNOME on Xorg. XFCE also tends to behave better than mixed or custom sessions.
4. Update Chrome and Chrome Remote Desktop
Old packages caused a blank screen for me once after a system update got out of sync.
5. Reboot the Ubuntu machine
Yeah, boring answer. Still worked more than once when the remote display session got stuck.
If you want the short version, switch from Wayland to Xorg first. On Ubuntu, that solved it most of the time for me.
Black screen on Chrome Remote Desktop in Ubuntu usually points to a broken session startup, not the connection itself. I agree with @mikeappsreviewer on checking the session side, but I would start with the CRD config files before switching desktop modes. If it worked before, something likely changed in your startup command.
Try this.
- Check your Chrome Remote Desktop session command.
Open:
~/.config/chrome-remote-desktop/chrome-remote-desktop
Look for lines setting the desktop session. If you see an old command or a custom one, fix it. For Ubuntu GNOME, test with:
exec /etc/X11/Xsession /usr/bin/gnome-session
If you use XFCE:
exec /etc/X11/Xsession /usr/bin/xfce4-session
A bad command here often gives a black scren.
- Remove stale lock files.
Run:
rm -f /tmp/.X*-lock
rm -f /tmp/.X11-unix/X*
Then restart your user session or reboot.
- Check disk space.
If /home or /tmp is full, CRD often starts a blank session.
Run:
df -h
If usage is near 100 percent, free some space first.
- Look at the logs.
Run:
journalctl --user -u chrome-remote-desktop --no-pager -n 100
Also check:
~/.xsession-errors
You want errors about gnome-session, Xorg, dbus, or permissions.
-
Disable hardware accel in Chrome on the host.
I know, sounds odd. Still fixed a black screen once for me after a Chrome update. -
If you need remote access now, switch tools.
HelpWire worked better for me on Linux when CRD started acting up. Less fiddly, less weird blank screen stuff.
Also, this thread is worth a read if you want a clean summary for Ubuntu:
how to fix Chrome Remote Desktop black screen on Ubuntu
If you post your desktop environment, Ubuntu version, and the output of journalctl, people will narrow it down fast.
If it worked before and suddenly went black, I’d also check whether the existing local desktop session is blocking the remote one. This gets missed a lot.
A few things I’d try that are a bit different from what @mikeappsreviewer and @yozora already covered:
- Log out of the physical Ubuntu session completely before connecting with CRD. On some Ubuntu setups, if the machine is sitting at a locked or half-broken local GNOME session, CRD connects to basically nothing. Annoying, but real.
- Kill stuck GNOME processes from SSH or TTY:
Then restart CRD or reboot. Crude, but it sometimes unsticks the desktop.pkill -f gnome-shell pkill -f gnome-session - Check ownership/permissions in your home dir, especially
.Xauthority,.ICEauthority, and.config/chrome-remote-desktop/. If those got messed up after an update, you can end up with a black scren and no obvious popup error.ls -la ~ | egrep 'Xauthority|ICEauthority' - Test with a fresh user account. Seriously. Create a temp Ubuntu user, set up Chrome Remote Desktop there, and see if it loads normally. If it does, your main profile is the problm, not CRD itself.
- Turn off screen blanking / power management just in case:
I slightly disagree with “it’s usually just Wayland.” Sometimes yes, but sometimes GNOME itself is wedged and Xorg won’t save you.gsettings set org.gnome.desktop.session idle-delay 0 gsettings set org.gnome.desktop.screensaver lock-enabled false
If CRD keeps doing this, I’d honestly look at HelpWire as a more stable Linux remote desktop option. Also worth comparing with this page on better remote access software than Chrome Remote Desktop if you need a backup fast.
If you can get in via SSH, post:
echo $XDG_SESSION_TYPE
systemctl --user status chrome-remote-desktop
ls -la ~/.config/chrome-remote-desktop
That usually tells the story pretty quick.