Gnome Shell crashing when starting Counter-Strike Global Offensive (native)
After update to 3.34.0 gnome-shell begins to output lots of errors once CSGO is started and the screen is flickering constantly until its forcefully closed some way.
Journal is full of these messages:
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 7ffff86eec90 I resource:///org/gnome/shell/ui/popupMenu.js:753 (7f0440b1e4c0 @ 81)
Sep 21 15:22:21 gnome-shell[2492]: #1 7ffff86eed40 I resource:///org/gnome/shell/ui/panel.js:165 (7f0440a87820 @ 30)
Sep 21 15:22:21 gnome-shell[2492]: #2 7ffff86eed40 I resource:///org/gnome/shell/ui/panel.js:147 (7f0440a875e0 @ 174)
Sep 21 15:22:21 gnome-shell[2492]: #3 7ffff86eed40 I resource:///org/gnome/shell/ui/panel.js:385 (7f0440a89160 @ 561)
Sep 21 15:22:21 gnome-shell[2492]: #4 7ffff86eed40 I resource:///org/gnome/shell/ui/panel.js:332 (7f0440a89040 @ 105)
Sep 21 15:22:21 gnome-shell[2492]: #5 7ffff86eed90 I self-hosted:979 (7f0440928af0 @ 440)
Sep 21 15:22:21 gnome-shell[2492]: #6 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was destroy on Gjs_PopupMenuItem 0x55eb3d612070.
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: #0 55eb2c5877e0 i resource:///org/gnome/shell/ui/closeDialog.js:188 (7f0440a5cca0 @ 37)
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending callback was focus(), a vfunc.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending callback was get_preferred_width(), a vfunc.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending callback was get_preferred_height(), a vfunc.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on Gjs_Dialog 0x55eb38661c60.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending callback was get_preferred_height(), a vfunc.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending callback was get_preferred_width(), a vfunc.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending callback was get_preferred_width(), a vfunc.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: Window manager warning: last_focus_time (4767418) is greater than comparison timestamp (4737205). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was enter-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending callback was focus(), a vfunc.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending callback was gesture_prepare(), a vfunc.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending callback was gesture_prepare(), a vfunc.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending callback was gesture_prepare(), a vfunc.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was kill-window-effects on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was size-change on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was size-changed on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was kill-window-effects on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was size-change on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was size-changed on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was kill-window-effects on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was size-change on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was size-changed on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was kill-window-effects on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was size-change on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was size-changed on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was kill-window-effects on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was size-change on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was size-changed on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was stream-removed on GvcMixerControl 0x55eb2cd10990.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending callback was SourceFunc().
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was g-signal on GDBusProxy 0x55eb2cd2e340.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was g-signal on GDBusProxy 0x55eb2d6d7f10.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was g-signal on GDBusProxy 0x55eb2d6d7fa0.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was g-signal on GDBusProxy 0x55eb2cd2e340.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was g-signal on GDBusProxy 0x55eb2d6d7f10.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was g-signal on GDBusProxy 0x55eb2d6d7fa0.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was enter-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was enter-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was enter-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was enter-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was stream-added on GvcMixerControl 0x55eb2cd10990.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was size-changed on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was kill-window-effects on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was minimize on ShellWM 0x55eb2bb0dc00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on ShellWindowTracker 0x55eb2bd33120.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was notify on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was in-fullscreen-changed on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was in-fullscreen-changed on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was in-fullscreen-changed on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was in-fullscreen-changed on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was restacked on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was restacked on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was restacked on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was restacked on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was restacked on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was captured-event on MetaStage 0x55eb2b691f00.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was restacked on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was restacked on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was restacked on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was restacked on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was restacked on MetaDisplay 0x55eb2b986020.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was stopped on ClutterPropertyTransition 0x55eb38cb5cb0.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was g-signal on GDBusProxy 0x55eb2cd2e340.
Sep 21 15:22:21 gnome-shell[2492]: == Stack trace for context 0x55eb2b6a2550 ==
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was g-signal on GDBusProxy 0x55eb2d6d7f10.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was g-signal on GDBusProxy 0x55eb2d6d7fa0.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was g-signal on GDBusProxy 0x55eb2cd2e340.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was g-signal on GDBusProxy 0x55eb2d6d7f10.
Sep 21 15:22:21 gnome-shell[2492]: 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.
Sep 21 15:22:21 gnome-shell[2492]: The offending signal was g-signal on GDBusProxy 0x55eb2d6d7fa0.
Edited by MaxXor