d9ef612302
If the GNOME shell crashes, we run a service that may disable extensions. This is important so that users will not be locked out of their own session in case an extension is causing crashes. As this is a very agressive action, we tried to only do this in the first two minutes of the session. Unfortunately, the logic was broken and would result in an unclean session shutdown. Fix this by using the newly introduced gnome-shell-disable-extensions file. This is created by the extension subsystem for a period of time to indicate the extensions may be the cause of a gnome-shell failure. See https://gitlab.gnome.org/GNOME/gnome-session/issues/43 for a log of the bug happening and the gnome-session part to fix this. https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/858
16 lines
513 B
Desktop File
16 lines
513 B
Desktop File
[Unit]
|
|
Description=Disable GNOME Shell extensions after failure
|
|
# Note that this unit must not conflict with anything, and must
|
|
# be able to run in parallel with the gnome-session-shutdown.target.
|
|
DefaultDependencies=no
|
|
|
|
# We want to disable extensions only if gnome-shell has flagged the extensions
|
|
# to be a likely cause of trouble.
|
|
ConditionPathExists=%t/gnome-shell-disable-extensions
|
|
|
|
[Service]
|
|
Type=simple
|
|
# Disable extensions
|
|
ExecStart=gsettings set org.gnome.shell disable-user-extensions true
|
|
Restart=no
|