Bug#1081940: gnome-session: "Oh no! Something has gone wrong." screen because of screensaver

[Simon McVittie]

Control: reassign -1 gnome-shell 47.0-1
Control: tags -1 + experimental moreinfo

On Mon, 16 Sep 2024 at 10:42:40 +0200, Michael Ott wrote:
> Gnome crashed regularly without a reason.
[...]
> journalctl -xe -t gnome-session

gnome-session is one component of GNOME, but not the only component. Please
look at the whole Journal for error messages, not just the gnome-session
topic.

I see you are using GNOME Shell from experimental, and GNOME Shell is
the most important component of the GNOME session, so the most likely
reason would seem to be GNOME Shell.

> Sep 16 06:00:24 k-c13 gnome-session[3287]: gnome-session-binary[3287]: WARNING:
> Desktop file /etc/xdg/autostart/tracker-miner-rss-3.desktop for application
> tracker-miner-rss-3.desktop could not be parsed or references a missing TryExec
> binary
> Sep 16 06:00:24 k-c13 gnome-session[3287]: gnome-session-binary[3287]:
> GnomeDesktop-WARNING: Could not create transient scope for PID 3319:
> GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit
> properties: No such process
> Sep 16 06:00:25 k-c13 gnome-session[3287]: gnome-session-binary[3287]:
> GnomeDesktop-WARNING: Could not create transient scope for PID 3567:
> GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit
> properties: No such process
> Sep 16 10:30:42 k-c13 gnome-session[3287]: gnome-session-binary[3287]: WARNING:
> Could not retrieve current screensaver active state:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.Shell.ScreenShield was not provided by any .service files

These are warnings, not fatal errors.

    smcv