Bug 916496 – net-misc/gnome-remote-desktop openrc service

• Product: Gentoo Linux
• Status: UNCONFIRMED ---

[Description adeliktas 2023-10-29 18:55:46 UTC]

Created attachment 873672 [details]
gnome-remote-desktop-daemon openrc service file with issues

until recently it wasn't possible to run gnome-remote-desktop on Gnome(X11) https://bugs.gentoo.org/861548

but now that it runs i'd like to create an openrc service for it.

The following does run the gnome-remote-desktop daemon with `rc-service gnome-remote-desktop start` but it's status is stuck at starting. I'd assume because it awaits a return from gnome-remote-desktop-daemon.

It also is not able to stop a running process and requires `kill -9 (pidof /usr/libexec/gnome-remote-desktop-daemon)`

[Comment 1 Mart Raudsepp 2023-10-30 21:19:15 UTC]

This is hardcoding uid 1000 and forcing it to run at boot for that user?

[Comment 2 adeliktas 2023-10-30 21:26:29 UTC]

(In reply to Mart Raudsepp from comment #1)
> This is hardcoding uid 1000 and forcing it to run at boot for that user?

That does work for my case and seems better than specifying a username, which others will not have. I don't know what the alternative would be for a user service. But that's something to look into after getting the service start/stop issue solved.

[Comment 3 Mart Raudsepp 2023-10-30 21:35:06 UTC]

There is no alternative that I can see (where it's only started when needed, controlled by GNOME); we need user services that are controllable via dbus API, preferably the same service as systemd provides.
gnome-remote-desktop is supposed to only be started as a user service when the user enables screen sharing in gnome-control-center - then it starts it up via systemd user service dbus API then, and when enabled, then also on next log-in, etc.

We can't put anything with hardcoded user uid's into the main tree like that.