Sounds similar but different to bug 1908429. The "offending" signal/callbacks are different.
** Summary changed: - [Solved] Gnome desktop freezes after reboot or resume after sleep + Attempting to call back into JSAPI during the sweeping phase of GC [resource:///org/gnome/shell/ui/calendar.js:320] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1994125 Title: Attempting to call back into JSAPI during the sweeping phase of GC [resource:///org/gnome/shell/ui/calendar.js:320] Status in gnome-shell package in Ubuntu: Confirmed Bug description: After a reboot or resuming from sleep, the desktop appears and is fully functional for about 20 seconds. Then the desktop freezes, the fan spins up but the mouse still moves. Now click around, open programs, execute <Alt><Tab> to switch programs does nothing. The system stays this way for 60 seconds. Then the desktop becomes responsive again and all click and keystrokes executed during this time are executed. After that the system stays responsive and normal. The system log fills up with the following lines (many of them) during this period, pointing at a gnome javascript / message queue issue : ``` Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: 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. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is mos t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be cau sed by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: 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. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is mos t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be cau sed by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: 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. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). ``` ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: robert 2224 F.... wireplumber /dev/snd/controlC1: robert 2224 F.... wireplumber /dev/snd/seq: robert 2221 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 09:49:23 2022 InstallationDate: Installed on 2022-10-23 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC Bus 001 Device 002: ID 1d57:ad03 Xenta [T3] 2.4GHz and IR Air Mouse Remote Control Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=0c55150a-14de-418b-b87f-c46b8f0ef3e7 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2018 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16Q2IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-16Q2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16Q2IMS.10E:bd08/27/2018:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGS65StealthThin8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16Q2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16Q2.1: dmi.product.family: GS dmi.product.name: GS65 Stealth Thin 8RF dmi.product.sku: 16Q2.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1994125/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
