Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#1036233: /usr/libexec/gdm-wayland-session[…]: dbus-daemon[…]: [session uid=… pid=…] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1

91 views
Skip to first unread message

Al Ma

unread,
May 17, 2023, 3:00:05 PM5/17/23
to
Package: gdm3
Version: 3.38.2.1-1



In my journal log I see that an activated service org.freedesktop.systemd1 failed:

Mai 17 20:37:18 AnonymizedComputerName /usr/libexec/gdm-wayland-session[1164]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Mai 17 20:37:18 AnonymizedComputerName org.gnome.Shell.desktop[1038]: Window manager warning: Failed to parse saved session file: Datei »/var/lib/gdm3/.config/mutter/sessions/10b3c2ff926492598a168434863567744800000009950000.ms« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
Mai 17 20:37:18 AnonymizedComputerName dbus-daemon[772]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Mai 17 20:37:18 AnonymizedComputerName systemd[1]: Started PackageKit Daemon.
Mai 17 20:37:18 AnonymizedComputerName kernel: rfkill: input handler disabled
Mai 17 20:37:18 AnonymizedComputerName /usr/libexec/gdm-wayland-session[983]: dbus-daemon[983]: [session uid=119 pid=983] Activating service name='org.freedesktop.systemd1' requested by ':1.9' (uid=119 pid=1176 comm="/usr/libexec/gsd-sharing ")
Mai 17 20:37:18 AnonymizedComputerName /usr/libexec/gdm-wayland-session[983]: dbus-daemon[983]: [session uid=119 pid=983] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1

Failures are not good in general and make me worry (especially since my log shows many of them). How bad is this particular failure? Who is the culprit and what to do? The machine runs systemd 247.3-7+deb11u2, dbus 1.12.24-0+deb11u1, and gnome-settings-daemon 42.2-1 (which contains /usr/libexec/gsd-sharing).

Gratefully,

AlMa

AlMa

unread,
Jun 21, 2023, 10:50:04 PM6/21/23
to
found 1036233 gdm3/43.0-3
severity 1036233 important
affects 1036233 gnome-settings-daemon
thanks

The bug still exists on Debian stable 12. Here's an excerpt from the log:

Jun 22 04:11:23 AnonymizedMachineName org.gnome.Shell.desktop[1148]:
Window manager warning: Failed to parse saved session file: Datei
»/var/lib/gdm3/.config/mutter/sessions/104bd2034b48525060168739988159401100000010980000.ms«
konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden
Jun 22 04:11:23 AnonymizedMachineName /usr/libexec/gdm-x-session[1096]:
dbus-daemon[1096]: [session uid=119 pid=1096] Successfully activated
service 'org.gnome.Shell.Notifications'
Jun 22 04:11:23 AnonymizedMachineName kernel: rfkill: input handler disabled
Jun 22 04:11:23 AnonymizedMachineName /usr/libexec/gdm-x-session[1096]:
dbus-daemon[1096]: [session uid=119 pid=1096] Activating service
name='org.gtk.vfs.Daemon' requested by ':1.20' (uid=119 pid=1282
comm="ibus-daemon --panel disable --xim")
Jun 22 04:11:23 AnonymizedMachineName /usr/libexec/gdm-x-session[1096]:
dbus-daemon[1096]: [session uid=119 pid=1096] Activating service
name='org.freedesktop.systemd1' requested by ':1.10' (uid=119 pid=1236
comm="/usr/libexec/gsd-sharing")
Jun 22 04:11:23 AnonymizedMachineName /usr/libexec/gdm-x-session[1096]:
dbus-daemon[1096]: [session uid=119 pid=1096] Activated service
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1
exited with status 1
Jun 22 04:11:23 AnonymizedMachineName gsd-sharing[1236]: Failed to
StopUnit service:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
org.freedesktop.systemd1 exited with status 1
Jun 22 04:11:23 AnonymizedMachineName gsd-sharing[1236]: Failed to
StopUnit service:
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
org.freedesktop.systemd1 exited with status 1

Raising severity because it causes an error report downstream by
gsd-sharing. (The hard error I observe outside the journal is that
Wayland doesn't start (instead, X11 jumps in) and there may or may not
be a connection between the two errors.)
0 new messages