Comment 14 for bug 2063333

Revision history for this message
Alex Stanhope (alexstanhope) wrote :

(TL;DR Now works for me). I too encountered this issue (same error message as OP) on a Raspberry Pi 5.

cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

I followed the suggestions made in this post:
gnome-control-center
sudo systemd-sysusers

I rebooted the device to restart all daemons. The gnome-remote-desktop.service came up:
sudo systemctl status gnome-remote-desktop.service
● gnome-remote-desktop.service - GNOME Remote Desktop
     Loaded: loaded (/usr/lib/systemd/system/gnome-remote-desktop.service; enabled; preset: enabled)
     Active: active (running) since Fri 2024-05-03 09:03:09 BST; 12min ago
   Main PID: 1165 (gnome-remote-de)
      Tasks: 4 (limit: 9066)
     Memory: 13.4M (peak: 13.9M)
        CPU: 80ms
     CGroup: /system.slice/gnome-remote-desktop.service
             └─1165 /usr/libexec/gnome-remote-desktop-daemon --system

May 03 09:03:09 iodic systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop...
May 03 09:03:09 iodic gnome-remote-de[1165]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback
May 03 09:03:09 iodic systemd[1]: Started gnome-remote-desktop.service - GNOME Remote Desktop.

The minor TPM warning seems to be inconsequential because my device doesn't have a TPM. I was able to connect to the remote desktop on port 3389.