Flood of "Attempting to call back into JSAPI during the sweeping phase of GC" messages
Gnome Shell 43.0 Wayland, Ubuntu 22.10, in my syslog I find a flood of
Nov 18 21:30:07 pc gnome-shell[2139]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was access-point-removed on NMDeviceWifi 0x55ccd870c3f0.
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was notify on NMDeviceWifi 0x55ccd870c3f0.
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was notify on NMDeviceWifi 0x55ccd870c3f0.
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<StIcon>:0x55ccd9add880] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<ClutterActor>:0x55ccd93b4640] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<Gjs_ui_windowPreview_WindowPreview>:0x55ccd9bad5c0] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<ClutterActor>:0x55ccd9bcecd0] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<ClutterClone>:0x55ccd9b7b810] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<StIcon>:0x55ccd73f4c70] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<ClutterActor>:0x55ccd938e380] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<Gjs_ui_windowPreview_WindowPreview>:0x55ccd9307cc0] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<ClutterActor>:0x55ccd76088c0] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<ClutterClone>:0x55ccd9b7b170] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<StIcon>:0x55ccd968bc90] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<ClutterActor>:0x55ccd974bb00] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<Gjs_ui_windowPreview_WindowPreview>:0x55ccd9a1d540] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<ClutterActor>:0x55ccd974a4b0] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<ClutterClone>:0x55ccd97224c0] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<StIcon>:0x55ccd722c150] is on because it needs an allocation.
Nov 18 21:27:10 pc gnome-shell[2139]: Can't update stage views actor <unnamed>[<ClutterActor>:0x55ccd93b4ca0] is on because it needs an allocation.
Nov 18 21:27:14 pc gnome-shell[2139]: Failed to set the markup of the actor '<unnamed>[<ClutterText>:0x55ccd9d7e4f0]': Error on line 1 char 14: “<” is not a valid name
Nov 18 21:27:14 pc gnome-shell[2139]: Failed to set the markup of the actor '<unnamed>[<ClutterText>:0x55ccd9d97bb0]': Error on line 1 char 14: “<” is not a valid name
Nov 18 21:27:33 pc gnome-shell[2139]: JS ERROR: Error: Argument descendant may not be null
_onCapturedEvent@resource:///org/gnome/shell/ui/keyboard.js:232:24
Nov 18 21:27:35 pc gnome-shell[2139]: (../clutter/clutter/clutter-actor.c:12145):clutter_actor_event: runtime check failed: (retval == CLUTTER_EVENT_PROPAGATE)
Nov 18 21:27:46 pc firefox-bin[2852]: Couldn't map window 0x7ffb61db70a0 as subsurface because its parent is not mapped.
Nov 18 21:28:41 pc pkexec[8740]: pam_unix(polkit-1:session): session opened for user root(uid=0) by (uid=1000)
Nov 18 21:29:59 pc gnome-shell[2139]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
Nov 18 21:30:01 pc gnome-session-binary[2122]: Entering running state
Nov 18 21:30:01 pc at-spi2-registr[2218]: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client
Nov 18 21:30:01 pc at-spi2-registr[2218]: Unable to register client with session manager
Nov 18 21:30:03 pc gnome-shell[2139]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
Nov 18 21:30:07 pc gnome-shell[2139]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was access-point-removed on NMDeviceWifi 0x55ccd870c3f0.
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was notify on NMDeviceWifi 0x55ccd870c3f0.
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was notify on NMDeviceWifi 0x55ccd870c3f0.
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was notify on NMDeviceWifi 0x55ccd870c3f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was notify on NMAccessPoint 0x7fd6a0005da0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was notify on NMAccessPoint 0x7fd6a0005da0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was notify on NMAccessPoint 0x7fd6a0005da0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was notify on NMActiveConnection 0x55ccd8710500.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was notify on NMActiveConnection 0x55ccd8710500.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was state-changed on NMDeviceWifi 0x55ccd870c3f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was state-changed on NMDeviceWifi 0x55ccd870c3f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ccd960df80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ccd960df80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ccd960df80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd94f2070.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd94f2070.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd94f2070.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd94f2070.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd9493ad0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd960df80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd949d180.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd949d180.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd949d180.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd949d180.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd9478710.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd960df80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd94ef470.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd94ef470.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd94ef470.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd94ef470.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd9889830.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd960df80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd7ccf240.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd7ccf240.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd7ccf240.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd7ccf240.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd7cc0530.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd960df80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd7ce18f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd7ce18f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd7ce18f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd7ce18f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd95c3750.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd960df80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd7ceb2d0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd7ceb2d0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd7ceb2d0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd7ceb2d0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd76394d0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd960df80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9513ed0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9513ed0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9513ed0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9513ed0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd787d590.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd960df80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9522bf0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9522bf0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9522bf0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9522bf0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd830e300.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd960df80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9756680.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9756680.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9756680.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9756680.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd6ef7c40.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd960df80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 th>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending callback was set_container(), a vfunc.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 th>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending callback was set_container(), a vfunc.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ccd9753bd0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ccd9753bd0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ccd9753bd0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9876770.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9876770.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9876770.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9876770.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd96ae140.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd9753bd0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd988f000.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd988f000.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd988f000.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd988f000.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd9811c20.
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd9753bd0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd8427430.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd8427430.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd8427430.
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd8427430.
Nov 18 21:30:09 pc gnome-shell[2139]: == Stack trace for context 0x55ccd6f2f7d0 ==
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd96a8e40.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd9753bd0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9167b30.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9167b30.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9167b30.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd9167b30.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd95fb6e0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd9753bd0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd949b740.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd949b740.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd949b740.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd949b740.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd9912730.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd9753bd0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd948db60.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd948db60.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd948db60.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd948db60.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd94ee1f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd9753bd0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd82e30d0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd82e30d0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd82e30d0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd82e30d0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd7ca98c0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd9753bd0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 th>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending callback was set_container(), a vfunc.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 th>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending callback was set_container(), a vfunc.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ccd979a580.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ccd979a580.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ccd979a580.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd95306f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd95306f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd95306f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd95306f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd942ed80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd979a580.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd96b69b0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd96b69b0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd96b69b0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd96b69b0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd946e5e0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd979a580.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 th>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending callback was set_container(), a vfunc.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 th>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending callback was set_container(), a vfunc.
Nov 18 21:30:09 pc update-notifier[3215]: Error reading events from display: Broken pipe
Nov 18 21:30:09 pc dconf-editor[7397]: Error reading events from display: Broken pipe
Nov 18 21:30:09 pc xdg-desktop-por[2442]: Error reading events from display: Broken pipe
Nov 18 21:30:09 pc gnome-terminal-[5983]: Error reading events from display: Broken pipe
Nov 18 21:30:09 pc Web Content[6326]: Error reading events from display: Broken pipe
Nov 18 21:30:09 pc xdg-desktop-por[6523]: Error reading events from display: Broken pipe
Nov 18 21:30:09 pc gnome-text-edit[6598]: Error reading events from display: Broken pipe
Nov 18 21:30:09 pc nautilus[6535]: Error reading events from display: Broken pipe
Nov 18 21:30:09 pc thunderbird[6230]: Error reading events from display: Broken pipe
Nov 18 21:30:09 pc firefox-bin[2852]: Error reading events from display: Broken pipe
Nov 18 21:30:09 pc systemd[1938]: vte-spawn-44827c35-03b1-4145-afcd-05bd339dbea5.scope: Consumed 4.940s CPU time.
Nov 18 21:30:09 pc systemd[1938]: vte-spawn-1e11777f-669e-4528-9649-11609f40d5a9.scope: Consumed 1.624s CPU time.
Nov 18 21:30:09 pc systemd[1938]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
Nov 18 21:30:09 pc systemd[1938]: gnome-terminal-server.service: Failed with result 'exit-code'.
Nov 18 21:30:09 pc systemd[1938]: gnome-terminal-server.service: Consumed 21.644s CPU time.
Nov 18 21:30:09 pc systemd[1938]: xdg-desktop-portal-gnome.service: Main process exited, code=exited, status=1/FAILURE
Nov 18 21:30:09 pc systemd[1938]: xdg-desktop-portal-gnome.service: Failed with result 'exit-code'.
Nov 18 21:30:09 pc systemd[1938]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Nov 18 21:30:09 pc systemd[1938]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Nov 18 21:30:09 pc systemd[1938]: app-gnome-update\x2dnotifier-3215.scope: Consumed 5.287s CPU time.
Nov 18 21:30:09 pc systemd[1938]: org.gnome.Shell@wayland.service: Consumed 7min 8.969s CPU time.
Nov 18 21:30:09 pc systemd[1938]: app-flatpak-org.gnome.TextEditor-6588.scope: Consumed 3.173s CPU time.
Nov 18 21:30:09 pc systemd[1938]: Stopped target GNOME Wayland Session (session: gnome).
Nov 18 21:30:09 pc systemd[1938]: Stopped target Current graphical user session.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[8205]: Exiting due to channel error.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[3992]: Exiting due to channel error.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[7329]: Exiting due to channel error.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[3179]: Exiting due to channel error.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[3143]: Exiting due to channel error.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[5584]: Exiting due to channel error.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[4645]: Exiting due to channel error.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[3078]: Exiting due to channel error.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[7287]: Exiting due to channel error.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[3989]: Exiting due to channel error.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[4749]: Exiting due to channel error.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[3008]: Exiting due to channel error.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[4097]: Exiting due to channel error.
Nov 18 21:30:09 pc systemd[1938]: Stopped Path trigger for Apport crash notifications.
Nov 18 21:30:09 pc org.mozilla.firefox.desktop[2955]: Exiting due to channel error.
Nov 18 21:30:09 pc systemd[1938]: Stopped Path trigger for new release of Ubuntu notifications.
Nov 18 21:30:09 pc systemd[1938]: Stopped target GNOME Session.
Nov 18 21:30:09 pc systemd[1938]: Stopped target GNOME Wayland Session.
Nov 18 21:30:09 pc systemd[1938]: Stopped target GNOME Session (session: gnome).
Nov 18 21:30:09 pc systemd[1938]: Stopped target GNOME accessibility target.
Nov 18 21:30:09 pc systemd[1938]: Stopped target GNOME color management target.
Nov 18 21:30:09 pc systemd[1938]: Stopped target GNOME date & time target.
Nov 18 21:30:09 pc systemd[1938]: Stopped target GNOME maintenance of expirable data target.
Nov 18 21:30:09 pc systemd[1938]: Stopped target GNOME keyboard configuration target.
Nov 18 21:30:09 pc systemd[1938]: Stopped target GNOME keyboard shortcuts target.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd95306f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd95306f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd95306f0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd942ed80.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd979a580.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd96b69b0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd96b69b0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd96b69b0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ccd96b69b0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ccd946e5e0.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 connect>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ccd979a580.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 th>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending callback was set_container(), a vfunc.
Nov 18 21:30:09 pc gnome-shell[2139]: 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 th>
Nov 18 21:30:09 pc gnome-shell[2139]: The offending callback was set_container(), a vfunc.