1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.RC

  • Bug#1070644: gnome-remote-desktop: System .service file enabled but not

    From =?UTF-8?Q?Jeremy_B=C3=ADcha?=@21:1/5 to bigon@debian.org on Fri Apr 11 17:20:01 2025
    On Fri, Mar 21, 2025 at 4:51 AM Laurent Bigonville <bigon@debian.org> wrote:
    On Mon, 06 May 2024 17:01:21 +0200 Laurent Bigonville <bigon@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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?Jeremy_B=C3=ADcha?=@21:1/5 to bigon@debian.org on Thu May 1 23:50:01 2025
    On Fri, Mar 21, 2025 at 4:51 AM Laurent Bigonville <bigon@debian.org> wrote:
    On Mon, 06 May 2024 17:01:21 +0200 Laurent Bigonville <bigon@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)

    Thank you. I am applying dh_installsystemd --no-enable as we were
    already doing dh_installsystemduser --no-enable

    Although the systemd system service was running, it wasn't actually
    listening for connections. This can be verified by running
    sudo apt install net-tools
    sudo netstat -nltp

    After applying the change, gnome-remote-desktop's system service
    behaves more like it does on other distros which is a good thing.

    Jeremy Bícha

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)