Gnome Crashes when opening secondary windows in Wayland
Affected version
- Hardware Model: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401IV_GA401IV
- OS Name: Fedora Linux 37.20221208.0 (Silverblue) (although I already experienced this in 36)
- Gnome Version: 43.1 (although I already experienced this in 42)
- Windowing System: Wayland
Bug summary
Gnome crashes and freezes (can only be fixed by Alt + F3 and rebooting) when opening secondary?/sub? windows, such as when opening the calendar event editor view window in Thunderbird, the document properties window in LibreOffice, the preferences window in Gnome Editor. When opening such a secondary window, there is about a 90% chance that Gnome freezes and becomes unusable. If I am lucky, then sometimes the window opens without crashing.
Steps to reproduce
The issue can be reproduced with a number of difference programs. I have personally experienced it with Thunderbird, LibreOffice, and Gnome Editor.
Gnome Editor (for which I have also attached logs):
- Open Gnome Editor
- Open the menu and press "Preferences"
What did you expect to happen
Instead of Gnome crashing, it should simply open the corresponding window.
Logs
The logs are very long (same message spammed over and over again), so I will attach it as a file.
journalctl -b -1 | grep gnome-shell >> Documents/gnome-crash.log
Highlights:
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was notify on MetaWindowActorWayland 0x55890d459850.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was size-changed on ShellWM 0x7f7130010320.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was notify on ShellWindowPreviewLayout 0x55890d79f4c0.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x558907362040.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x558907362040.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x558907362040.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x558907362040.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x558907362040.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x558907362040.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x558907362040.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x558907362040.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x558907362040.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x558907362040.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x558907362040.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x558907362040.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x558907362040.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: 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.
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: == Stack trace for context 0x5589070d7490 ==
Dec 09 14:14:13 nichols-ve701-0500.eduroam.wlan.private.upenn.edu gnome-shell[2169]: The offending signal was window-left-monitor on MetaDisplay 0x5589073620[gnome-crash.log](/uploads/73e8ef5e10c40e5825e0776323604465/gnome-crash.log)