Investigate suitability of systemd user sessions

[jonte]

Should all applications started in a user (as in non-system) context be started in a systemd user session? Does this make sense for Bistro?

See here for more information: https://wiki.archlinux.org/index.php/Systemd/User

Using this concept would make it easier to set up per-user services, such a D-Bus daemons (for session busses), PulseAudio daemons, and would also be a logical place to start AppMan on QtAS systems.

[erikboto]

In the GDP QtAS-spin appman and neptune-ui is running in a systemd-user-sessions, but still as root. I'd be happy to look in to this a bit more if I can get the time, but my first impression is that we should start using systemd user sessions.

Just a note if anyone else is looking into this, any user that should run services using the user-session when not being logged in need to be allowed to "linger". See loginctl man-page and search for linger. It's basically a way to tell systemd that the user session should not only be allowed to be active when the user is logged in.

[tobsan]

From a security point of view this makes so much sense, but I assume that this issue really should be moved to meta-pelux rather than here nowadays, right?