Package: gnome-remote-desktop Version: 46.1-3 Severity: normal Hello,
It seems that the system systemd .service is enabled at boot, while the user one is not. Any reason why the former is enabled and the later is not? Not sure I see the rational here Kind regards, Laurent Bigonville -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr 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.38-7 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-3 ii libfreerdp3-3 3.5.1+dfsg1-3 ii libfuse3-3 3.14.0-5 ii libglib2.0-0t64 2.80.0-9 ii libmutter-14-0 46.1-2 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-3 ii libxkbcommon0 1.6.0-1+b1 ii pipewire 1.0.5-1+b3 ii systemd [systemd-sysusers] 255.5-1 ii wireplumber 0.4.17-1+b2 gnome-remote-desktop recommends no packages. gnome-remote-desktop suggests no packages. -- no debconf information
