Package: gnome-remote-desktop Version: 46.1-1 Severity: normal I believe the bug is import as it prevents opening a new desktop session (but it still works when connection to an existing session).
The issue seems to be that the user gnome-remote-desktop is not existing thus the system wide systemd gnome-remote-desktop.service fails to start: journalctl -b -u gnome-remote-desktop.service avril 30 15:47:42 hermes systemd[1]: Starting gnome-remote-desktop.service - GNOME Remote Desktop... avril 30 15:47:42 hermes (p-daemon)[855818]: gnome-remote-desktop.service: Failed to determine user credentials: No such process avril 30 15:47:42 hermes systemd[1]: gnome-remote-desktop.service: Main process exited, code=exited, status=217/USER avril 30 15:47:42 hermes systemd[1]: gnome-remote-desktop.service: Failed with result 'exit-code'. avril 30 15:47:42 hermes systemd[1]: Failed to start gnome-remote-desktop.service - GNOME Remote Desktop. Also there is an error message about being unable to create the gnoem-remote-desktop home /var/lib/gnome-remote-desktop and /etc/gnome-remote-desktop as user and group gnome-remote-desktop: sudo LC_ALL=C dpkg -i gnome-remote-desktop_46.1-1_amd64.deb (Reading database ... 728947 files and directories currently installed.) Preparing to unpack gnome-remote-desktop_46.1-1_amd64.deb ... Unpacking gnome-remote-desktop (46.1-1) over (46.1-1) ... Setting up gnome-remote-desktop (46.1-1) ... /usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf:2: Failed to resolve user 'gnome-remote-desktop': No such process /usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf:3: Failed to resolve user 'gnome-remote-desktop': No such process Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 148. Processing triggers for gnome-menus (3.36.0-1.1+b2) ... Processing triggers for desktop-file-utils (0.27-2) ... Processing triggers for mailcap (3.70+nmu1) ... Processing triggers for dbus (1.14.10-4+b1) ... Processing triggers for libglib2.0-0t64:i386 (2.80.0-6) ... Processing triggers for libglib2.0-0t64:amd64 (2.80.0-6) ... Processing triggers for man-db (2.12.1-1) ... /usr/lib/tmpfiles.d/gnome-remote-desktop-tmpfiles.conf # tmpfiles.d file to ensure the existence of the home directory for gnome-remote-desktop user d /var/lib/gnome-remote-desktop 0700 gnome-remote-desktop gnome-remote-desktop d /etc/gnome-remote-desktop 0755 gnome-remote-desktop gnome-remote-desktop indeed I have no gnome-remote-desktop user: $ getent passwd|grep gnome I found no issue tracker on the salsa project for gnome-remote-desktop so opened the issue here. Cheers Alban -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'oldstable-debug'), (500, 'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.9.0-rc5+ (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-remote-desktop depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4+b2 ii fuse3 3.14.0-5 ii init-system-helpers 1.66 ii libc6 2.37-19 ii libcairo2 1.18.0-3+b1 ii libei1 1.2.1-1 ii libepoxy0 1.5.10-1+b2 ii libfreerdp-server3-3 3.5.1+dfsg1-1 ii libfreerdp3-3 3.5.1+dfsg1-1 ii libfuse3-3 3.14.0-5 ii libglib2.0-0t64 2.80.0-6 ii libmutter-14-0 46.1-1 ii libnotify4 0.8.3-1+b1 ii libopus0 1.4-1+b1 ii libpipewire-0.3-0t64 1.0.5-1+b3 ii libpolkit-gobject-1-0 124-2 ii libsecret-1-0 0.21.4-1+b1 ii libsystemd0 255.5-1 ii libtss2-esys-3.0.2-0t64 4.0.1-7.2 ii libtss2-mu-4.0.1-0t64 4.0.1-7.2 ii libtss2-rc0t64 4.0.1-7.2 ii libtss2-tctildr0t64 4.0.1-7.2 ii libwinpr3-3 3.5.1+dfsg1-1 ii libxkbcommon0 1.6.0-1+b1 ii pipewire 1.0.5-1+b3 ii wireplumber 0.4.17-1+b2 gnome-remote-desktop recommends no packages. gnome-remote-desktop suggests no packages. -- no debconf information
