[Bug 2064647] Re: Documentation for how to enable gnome-remote-desktop on a completly headless system
From Upstream I tried to enable using some commands through grdctl with no such luck grdctl enable [20:15:58:493] [60992:ee40] [ERROR][com.freerdp.crypto] - [x509_utils_from_pem]: BIO_new failed for certificate RDP server certificate is invalid. Usage: grdctl [OPTIONS...] COMMAND [SUBCOMMAND]... grdctl --headless enable [20:[61000:ee48] [ERROR][com.freerdp.crypto] - [x509_utils_from_pem]: BIO_new failed for certificate 16:02:476] RDP server certificate is invalid. Init TPM credentials failed because No TPM device found, using GKeyFile as fallback. Usage: grdctl [OPTIONS...] COMMAND [SUBCOMMAND]... grdctl --system enable Error changing to home directory /var/lib/gnome-remote-desktop: No such file or directory From @pnowack That's a packaging issue. Please report that to your distro. g-r-d installs both a sysusers and a tmpfiles file for the user for the system daemon and its config dirs. The sysusers and tmpfiles hooks usually run on a reboot, but they also MUST run when installing the respective pkg, in particular: after the decompression of the files (post-installation hooks). This works fine on other distros, like Arch (pacman automatically detects such sysusers- or tmpfiles-file installation and runs the respective hooks for that). apt or dpkg must also be able to correctly handle this (regardless of the pkg). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064647 Title: Documentation for how to enable gnome-remote-desktop on a completly headless system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2064647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064647] [NEW] Documentation for how to enable gnome-remote-desktop on a completly headless system
Public bug reported: Asked to create a new bug from https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/206 I am on a completely headless system starting from a minimal ubuntu-server 24.04 installation. I have installed the desktop using apt install ubuntu-desktop I want to use the new gnome-remote-desktop so that I can create a developer machine in a VM environment that can be accessed through a thin client as an example using Microsoft RDP I suspect there is some missing documentation. Starting the service using systemctl start gnome-remote-desktop.service results in: journalctl -xeu gnome-remote-desktop.service Apr 30 10:16:39 localhost systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... ░░ Subject: A start job for unit gnome-remote-desktop.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit gnome-remote-desktop.service has begun execution. ░░ ░░ The job identifier is 2929. Apr 30 10:16:39 localhost (p-daemon)[1613]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 30 10:16:39 localhost systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit gnome-remote-desktop.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 217. Running sudo systemd-sysusers does create some new users, restarting the remote desktop now gives: May 02 14:27:47 localhost gnome-remote-de[36906]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback May 02 14:27:47 localhost gnome-remote-de[36906]: Init file credentials failed: Error creating directory /var/lib/gnome-remote-desktop: Permission denied May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: ** May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: (priv->credentials) May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: Bail out! ERROR:../src/grd-settings.c:345:grd_settings_constructed: assertion failed: (priv->credentials) May 02 14:27:47 localhost systemd[1]: gnome-remote-desktop.service: Main process exited, code=dumped, status=6/ABRT As a headless system I can not use any UI controls so I suspect there is some command / config that needs to to be set before launching rdp ** Affects: gnome-remote-desktop (Ubuntu) Importance: Low Status: Triaged ** Description changed: Asked to create a new bug from https://bugs.launchpad.net/ubuntu/+source/gnome-remote- desktop/+bug/206 - I am on a completely headless system starting from a minimal ubuntu-server 24.04 installation. - I have installed the desktop using apt install ubuntu-desktop + I am on a completely headless system starting from a minimal ubuntu-server 24.04 installation. + I have installed the desktop using apt install ubuntu-desktop I want to use the new gnome-remote-desktop so that I can create a developer machine in a VM environment that can be accessed through a - thin client using Microsoft RDP + thin client as an example using Microsoft RDP I suspect there is some missing documentation. Starting the service using systemctl start gnome-remote-desktop.service results in: journalctl -xeu gnome-remote-desktop.service Apr 30 10:16:39 localhost systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... ░░ Subject: A start job for unit gnome-remote-desktop.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit gnome-remote-desktop.service has begun execution. ░░ ░░ The job identifier is 2929. Apr 30 10:16:39 localhost (p-daemon)[1613]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 30 10:16:39 localhost systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit gnome-remote-desktop.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 217. - Running sudo systemd-sysusers does create some new users, restarting the remote desktop now gives: May 02 14:27:47 localhost gnome-remote-de[36906]: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback May 02 14:27:47 localhost gnome-remote-de[36906]: Init file credentials failed: Error creating directory /var/lib/gnome-remote-desktop: Permission denied May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]: ** May 02 14:27:47 localhost gnome-remote-desktop-daemon[36906]:
[Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
I using it in a cloud provider using ssh, I want to be able to configure it completely headless. I can not log into the UI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
Nothing really reported from running the above command /usr/libexec/gnome-remote-desktop-daemon --system ** (gnome-remote-desktop-daemon:36048): WARNING **: 11:01:25.879: Init TPM credentials failed because No TPM device found, using GKeyFile as fallback But no ports are open netstat -tnlp Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN 29997/cupsd tcp0 0 127.0.0.54:53 0.0.0.0:* LISTEN 16105/systemd-resol tcp0 0 127.0.0.53:53 0.0.0.0:* LISTEN 16105/systemd-resol tcp6 0 0 ::1:631 :::*LISTEN 29997/cupsd tcp6 0 0 :::22 :::*LISTEN 1/systemd I restarted GDM3 ps -aux | grep gnome gdm35757 0.0 0.6 233060 6144 tty1 Ssl+ 11:01 0:00 /usr/libexec/gdm-wayland-session dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart gdm35761 0.0 0.2 6500 2432 tty1 S+ 11:01 0:00 dbus-run-session -- gnome-session --autostart /usr/share/gdm/greeter/autostart gdm35763 0.0 1.8 518252 18304 tty1 Sl+ 11:01 0:00 /usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart gdm35772 1.0 22.0 3251940 217456 tty1 Sl+ 11:01 0:01 /usr/bin/gnome-shell gdm35799 0.0 0.7 236060 7552 tty1 Sl+ 11:01 0:00 /usr/libexec/at-spi2-registryd --use-gnome-session gdm35822 0.0 2.7 2590472 26852 tty1Sl+ 11:01 0:00 /usr/bin/gjs -m /usr/share/gnome-shell/org.gnome.Shell.Notifications gdm36027 0.0 2.7 2590464 26860 tty1Sl+ 11:01 0:00 /usr/bin/gjs -m /usr/share/gnome-shell/org.gnome.ScreenSaver root 36090 0.0 1.7 439656 16896 ttyS0Sl+ 11:02 0:00 /usr/libexec/gnome-remote-desktop-daemon --system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063333] Re: gnome-remote-desktop.service: Failed to determine user credentials: No such process
Also seeing the same issue on a headless server (Linode) 24.04 Ubuntu server Installed ubuntu-desktop 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 journalctl -xeu gnome-remote-desktop.service Apr 30 10:16:39 localhost systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... ░░ Subject: A start job for unit gnome-remote-desktop.service has begun execution ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ A start job for unit gnome-remote-desktop.service has begun execution. ░░ ░░ The job identifier is 2929. Apr 30 10:16:39 localhost (p-daemon)[1613]: gnome-remote-desktop.service: Failed to determine user credentials: No such process Apr 30 10:16:39 localhost systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER ░░ Subject: Unit process exited ░░ Defined-By: systemd ░░ Support: http://www.ubuntu.com/support ░░ ░░ An ExecStart= process belonging to unit gnome-remote-desktop.service has exited. ░░ ░░ The process' exit code is 'exited' and its exit status is 217. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206 Title: gnome-remote-desktop.service: Failed to determine user credentials: No such process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
