Use Chrome Remote Desktop to Remote Into Alma Linux Gnome Desktop

by | Apr 16, 2026 | Misc | 0 comments

Chrome Remote Desktop can work with an AlmaLinux GNOME desktop, but it usually needs an X11-based session rather than pure Wayland. Google’s Linux setup docs list GNOME as a supported desktop option and note that Chrome Remote Desktop does not support 3D acceleration, so GNOME Classic or a non-Wayland GNOME session is often the safer choice.

What to expect

Chrome Remote Desktop on Linux commonly creates or uses a separate remote session instead of attaching cleanly to your local logged-in desktop, so behavior may differ from what you see on Windows or macOS. For GNOME specifically, the setup typically points the remote session at gnome-session or gnome-session-classic, which fits better with Xorg than Wayland.

AlmaLinux notes

AlmaLinux can run GNOME, but the practical question is which display stack you’re using. If your GNOME login is on Wayland, Chrome Remote Desktop may be less reliable; if you switch the session to Xorg/X11, it is much more likely to work smoothly.

Practical recommendation

For an AlmaLinux GNOME server or workstation, the most reliable path is:

  • Install Chrome Remote Desktop.
  • Use a GNOME X11 session, or GNOME Classic if needed.
  • Avoid 3D-accelerated desktop effects for the remote session.

 you can get Chrome Remote Desktop working well on AlmaLinux 10.1 with the default GNOME; you’ll mostly need to ensure GNOME runs over Xorg (or X11) and then install the Chrome Remote Desktop package. Below is a tight, step‑by‑step recipe tailored to your AlmaLinux 10.1 GNOME desktop.

Step 1: Confirm/display GNOME + Xorg

  1. Log in to your AlmaLinux 10.1 GNOME desktop.
  2. Open a terminal and run:bashecho $XDG_SESSION_TYPE
    • If it shows x11, you’re good.
    • If it shows wayland, Chrome Remote Desktop will be less reliable.
  3. To force X11 on login:
    • On the login screen, click the little gear (or settings) icon next to your name.
    • Choose a session called GNOME on Xorg or GNOME (X11) instead of plain GNOME/Wayland.
  4. Log in again and verify again:bashecho $XDG_SESSION_TYPE
    • It should now be x11.

Keep this Xorg session for the user you want to remote‑desktop into.

Step 2: Install Chrome browser (optional but recommended)

Chrome Remote Desktop does not strictly require the Chrome browser, but it’s easier to set up from the Chrome app UI.

  1. Download and install Chrome:bashsudo dnf install -y wget wget https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm sudo dnf install -y ./google-chrome-stable_current_x86_64.rpm rm -f google-chrome-stable_current_x86_64.rpm
  2. Start Chrome from the GNOME menu and log in with the Google account you’ll use for Chrome Remote Desktop.

Step 3: Install Chrome Remote Desktop

Chrome Remote Desktop is distributed as a .rpm under the same Google repo as Chrome.

  1. Add the Google YUM repo (if not already present):bashsudo dnf install -y dnf-plugins-core sudo dnf config-manager --add-repo https://dl.google.com/linux/chrome/rpm/stable/x86_64/
  2. Install the Chrome Remote Desktop package:bashsudo dnf install -y chrome-remote-desktop
  3. Add your user to the chrome-remote-desktop group:bashsudo usermod -aG chrome-remote-desktop $USERThen reboot:bashsudo reboot

After reboot, log back into your GNOME (X11) session.

Step 4: Tell Chrome Remote Desktop to use GNOME

You need to tell the service which desktop session to launch.

  1. As your normal user (not root), create or edit the session file:bashmkdir -p ~/.config/chrome-remote-desktop echo "exec /etc/X11/xinit/Xsession /usr/bin/gnome-session" > ~/.config/chrome-remote-desktop/session(Older guides sometimes use /etc/chrome-remote-desktop-session, but per Google’s docs the user‑level ~/.config/chrome-remote-desktop/session is the preferred way for a user session.)
  2. Make sure the file is executable:bashchmod +x ~/.config/chrome-remote-desktop/session

Step 5: Enable and start the service

  1. Start the user‑level service:bashsystemctl --user start chrome-remote-desktop systemctl --user enable chrome-remote-desktop
  2. Optionally, verify it’s running:bashsystemctl --user status chrome-remote-desktop

Step 6: Set up Chrome Remote Desktop from the web

  1. In Chrome on your AlmaLinux box, go to:
    • https://remotedesktop.google.com
  2. Click Remote access → Turn on.
  3. Follow the prompts:
    • You’ll be asked to download an install script (the same .rpm you already installed).
    • When it asks for a PIN, set a 6–8 digit PIN you’ll remember.
  4. The page should confirm Chrome Remote Desktop is enabled and show your machine under “My computers”.

Step 7: Connect from another machine

  1. On any other device, open Chrome and go to:
    • https://remotedesktop.google.com/access
  2. Sign in with the same Google account.
  3. Your AlmaLinux 10.1 GNOME machine should appear.
  4. Click it and enter the PIN you set earlier.

At this point, you should see your GNOME desktop. If it’s slow, try:

  • Turning off GNOME animations (in Settings → Accessibility or Appearance).
  • Using a wired or fast WiFi connection.

Notes / troubleshooting

  • If the remote session is black or laggy: double‑check you’re using GNOME on Xorg, not Wayland.
  • If chrome-remote-desktop fails to start: inspect the logs:bashjournalctl --user -u chrome-remote-desktop -b
  • If you want a minimal desktop: you can also install a lightweight DE like xfce and point session to xfce4-session instead of gnome-session, but that’s optional.