-- Logs begin at Sat 2019-12-21 04:40:18 EST, end at Wed 2020-05-06 00:47:50 EDT. -- May 05 11:10:35 dipper systemd[3869]: Starting GNOME Shell on Wayland... May 05 11:10:35 dipper gnome-shell[4037]: Enabling experimental feature 'scale-monitor-framebuffer' May 05 11:10:35 dipper gnome-shell[4037]: Enabling experimental feature 'x11-randr-fractional-scaling' May 05 11:10:36 dipper gnome-shell[4037]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. May 05 11:10:36 dipper gnome-shell[4037]: Will monitor session 2 May 05 11:10:36 dipper gnome-shell[4037]: Telepathy is not available, chat integration will be disabled. May 05 11:10:37 dipper systemd[3869]: Started GNOME Shell on Wayland. May 05 11:10:37 dipper gnome-shell[4037]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation May 05 11:10:37 dipper gnome-shell[4037]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). May 05 11:10:37 dipper gnome-shell[4037]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). May 05 11:10:37 dipper gnome-shell[4037]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). May 05 11:10:37 dipper gnome-shell[4037]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). May 05 11:10:37 dipper gnome-shell[4037]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). May 05 11:10:37 dipper gnome-shell[4037]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). May 05 11:10:37 dipper gnome-shell[4037]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). May 05 11:10:37 dipper gnome-shell[4037]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). May 05 11:10:37 dipper gnome-shell[4037]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). May 05 11:10:37 dipper ibus-daemon[4108]: 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. May 05 11:10:37 dipper gnome-shell[4037]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed May 05 11:10:37 dipper gnome-shell[4037]: JS ERROR: TypeError: src is null connectSmart4A@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/util.js:189:21 connectSmart@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/util.js:214:31 _init@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:325:14 _init@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/indicatorStatusIcon.js:42:25 _registerItem@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:95:22 _ensureItemRegistered@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:123:14 RegisterStatusNotifierItemAsync@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:169:14 _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:371:35 _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404:34 May 05 11:10:37 dipper gnome-shell[4037]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed May 05 11:10:37 dipper gnome-shell[4037]: JS ERROR: Exception in callback for signal: icon: TypeError: Gtk.IconTheme.get_default(...) is null _getIconInfo@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:453:31 _cacheOrCreateIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:367:25 _updateIconByType@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:574:18 _updateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:601:14 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:133:47 _onPropertiesChanged/<@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:220:22 _onPropertiesChanged@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:214:15 May 05 11:10:37 dipper gnome-shell[4630]: The XKEYBOARD keymap compiler (xkbcomp) reports: May 05 11:10:37 dipper gnome-shell[4630]: > Warning: Unsupported maximum keycode 569, clipping. May 05 11:10:37 dipper gnome-shell[4630]: > X11 cannot support keycodes above 255. May 05 11:10:37 dipper gnome-shell[4630]: > Internal error: Could not resolve keysym Invalid May 05 11:10:37 dipper gnome-shell[4630]: Errors from xkbcomp are not fatal to the X server May 05 11:10:38 dipper gnome-shell[4037]: GNOME Shell started at Tue May 05 2020 11:10:37 GMT-0400 (EDT) May 05 11:10:38 dipper gnome-shell[4037]: Registering session with GDM May 05 11:10:39 dipper gnome-shell[4037]: clutter_actor_set_child_at_index: assertion 'index_ <= self->priv->n_children' failed May 05 11:10:39 dipper gnome-shell[4037]: clutter_actor_set_child_at_index: assertion 'index_ <= self->priv->n_children' failed May 05 11:10:39 dipper gnome-shell[4037]: clutter_actor_set_child_at_index: assertion 'index_ <= self->priv->n_children' failed May 05 11:10:39 dipper gnome-shell[4037]: clutter_actor_set_child_at_index: assertion 'index_ <= self->priv->n_children' failed May 05 11:10:39 dipper gnome-shell[4037]: clutter_actor_set_child_at_index: assertion 'index_ <= self->priv->n_children' failed May 05 11:10:39 dipper gnome-shell[4037]: clutter_actor_set_child_at_index: assertion 'index_ <= self->priv->n_children' failed May 05 11:10:39 dipper gnome-shell[4037]: clutter_actor_set_child_at_index: assertion 'index_ <= self->priv->n_children' failed May 05 11:12:47 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:12:47 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:12:47 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:12:47 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:12:47 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:12:47 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:12:47 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:12:47 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:12:47 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:12:47 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:12:47 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:12:47 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:12:47 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:12:47 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:12:47 dipper gnome-shell[4037]: The offending signal was notify on Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock 0x5632ca8598d0. May 05 11:12:47 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:12:47 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:12:47 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:12:47 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:12:47 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:12:47 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:12:47 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:12:47 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:12:47 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:12:47 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:12:47 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:12:47 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:12:47 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:12:47 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:12:47 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:12:47 dipper gnome-shell[4037]: The offending signal was filter-keybinding on ShellWM 0x5632c8449020. May 05 11:12:47 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:12:47 dipper gnome-shell[4037]: The offending signal was overlay-key on MetaDisplay 0x5632c843a000. May 05 11:12:47 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:12:47 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:12:47 dipper gnome-shell[4037]: The offending signal was last-device-changed on MetaBackendNative 0x5632c7fab170. May 05 11:14:08 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:08 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:08 dipper gnome-shell[4037]: #0 7fff4bd4bb60 I /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/docking.js:119 (d122ccd0718 @ 1115) May 05 11:14:08 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:08 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:08 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:08 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:08 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:08 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:08 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:08 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:14:08 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:08 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:14:08 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:08 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:08 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:08 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:08 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:08 dipper gnome-shell[4037]: The offending callback was update_allocation(), a vfunc. May 05 11:14:08 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:08 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:08 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:08 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:14:08 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:08 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:14:08 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:08 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:08 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:08 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:08 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:08 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:08 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:08 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:08 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was update_allocation(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was notify on StWidget 0x5632c89b8a40. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was key-press-event on ClutterText 0x5632ca2115c0. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was key-press-event on ClutterText 0x5632ca2115c0. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was key-press-event on ClutterText 0x5632ca2115c0. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was key-press-event on ClutterText 0x5632ca2115c0. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:18 dipper gnome-shell[4037]: The offending signal was key-press-event on ClutterText 0x5632ca2115c0. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was update_allocation(), a vfunc. May 05 11:14:18 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:18 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:14:19 dipper gnome-shell[4037]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application May 05 11:14:19 dipper gnome-shell[4037]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0 May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was notify on Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock 0x5632ca8598d0. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was update_allocation(), a vfunc. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-properties-changed on GDBusProxy 0x5632ceee9130. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-properties-changed on GDBusProxy 0x5632ceee9130. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-properties-changed on GDBusProxy 0x5632ca7a9160. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:30 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:30 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:30 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:30 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was notify on Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock 0x5632ca8598d0. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was update_allocation(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was notify on StWidget 0x5632c89b8a40. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was filter-keybinding on ShellWM 0x5632c8449020. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was overlay-key on MetaDisplay 0x5632c843a000. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was key-press-event on MetaStage 0x5632c8356410. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was key-press-event on MetaStage 0x5632c8356410. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was key-press-event on MetaStage 0x5632c8356410. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was key-press-event on MetaStage 0x5632c8356410. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was filter-keybinding on ShellWM 0x5632c8449020. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was overlay-key on MetaDisplay 0x5632c843a000. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was filter-keybinding on ShellWM 0x5632c8449020. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was overlay-key on MetaDisplay 0x5632c843a000. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was update_allocation(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was notify on StBin 0x5632ca2809d0. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was notify on StBin 0x5632ca2809d0. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was notify on StBin 0x5632ca2809d0. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was notify on StBin 0x5632ca2809d0. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: The offending signal was notify on StBin 0x5632ca2809d0. May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:14:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:14:40 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:49 dipper gnome-shell[4037]: The offending signal was notify on Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock 0x5632ca8598d0. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was update_allocation(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:18:49 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:49 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:49 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:18:49 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:49 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:49 dipper gnome-shell[4037]: The offending signal was key-press-event on ClutterText 0x5632ca2115c0. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:49 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:49 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:49 dipper gnome-shell[4037]: The offending signal was key-press-event on ClutterText 0x5632ca2115c0. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:49 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:49 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:49 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:49 dipper gnome-shell[4037]: The offending signal was key-press-event on ClutterText 0x5632ca2115c0. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:49 dipper gnome-shell[4037]: The offending signal was captured-event on MetaStage 0x5632c8356410. May 05 11:18:49 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:49 dipper gnome-shell[4037]: The offending callback was filter_key_event(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was update_allocation(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:59 dipper gnome-shell[4037]: The offending signal was notify on StWidget 0x5632c89b8a40. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:18:59 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:18:59 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:18:59 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:18:59 dipper gnome-shell[4037]: The offending signal was last-device-changed on MetaBackendNative 0x5632c7fab170. May 05 11:19:00 dipper gnome-shell[4037]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell.SearchProvider2” on object at path /org/gnome/seahorse/Application May 05 11:19:00 dipper gnome-shell[4037]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0 May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was update_allocation(), a vfunc. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was get_paint_volume(), a vfunc. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-properties-changed on GDBusProxy 0x5632ceee9130. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-properties-changed on GDBusProxy 0x5632ceee9130. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-properties-changed on GDBusProxy 0x5632ca7a9160. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:16 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:16 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:16 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: #0 7fff4bd49e00 I /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/docking.js:119 (d122ccd0718 @ 1115) May 05 11:19:28 dipper gnome-shell[4037]: #1 5632cbd0df30 i resource:///org/gnome/shell/ui/main.js:620 (19fbe03db880 @ 726) May 05 11:19:28 dipper gnome-shell[4037]: #2 5632cbd0de58 i resource:///org/gnome/shell/ui/overview.js:544 (1d58ba11a60 @ 289) May 05 11:19:28 dipper gnome-shell[4037]: #3 5632cbd0ddc0 i resource:///org/gnome/shell/ui/overview.js:678 (1d58ba11e20 @ 215) May 05 11:19:28 dipper gnome-shell[4037]: #4 5632cbd0dd38 i resource:///org/gnome/shell/ui/overview.js:650 (1d58ba11da8 @ 12) May 05 11:19:28 dipper gnome-shell[4037]: #5 5632cbd0dca8 i resource:///org/gnome/shell/ui/environment.js:75 (19fbe038d5b0 @ 98) May 05 11:19:28 dipper gnome-shell[4037]: #6 5632cbd0dc18 i resource:///org/gnome/shell/ui/environment.js:149 (19fbe038d9e8 @ 14) May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: #0 5632cbd0df30 i resource:///org/gnome/shell/ui/main.js:620 (19fbe03db880 @ 726) May 05 11:19:28 dipper gnome-shell[4037]: #1 5632cbd0de58 i resource:///org/gnome/shell/ui/overview.js:544 (1d58ba11a60 @ 289) May 05 11:19:28 dipper gnome-shell[4037]: #2 5632cbd0ddc0 i resource:///org/gnome/shell/ui/overview.js:678 (1d58ba11e20 @ 215) May 05 11:19:28 dipper gnome-shell[4037]: #3 5632cbd0dd38 i resource:///org/gnome/shell/ui/overview.js:650 (1d58ba11da8 @ 12) May 05 11:19:28 dipper gnome-shell[4037]: #4 5632cbd0dca8 i resource:///org/gnome/shell/ui/environment.js:75 (19fbe038d5b0 @ 98) May 05 11:19:28 dipper gnome-shell[4037]: #5 5632cbd0dc18 i resource:///org/gnome/shell/ui/environment.js:149 (19fbe038d9e8 @ 14) May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: #0 5632cbd0df30 i resource:///org/gnome/shell/ui/main.js:620 (19fbe03db880 @ 726) May 05 11:19:28 dipper gnome-shell[4037]: #1 5632cbd0de58 i resource:///org/gnome/shell/ui/overview.js:544 (1d58ba11a60 @ 289) May 05 11:19:28 dipper gnome-shell[4037]: #2 5632cbd0ddc0 i resource:///org/gnome/shell/ui/overview.js:678 (1d58ba11e20 @ 215) May 05 11:19:28 dipper gnome-shell[4037]: #3 5632cbd0dd38 i resource:///org/gnome/shell/ui/overview.js:650 (1d58ba11da8 @ 12) May 05 11:19:28 dipper gnome-shell[4037]: #4 5632cbd0dca8 i resource:///org/gnome/shell/ui/environment.js:75 (19fbe038d5b0 @ 98) May 05 11:19:28 dipper gnome-shell[4037]: #5 5632cbd0dc18 i resource:///org/gnome/shell/ui/environment.js:149 (19fbe038d9e8 @ 14) May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: #0 5632cbd0df30 i resource:///org/gnome/shell/ui/main.js:620 (19fbe03db880 @ 726) May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:19:28 dipper gnome-shell[4037]: #1 5632cbd0de58 i resource:///org/gnome/shell/ui/overview.js:544 (1d58ba11a60 @ 289) May 05 11:19:28 dipper gnome-shell[4037]: #2 5632cbd0ddc0 i resource:///org/gnome/shell/ui/overview.js:678 (1d58ba11e20 @ 215) May 05 11:19:28 dipper gnome-shell[4037]: #3 5632cbd0dd38 i resource:///org/gnome/shell/ui/overview.js:650 (1d58ba11da8 @ 12) May 05 11:19:28 dipper gnome-shell[4037]: #4 5632cbd0dca8 i resource:///org/gnome/shell/ui/environment.js:75 (19fbe038d5b0 @ 98) May 05 11:19:28 dipper gnome-shell[4037]: #5 5632cbd0dc18 i resource:///org/gnome/shell/ui/environment.js:149 (19fbe038d9e8 @ 14) May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: #0 5632cbd0df30 i resource:///org/gnome/shell/ui/main.js:620 (19fbe03db880 @ 726) May 05 11:19:28 dipper gnome-shell[4037]: #1 5632cbd0de58 i resource:///org/gnome/shell/ui/overview.js:544 (1d58ba11a60 @ 289) May 05 11:19:28 dipper gnome-shell[4037]: #2 5632cbd0ddc0 i resource:///org/gnome/shell/ui/overview.js:678 (1d58ba11e20 @ 215) May 05 11:19:28 dipper gnome-shell[4037]: #3 5632cbd0dd38 i resource:///org/gnome/shell/ui/overview.js:650 (1d58ba11da8 @ 12) May 05 11:19:28 dipper gnome-shell[4037]: #4 5632cbd0dca8 i resource:///org/gnome/shell/ui/environment.js:75 (19fbe038d5b0 @ 98) May 05 11:19:28 dipper gnome-shell[4037]: #5 5632cbd0dc18 i resource:///org/gnome/shell/ui/environment.js:149 (19fbe038d9e8 @ 14) May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was stopped on ClutterPropertyTransition 0x5632cecfcdd0. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was stopped on ClutterPropertyTransition 0x5632cecfcd00. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was stopped on ClutterPropertyTransition 0x5632c8a178d0. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was app-state-changed on ShellAppSystem 0x5632c8486cd0. May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was app-state-changed on ShellAppSystem 0x5632c8486cd0. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was app-state-changed on ShellAppSystem 0x5632c8486cd0. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was app-state-changed on ShellAppSystem 0x5632c8486cd0. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was notify on ShellApp 0x5632ca078880. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was startup-sequence-changed on ShellWindowTracker 0x5632c8aa8a40. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was startup-sequence-changed on ShellWindowTracker 0x5632c8aa8a40. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was AsyncReadyCallback(). May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was AsyncReadyCallback(). May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was update-preedit-text on IBusInputContext 0x5632c9ff1ed0. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was update-auxiliary-text on IBusPanelService 0x5632ce558c30. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was update-lookup-table on IBusPanelService 0x5632ce558c30. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was register-properties on IBusPanelService 0x5632ce558c30. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was update-preedit-text on IBusInputContext 0x5632c9ff1ed0. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was update-auxiliary-text on IBusPanelService 0x5632ce558c30. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was update-lookup-table on IBusPanelService 0x5632ce558c30. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was register-properties on IBusPanelService 0x5632ce558c30. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was update-preedit-text on IBusInputContext 0x5632c9ff1ed0. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was update-auxiliary-text on IBusPanelService 0x5632ce558c30. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was update-lookup-table on IBusPanelService 0x5632ce558c30. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was register-properties on IBusPanelService 0x5632ce558c30. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was update-preedit-text on IBusInputContext 0x5632c9ff1ed0. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was focus-out on IBusPanelService 0x5632ce558c30. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was focus-out on IBusPanelService 0x5632ce558c30. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was update-preedit-text on IBusInputContext 0x5632c9ff1ed0. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was focus-in on IBusPanelService 0x5632ce558c30. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was set-content-type on IBusPanelService 0x5632ce558c30. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:28 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:28 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:28 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was notify on Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock 0x5632ca8598d0. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was SourceFunc(). May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632c8445c90. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was g-signal on GDBusProxy 0x5632ca071c10. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was DBusSignalCallback(). May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was size-changed on ShellWM 0x5632c8449020. May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:19:40 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was repaint on StDrawingArea 0x5632cba9c070. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was repaint on StDrawingArea 0x5632cba9c070. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was repaint on StDrawingArea 0x5632cba9c070. May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was repaint on StDrawingArea 0x5632cba9c070. May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was repaint on StDrawingArea 0x5632cba9c070. May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was repaint on StDrawingArea 0x5632ce675df0. May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:40 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:19:40 dipper gnome-shell[4037]: The offending signal was repaint on StDrawingArea 0x5632cba9c070. May 05 11:19:40 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:19:44 dipper gnome-shell[4037]: libinput error: client bug: timer event2 debounce: scheduled expiry is in the past (-1ms), your system is too slow May 05 11:19:44 dipper gnome-shell[4037]: libinput error: client bug: timer event2 debounce short: scheduled expiry is in the past (-14ms), your system is too slow May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: libinput error: client bug: timer event2 debounce: scheduled expiry is in the past (-4521ms), your system is too slow May 05 11:21:06 dipper gnome-shell[4037]: libinput error: client bug: timer event2 debounce short: scheduled expiry is in the past (-4534ms), your system is too slow May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: == Stack trace for context 0x5632c8017280 == May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. May 05 11:21:06 dipper gnome-shell[4037]: The offending signal was notify on Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock 0x5632ca8598d0. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was allocate(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_height(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc. May 05 11:21:06 dipper gnome-shell[4037]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. May 05 11:21:06 dipper gnome-shell[4037]: The offending callback was get_preferred_width(), a vfunc.