"metacity --replace &" on gnome 3.36.2 causes a crash / logout
Affected version
Ubuntu 20.04
Gnome-shell 3.36.2
Metacity 3.36.1
Bug summary
Running metacity --replace &
crashes/logout of the current session. This works fine on Ubuntu 18.04 with gnome-shell 3.28.4 and metacity 3.28.0
Steps to reproduce
- Install Metacity (Ubuntu 20.04 doesn't ship with gnome flashback metacity)
- Run
metacity --replace &
What happened
There is some type of crash and you are presented with the error/logout dialog.
What did you expect to happen
I expected the running window manager to be replaced with Metacity
Relevant logs, screenshots, screencasts etc.
Jun 24 14:44:31 Ubuntu-20-001 systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 24 14:44:31 Ubuntu-20-001 dbus-daemon[778]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 24 14:44:31 Ubuntu-20-001 systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 24 14:44:42 Ubuntu-20-001 systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jun 24 14:46:07 Ubuntu-20-001 gnome-shell[5012]: Object Meta.BackgroundActor (0x559b21020f70), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
Jun 24 14:46:07 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:07 Ubuntu-20-001 gnome-shell[5012]: #0 7fff002d9cd0 b resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (1a95695b6c40 @ 25)
Jun 24 14:46:07 Ubuntu-20-001 gnome-shell[5012]: #1 559b25cec3d0 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209 (21ba4ae9fb50 @ 85)
Jun 24 14:46:07 Ubuntu-20-001 gnome-shell[5012]: #2 559b25cec348 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148 (21ba4ae9f970 @ 12)
Jun 24 14:46:07 Ubuntu-20-001 gnome-shell[5012]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
_init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24
_onDestroy@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:209:45
_init/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:148:44
Jun 24 14:46:07 Ubuntu-20-001 gnome-shell[5012]: JS ERROR: TypeError: actor.get_meta_window(...) is null
_destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1578:32
onStopped@resource:///org/gnome/shell/ui/windowManager.js:1548:39
_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13
_easeActor/<@resource:///org/gnome/shell/ui/environment.js:149:56
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x559b227f0100.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b228ff690.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b228ff690.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b203cfa70.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b2149dc90.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b2149dc90.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b204f5470.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b22776a50.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b22776a50.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b21a88220.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b25353140.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: == Stack trace for context 0x559b1fae1640 ==
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b25353140.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b21a5b590.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b208d8760.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b208d8760.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b1fe4ff60.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b21aaa570.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b21aaa570.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b20ee2180.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b22913090.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b22913090.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b203c1470.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b223d7090.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b223d7090.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b20c3d7c0.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b25bf6c90.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b25bf6c90.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b208d3db0.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b228bfa60.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b228bfa60.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b20617440.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b25cf3bb0.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b25cf3bb0.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b22816ec0.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b204e2c90.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b204e2c90.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b20059920.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b20625490.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b20625490.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b20629670.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b204f8a90.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b204f8a90.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b204fd670.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b209d7400.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b209d7400.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b223af870.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b20638a90.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b20638a90.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b25451270.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b2545c890.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559b2545c890.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559b203c8870.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x559b22762190.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was notify on NMDeviceEthernet 0x559b22374270.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was notify on NMActiveConnection 0x559b22378180.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was notify on NMActiveConnection 0x559b22378180.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: Attempting to call back into 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.
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5012]: The offending signal was state-changed on NMDeviceEthernet 0x559b22374270.
Jun 24 14:46:08 Ubuntu-20-001 ibus-daemon[5044]: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes.
Jun 24 14:46:08 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Succeeded.
Jun 24 14:46:08 Ubuntu-20-001 polkitd(authority=local)[797]: Unregistered Authentication Agent for unix-session:12 (system bus name :1.303, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_CA.UTF-8) (disconnected from bus)
Jun 24 14:46:08 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 1.
Jun 24 14:46:08 Ubuntu-20-001 systemd[1410]: Stopped target GNOME X11 Session (session: ubuntu).
Jun 24 14:46:08 Ubuntu-20-001 systemd[1410]: Stopping GNOME X11 Session (session: ubuntu).
Jun 24 14:46:08 Ubuntu-20-001 systemd[1410]: Stopped target GNOME X11 Session.
Jun 24 14:46:08 Ubuntu-20-001 systemd[1410]: Stopping GNOME X11 Session.
Jun 24 14:46:08 Ubuntu-20-001 systemd[1410]: Stopped target GNOME Shell on X11.
Jun 24 14:46:08 Ubuntu-20-001 systemd[1410]: Stopping GNOME Shell on X11.
Jun 24 14:46:08 Ubuntu-20-001 systemd[1410]: Stopped GNOME Shell on X11.
Jun 24 14:46:08 Ubuntu-20-001 systemd[1410]: Starting GNOME Shell on X11...
Jun 24 14:46:08 Ubuntu-20-001 gnome-shell[5650]: Failed to use stored monitor configuration: Invalid mode 3213x1937 (59.999310) for monitor 'unknown unknown'
Jun 24 14:46:08 Ubuntu-20-001 gsd-media-keys[5163]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell
Jun 24 14:46:09 Ubuntu-20-001 gnome-shell[5650]: Failed to init X11 display: Failed to acquire window manager ownership
Jun 24 14:46:09 Ubuntu-20-001 gnome-shell[5650]: Window manager warning: Display “:0” already has a window manager; try using the --replace option to replace the current window manager.GNOME Shell crashed with signal 5
Jun 24 14:46:09 Ubuntu-20-001 gnome-shell[5650]: == Stack trace for context 0x55e7f73326a0 ==
Jun 24 14:46:09 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP
Jun 24 14:46:09 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Failed with result 'core-dump'.
Jun 24 14:46:09 Ubuntu-20-001 systemd[1410]: Failed to start GNOME Shell on X11.
Jun 24 14:46:09 Ubuntu-20-001 systemd[1410]: Dependency failed for GNOME Shell on X11.
Jun 24 14:46:09 Ubuntu-20-001 systemd[1410]: Dependency failed for GNOME X11 Session.
Jun 24 14:46:09 Ubuntu-20-001 systemd[1410]: Dependency failed for GNOME X11 Session (session: ubuntu).
Jun 24 14:46:09 Ubuntu-20-001 systemd[1410]: gnome-session-x11@ubuntu.target: Job gnome-session-x11@ubuntu.target/start failed with result 'dependency'.
Jun 24 14:46:09 Ubuntu-20-001 systemd[1410]: gnome-session-x11.target: Job gnome-session-x11.target/start failed with result 'dependency'.
Jun 24 14:46:09 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.target: Job gnome-shell-x11.target/start failed with result 'dependency'.
Jun 24 14:46:09 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 2.
Jun 24 14:46:09 Ubuntu-20-001 systemd[1410]: Stopped GNOME Shell on X11.
Jun 24 14:46:09 Ubuntu-20-001 systemd[1410]: Starting GNOME Shell on X11...
Jun 24 14:46:09 Ubuntu-20-001 gnome-shell[5668]: Failed to use stored monitor configuration: Invalid mode 3213x1937 (59.999310) for monitor 'unknown unknown'
Jun 24 14:46:09 Ubuntu-20-001 gsd-media-keys[5163]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell
Jun 24 14:46:09 Ubuntu-20-001 gnome-shell[5668]: Failed to init X11 display: Failed to acquire window manager ownership
Jun 24 14:46:09 Ubuntu-20-001 gnome-shell[5668]: Window manager warning: Display “:0” already has a window manager; try using the --replace option to replace the current window manager.GNOME Shell crashed with signal 5
Jun 24 14:46:09 Ubuntu-20-001 gnome-shell[5668]: == Stack trace for context 0x55673b899640 ==
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Failed with result 'core-dump'.
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: Failed to start GNOME Shell on X11.
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3.
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: Stopped GNOME Shell on X11.
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: Starting GNOME Shell on X11...
Jun 24 14:46:10 Ubuntu-20-001 gnome-shell[5684]: Failed to use stored monitor configuration: Invalid mode 3213x1937 (59.999310) for monitor 'unknown unknown'
Jun 24 14:46:10 Ubuntu-20-001 gsd-media-keys[5163]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell
Jun 24 14:46:10 Ubuntu-20-001 gnome-shell[5684]: Failed to init X11 display: Failed to acquire window manager ownership
Jun 24 14:46:10 Ubuntu-20-001 gnome-shell[5684]: Window manager warning: Display “:0” already has a window manager; try using the --replace option to replace the current window manager.GNOME Shell crashed with signal 5
Jun 24 14:46:10 Ubuntu-20-001 gnome-shell[5684]: == Stack trace for context 0x55835de7c640 ==
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Main process exited, code=dumped, status=5/TRAP
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Failed with result 'core-dump'.
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: Failed to start GNOME Shell on X11.
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 4.
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: Stopped GNOME Shell on X11.
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Start request repeated too quickly.
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Failed with result 'core-dump'.
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: Failed to start GNOME Shell on X11.
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: gnome-shell-x11.service: Triggering OnFailure= dependencies.
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: Started GNOME Session Failed lockdown screen (user).
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: Reached target GNOME Session Failed.
Jun 24 14:46:10 Ubuntu-20-001 systemd[1410]: Condition check resulted in Disable GNOME Shell extensions after failure being skipped.
Jun 24 14:46:11 Ubuntu-20-001 gsd-media-keys[5163]: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed