gnome-shell frozen during / after GDM login
Affected version
- Operating System: Fedora Linux 39.20231222.0 (Silverblue)
- Gnome Shell Version: 45.2
- Gjs Version: 1.78.1
- $WAYLAND_DISPLAY: wayland-0
- Enabled extensions: none
Bug summary
Recently after boot GDM and Gnome Shell often freezes and/or broken. The top bar might overlap with application windows and not clickable.
Steps to reproduce
Boot Fedora Silverblue and login
Relevant logs, screenshots, screencasts etc.
Log from journalctl --boot --no-hostname _CMDLINE=/usr/bin/gnome-shell
has 299893 lines, compressed and attached.
gnome-shell.log.gz
This is the beginning of the logs:
Dec 22 20:15:55 gnome-shell[1567]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Dec 22 20:16:06 gnome-shell[1567]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
The offending signal was notify on Gjs_status_backlight_SliderItem 0x55ddfe16ca40.
== Stack trace for context 0x55ddfc45acb0 ==
#0 7ffc8caf8e40 I resource:///org/gnome/shell/ui/status/backlight.js:57 (3d0af0428e20 @ 131)
#1 7ffc8caf9990 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:687 (22316a79bec0 @ 25)
#2 7ffc8caf99d0 I resource:///org/gnome/shell/ui/status/backlight.js:197 (3d0af042c3d0 @ 199)
#3 7ffc8caf9a00 I resource:///org/gnome/shell/ui/status/backlight.js:157 (3d0af042c290 @ 12)
#4 55ddfc5269f8 i resource:///org/gnome/shell/ui/init.js:21 (22316a770ba0 @ 48)
Dec 22 20:16:06 gnome-shell[1567]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
The offending callback was AsyncReadyCallback().
== Stack trace for context 0x55ddfc45acb0 ==
#0 55ddfc5269f8 i resource:///org/gnome/shell/ui/init.js:21 (22316a770ba0 @ 48)
Dec 22 20:16:06 gnome-shell[1567]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
The offending signal was g-properties-changed on GDBusProxy 0x55ddfe167a80.
== Stack trace for context 0x55ddfc45acb0 ==
#0 55ddfc5269f8 i resource:///org/gnome/shell/ui/init.js:21 (22316a770ba0 @ 48)
Dec 22 20:16:06 gnome-shell[1567]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
The offending callback was AsyncReadyCallback().
== Stack trace for context 0x55ddfc45acb0 ==
#0 55ddfc5269f8 i resource:///org/gnome/shell/ui/init.js:21 (22316a770ba0 @ 48)
Dec 22 20:16:06 gnome-shell[1567]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
The offending signal was g-properties-changed on GDBusProxy 0x55ddfe167a80.
== Stack trace for context 0x55ddfc45acb0 ==
#0 55ddfc5269f8 i resource:///org/gnome/shell/ui/init.js:21 (22316a770ba0 @ 48)
Dec 22 20:16:06 gnome-shell[1567]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
The offending callback was AsyncReadyCallback().
== Stack trace for context 0x55ddfc45acb0 ==
#0 55ddfc5269f8 i resource:///org/gnome/shell/ui/init.js:21 (22316a770ba0 @ 48)
Dec 22 20:16:06 gnome-shell[1567]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
The offending signal was g-properties-changed on GDBusProxy 0x55ddfe167a80.
== Stack trace for context 0x55ddfc45acb0 ==
#0 55ddfc5269f8 i resource:///org/gnome/shell/ui/init.js:21 (22316a770ba0 @ 48)
Dec 22 20:16:06 gnome-shell[1567]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
The offending callback was AsyncReadyCallback().
== Stack trace for context 0x55ddfc45acb0 ==
#0 55ddfc5269f8 i resource:///org/gnome/shell/ui/init.js:21 (22316a770ba0 @ 48)
Dec 22 20:16:06 gnome-shell[1567]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
The offending signal was g-properties-changed on GDBusProxy 0x55ddfe167a80.
== Stack trace for context 0x55ddfc45acb0 ==
#0 55ddfc5269f8 i resource:///org/gnome/shell/ui/init.js:21 (22316a770ba0 @ 48)