On Fri, Mar 21, 2025 at 4:51 AM Laurent Bigonville <bi...@debian.org> wrote: > On Mon, 06 May 2024 17:01:21 +0200 Laurent Bigonville <bi...@debian.org> > wrote: > > > 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 > > So the gnome-control-center controls itself whether the > /etc/systemd/system/graphical.target.wants/gnome-remote-desktop.service > symlink is created or not > > By default when installing the package, the service is enabled (and > started?), this is IMHO not good and make the switch in g-c-c out of > sync with the real state of the service. > > The package should not enable and start the system part of the daemon by > default either (dh_installsystemd --no-enable --no-start)
When I looked at this before, I think the upstream design was that the service may be running without actually listening to connections. If that's true, this doesn't seem to be RC. I don't have capacity to look at this issue now or soon, so I'm replying to reset the autoremoval timer since we definitely want gnome-remote-desktop in Trixie. Thank you, Jeremy Bícha
