Public bug reported:
As title says: sometimes when I disconnect my laptop from DisplayPort-
over-USBC monitor desktop goes to black screen (sometimes with cursor
available, but only the cursor!), and over the time I've found out that
opening a tty session and executing a `killall gnome-shell` brings
system back to life! It looks very glitchy but it helps.
The only relevant part I've found out is this part of the log. It's an
extremely long thread of similar but mixed messages like:
```
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
```
...and there are really a lot of those!
I've did a small count over today's bug and here are the summaries:
```
85000 == Stack trace for context 0x641018d41170 ==
29999 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.
29998 The offending callback was SourceFunc().
12501 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.
2680 The offending signal was window-left-monitor on MetaDisplay
0x641018e6a160.
2320 The offending signal was window-entered-monitor on MetaDisplay
0x641018e6a160.
...
```
Looks scary! Text log of gnome-shell (as captured by journalctl via
systemd --user) is around 26MB.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2.1
ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-45-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 31 17:37:18 2024
DisplayManager: gdm3
InstallationDate: Installed on 2022-04-19 (834 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
RelatedPackageVersions: mutter-common 42.9-0ubuntu8
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-08-21 (709 days ago)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
** Description changed:
As title says: sometimes when I disconnect my laptop from DisplayPort-
over-USBC monitor desktop goes to black screen (sometimes with cursor
available, but only the cursor!), and over the time I've found out that
opening a tty session and executing a `killall gnome-shell` brings
system back to life! It looks very glitchy but it helps.
- The only relevant part I've found out is this part of the log. It's an
extremely long thread of similar but mixed messages like:
+ The only relevant part I've found out is this part of the log. It's an
+ extremely long thread of similar but mixed messages like:
+
```
-
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: == Stack trace for context
0x641018d41170 ==
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: 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.
+ июл 31 15:31:02 MUNIT-517 gnome-shell[3683]: The offending signal was
window-entered-monitor on MetaDisplay 0x641018e6a160.
```
...and there are really a lot of those!
I've did a small count over today's bug and here are the summaries:
```
- 85000 == Stack trace for context 0x641018d41170 ==
- 29999 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.
- 29998 The offending callback was SourceFunc().
- 12501 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.
- 2680 The offending signal was window-left-monitor on MetaDisplay
0x641018e6a160.
- 2320 The offending signal was window-entered-monitor on MetaDisplay
0x641018e6a160.
+ 85000 == Stack trace for context 0x641018d41170 ==
+ 29999 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.
+ 29998 The offending callback was SourceFunc().
+ 12501 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.
+ 2680 The offending signal was window-left-monitor on MetaDisplay
0x641018e6a160.
+ 2320 The offending signal was window-entered-monitor on MetaDisplay
0x641018e6a160.
...
```
Looks scary! Text log of gnome-shell (as captured by journalctl via
systemd --user) is around 26MB.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2.1
ProcVersionSignature: Ubuntu 6.5.0-45.45~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-45-generic x86_64
NonfreeKernelModules: zfs nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 31 17:37:18 2024
DisplayManager: gdm3
InstallationDate: Installed on 2022-04-19 (834 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
RelatedPackageVersions: mutter-common 42.9-0ubuntu8
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-08-21 (709 days ago)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075350
Title:
gnome-shell seems to hang on monitor disconnect, killing gnome-shell
process helps to bring system to life
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2075350/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
