Control: severity -1 minor
On Mon, 21 Dec 2020 at 16:30:40 +0100, Michael Biebl wrote:
> I noticed in my journal the following error messages
>
> Dez 21 16:22:13 pluto /usr/libexec/gdm-wayland-session[820]:
> dbus-daemon[820]: [session uid=109 pid=820] Activating service
> name='org.freedesktop.systemd1' requested by ':1.27' (uid=109 pid=1090
> comm="/usr/libexec/gsd-sharing ")
> Dez 21 16:22:13 pluto /usr/libexec/gdm-wayland-session[820]:
> dbus-daemon[820]: [session uid=109 pid=820] Activated service
> 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited
> with status 1
> Dez 21 16:22:13 pluto gsd-sharing[1090]: Failed to StopUnit service:
> GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
> org.freedesktop.systemd1 exited with status 1
> Dez 21 16:22:13 pluto gsd-sharing[1090]: Failed to StopUnit service:
> GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
> org.freedesktop.systemd1 exited with status 1
> Dez 21 16:22:13 pluto gsd-sharing[1090]: Failed to StopUnit service:
> GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
> org.freedesktop.systemd1 exited with status 1
>
> I wonder if this is related to #977826 and how the session is started
> within gdm.
Almost certainly. The dbus-daemon is started on a per-greeter basis
(one per X11 or Wayland display) because on multi-seat or XDMCP systems,
gdm wants to run several independent sessions all sharing one uid; so it
can't talk to `systemd --user`.
The error message is different because gsd-sharing is still trying to
perform activation via autostarting, whereas gnome-session has been taught
not to try to do that (it won't work).
Ideally these messages shouldn't appear, but I don't think they indicate
a real bug.
> comm="/usr/libexec/gsd-sharing "
In an ideal world, I suspect this service shouldn't even be started in
the greeter: there's no reason why the greeter session would want to
share anything with a LAN.
smcv
