[SOLVED] Close "Oh no!" screen without logout / Controversial Opinion! Disabling/Masking gnome-session-failed service infinitely increases session uptime, productivity, decreases stress

To follow up on my previous post, I found the source of the “Oh no!” overlay screen is the userland gnome-session-failed service. I took control over my session back by disabling and masking it:

systemctl --user disable gnome-session-failed.service
systemctl --user mask gnome-session-failed.service

Now, try as it may, it’s been unable to interfere with my session and my work:

Feb 26 06:29:10 throne systemd[1581069]: org.gnome.Shell@x11.service: Failed to enqueue OnFailure=gnome-session-failed.target job, ignoring: Unit gnome-session-failed.service is masked.
Mar 01 01:36:53 throne systemd[1581069]: org.gnome.Shell@x11.service: Failed to enqueue OnFailure=gnome-session-failed.target job, ignoring: Unit gnome-session-failed.service is masked.
Mar 06 16:14:18 throne systemd[1581069]: org.gnome.Shell@x11.service: Failed to enqueue OnFailure=gnome-session-failed.target job, ignoring: Unit gnome-session-failed.service is masked.
Mar 09 22:44:19 throne systemd[1581069]: org.gnome.Shell@x11.service: Failed to enqueue OnFailure=gnome-session-failed.target job, ignoring: Unit gnome-session-failed.service is masked.
Mar 11 12:05:41 throne systemd[1581069]: org.gnome.Shell@x11.service: Failed to enqueue OnFailure=gnome-session-failed.target job, ignoring: Unit gnome-session-failed.service is masked.
Mar 17 04:02:48 throne systemd[1581069]: org.gnome.Shell@x11.service: Failed to enqueue OnFailure=gnome-session-failed.target job, ignoring: Unit gnome-session-failed.service is masked.
Mar 20 09:23:47 throne systemd[1581069]: org.gnome.Shell@x11.service: Failed to enqueue OnFailure=gnome-session-failed.target job, ignoring: Unit gnome-session-failed.service is masked.
Mar 23 17:37:09 throne systemd[1581069]: org.gnome.Shell@x11.service: Failed to enqueue OnFailure=gnome-session-failed.target job, ignoring: Unit gnome-session-failed.service is masked.
Mar 28 21:51:17 throne systemd[1581069]: org.gnome.Shell@x11.service: Failed to enqueue OnFailure=gnome-session-failed.target job, ignoring: Unit gnome-session-failed.service is masked.
Mar 30 18:29:39 throne systemd[1581069]: org.gnome.Shell@x11.service: Failed to enqueue OnFailure=gnome-session-failed.target job, ignoring: Unit gnome-session-failed.service is masked.
Apr 02 01:34:53 throne systemd[1581069]: org.gnome.Shell@x11.service: Failed to enqueue OnFailure=gnome-session-failed.target job, ignoring: Unit gnome-session-failed.service is masked.
Apr 04 19:36:36 throne systemd[1581069]: org.gnome.Shell@x11.service: Failed to enqueue OnFailure=gnome-session-failed.target job, ignoring: Unit gnome-session-failed.service is masked.

:smiling_imp:

I’m not yet clear on what triggers it, but it’s clearly got a hair trigger. I’ve not noticed any negative side effects from this, either. All apps, including Gnome apps and integrations, and all my extensions continue working as expected. This has increased my session uptime by almost 20-fold so far,

$ ps -o etime= -p $(pidof gdm-x-session)
38-07:15:32

and on-going, increasing to infinity.

This has worked wonders on my productivity and my stress levels!@


⠀⢀⡀⣴⡆⣰⣾⡷⠀╭────────────╼
⢶⠘⠃⣈⣀⣙⠋⠀⠀│ GNOME 47.3
⢀⣴⣿⣿⣿⣿⠇⠀⠀│ X11
⠘⣿⣿⡟⠋⣀⡀⠀⠀│ Debian trixie/sid
⠀⠈⠻⢷⣶⠿⠃⠀⠀╰────────────────────╼

I’m not yet clear on what triggers it,

journalctl -f shows runtime logs (warnings / errors etc) for the entire system.

You can check it for clues when the issue happens.