gnome-shell crashes when suspending with nvidia unless MUTTER_DEBUG_KMS_THREAD_TYPE=user is set
Affected version
mutter-45.0-11.fc39.x86_64
mutter-common-45.0-11.fc39.noarch
gnome-shell-45.0-1.fc39.x86_64
Bug summary
More recently, I believe it started with GNOME 45 on Fedora 39, I have noticed that GNOME will simply refuse to login if my laptop is not plugged to AC. Also, sometimes I will leave the laptop suspend and have to take it out of AC charger for some reason (for example, heavy rain), and when I resume it will run fine for a while but the it might randomly logout (seem to be triggered by closing some applications)
Steps to reproduce
Have a laptop, boot it without Ac charger connected
What happened
If from a cold boot and AC charger unplugged, you won't be able to login, you will be returned to login screen.
If resuming from suspend with AC charger unplugged, the session may crash at random.
What did you expect to happen
Ideally the session should work fine.
Relevant logs, screenshots, screencasts etc.
out 27 10:35:15 centauro systemd[2883]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL
out 27 10:35:15 centauro systemd[2883]: org.gnome.SettingsDaemon.Keyboard.service: Main process exited, code=exited, status=1/FAILURE
out 27 10:35:15 centauro systemd[2883]: dbus-:1.2-org.gnome.Shell.Screencast@0.service: Main process exited, code=exited, status=1/FAILURE
out 27 10:35:15 centauro systemd[2883]: dbus-:1.2-org.gnome.Shell.Screencast@0.service: Failed with result 'exit-code'.
out 27 10:35:15 centauro systemd[2883]: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=exited, status=1/FAILURE
out 27 10:35:15 centauro systemd[2883]: org.gnome.SettingsDaemon.Power.service: Main process exited, code=exited, status=1/FAILURE
out 27 10:35:15 centauro systemd[2883]: org.gnome.SettingsDaemon.Wacom.service: Main process exited, code=exited, status=1/FAILURE
out 27 10:35:15 centauro systemd[2883]: org.gnome.SettingsDaemon.Color.service: Failed with result 'exit-code'.
out 27 10:35:15 centauro systemd[2883]: org.gnome.SettingsDaemon.Keyboard.service: Failed with result 'exit-code'.
out 27 10:35:15 centauro systemd[2883]: Failed to start org.gnome.SettingsDaemon.Keyboard.service - GNOME keyboard configuration service.
out 27 10:35:15 centauro systemd[2883]: org.gnome.SettingsDaemon.Power.service: Failed with result 'exit-code'.
out 27 10:35:15 centauro systemd[2883]: Failed to start org.gnome.SettingsDaemon.Power.service - GNOME power management service.
out 27 10:35:15 centauro systemd[2883]: org.gnome.SettingsDaemon.MediaKeys.service: Failed with result 'exit-code'.
out 27 10:35:15 centauro systemd[2883]: Failed to start org.gnome.SettingsDaemon.MediaKeys.service - GNOME keyboard shortcuts service.
out 27 10:35:15 centauro systemd[2883]: org.gnome.SettingsDaemon.Wacom.service: Failed with result 'exit-code'.
out 27 10:35:15 centauro systemd[2883]: Failed to start org.gnome.SettingsDaemon.Wacom.service - GNOME Wacom tablet support service.
Edit: Seems it's caused by the Vitals extension and not by the power state:
User Logs:
--nov 21 19:21:28 centauro gnome-shell[20588]: Running GNOME Shell (using mutter 45.1) as a Wayland display server
nov 21 19:21:28 centauro gnome-shell[20588]: Enabling experimental feature 'kms-modifiers'
nov 21 19:21:28 centauro gnome-shell[20588]: Enabling experimental feature 'rt-scheduler'
nov 21 19:21:28 centauro gnome-shell[20588]: Enabling experimental feature 'autoclose-xwayland'
nov 21 19:21:28 centauro gnome-shell[20588]: Made thread 'KMS thread' realtime scheduled
nov 21 19:21:28 centauro gnome-shell[20588]: Device '/dev/dri/card1' prefers shadow buffer
nov 21 19:21:28 centauro gnome-shell[20588]: Added device '/dev/dri/card1' (nvidia-drm) using atomic mode setting.
nov 21 19:21:28 centauro gnome-shell[20588]: Device '/dev/dri/card0' prefers shadow buffer
nov 21 19:21:28 centauro gnome-shell[20588]: Added device '/dev/dri/card0' (i915) using atomic mode setting.
nov 21 19:21:28 centauro gnome-shell[20588]: Created gbm renderer for '/dev/dri/card1'
nov 21 19:21:28 centauro gnome-shell[20588]: Created gbm renderer for '/dev/dri/card0'
nov 21 19:21:28 centauro gnome-shell[20588]: Boot VGA GPU /dev/dri/card0 selected as primary
nov 21 19:21:28 centauro gnome-shell[20588]: Obtained a high priority EGL context
nov 21 19:21:28 centauro gnome-shell[20588]: Obtained a high priority EGL context
nov 21 19:21:28 centauro gnome-shell[20588]: Using public X11 display :0, (using :1 for managed services)
nov 21 19:21:28 centauro gnome-shell[20588]: Using Wayland display name 'wayland-0'
nov 21 19:21:28 centauro gnome-shell[20588]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
nov 21 19:21:28 centauro gnome-shell[20588]: Will monitor session 5
nov 21 19:21:29 centauro gnome-shell[20588]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
nov 21 19:21:29 centauro gnome-shell[20588]: st_widget_get_theme_node called on the widget [0x56054db99240 StBoxLayout ("…")] which is not in the stage.
nov 21 19:21:29 centauro gnome-shell[20588]: st_widget_get_theme_node called on the widget [0x56054db9b990 StLabel.vitals-panel-label:insensitive ("…")] which is not in the stage.
nov 21 19:21:29 centauro gnome-shell[20588]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
--
The RedHat Bugzilla also contains the backtrace: https://bugzilla.redhat.com/show_bug.cgi?id=2250968