Attachment 1674105 Details for Bug 1814015 – gnome-shell journal entry before crash

gnome-shell journal entry before crash

journal_gnome-shell_before_crash.txt (text/plain), 158.84 KB, created by Geoffrey Marr on 2020-03-27 15:27:56 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Geoffrey Marr

Created: 2020-03-27 15:27:56 UTC

Size: 158.84 KB

patch

obsolete

>-- Logs begin at Thu 2020-03-26 09:54:20 MDT, end at Thu 2020-03-26 14:41:34 MDT. --
>Mar 26 09:54:40 localhost.localdomain gnome-shell[1339]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 9.0.1, 256 bits)), falling back to CPU copy path
>Mar 26 09:54:41 localhost.localdomain gnome-shell[1339]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 09:54:41 localhost.localdomain gnome-shell[1339]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 09:54:41 localhost.localdomain gnome-shell[1339]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
>Mar 26 09:54:41 localhost.localdomain gnome-shell[1339]: Will monitor session c1
>Mar 26 09:54:42 localhost.localdomain gnome-shell[1339]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property "MetaWindowXwayland"
>Mar 26 09:54:42 localhost.localdomain gnome-shell[1339]: Registering session with GDM
>Mar 26 09:55:39 localhost.localdomain gnome-shell[1910]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 9.0.1, 256 bits)), falling back to CPU copy path
>Mar 26 09:55:40 localhost.localdomain gnome-shell[1339]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 09:55:40 localhost.localdomain gnome-shell[1339]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 09:55:40 localhost.localdomain gnome-shell[1910]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 09:55:40 localhost.localdomain gnome-shell[1910]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 09:55:40 localhost.localdomain gnome-shell[1910]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
>Mar 26 09:55:40 localhost.localdomain gnome-shell[1910]: Will monitor session 4
>Mar 26 09:55:41 localhost.localdomain gnome-shell[1910]: Telepathy is not available, chat integration will be disabled.
>Mar 26 09:55:41 localhost.localdomain gnome-shell[1910]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
>Mar 26 09:55:42 localhost.localdomain gnome-shell[1339]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied
>Mar 26 09:55:42 localhost.localdomain gnome-shell[1339]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied
>Mar 26 09:55:42 localhost.localdomain gnome-shell[1910]: GNOME Shell started at Thu Mar 26 2020 09:55:41 GMT-0600 (Mountain Daylight Time)
>Mar 26 09:55:42 localhost.localdomain gnome-shell[1910]: Registering session with GDM
>Mar 26 09:55:42 localhost.localdomain gnome-shell[1339]: Connection to xwayland lost
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: Received error from DBus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: Received error from DBus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: Object St.BoxLayout (0x5652338ddc70), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: == Stack trace for context 0x5652331b6470 ==
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #0   5652335dd8d0 i   resource:///org/gnome/shell/ui/search.js:332 (13328838970 @ 22)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #1   7ffc918535d0 b   resource:///org/gnome/shell/ui/search.js:264 (13328838628 @ 53)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #2   7ffc918536c0 b   resource:///org/gnome/shell/ui/search.js:704 (13328839da8 @ 71)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #3   7ffc91853790 b   resource:///org/gnome/shell/ui/search.js:522 (13328839448 @ 45)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #4   5652335dd838 i   resource:///org/gnome/shell/ui/search.js:563 (13328839718 @ 20)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #5   7ffc91854bc0 b   resource:///org/gnome/shell/ui/remoteSearch.js:255 (1332883b880 @ 157)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #6   7ffc91854ca0 b   resource:///org/gnome/shell/ui/remoteSearch.js:261 (1332883b970 @ 23)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #7   7ffc91854d90 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (f90c0cce448 @ 312)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: == Stack trace for context 0x5652331b6470 ==
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #0   7ffc918535d0 b   resource:///org/gnome/shell/ui/search.js:265 (13328838628 @ 69)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #1   7ffc918536c0 b   resource:///org/gnome/shell/ui/search.js:704 (13328839da8 @ 71)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #2   7ffc91853790 b   resource:///org/gnome/shell/ui/search.js:522 (13328839448 @ 45)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #3   5652335dd838 i   resource:///org/gnome/shell/ui/search.js:563 (13328839718 @ 20)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #4   7ffc91854bc0 b   resource:///org/gnome/shell/ui/remoteSearch.js:255 (1332883b880 @ 157)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #5   7ffc91854ca0 b   resource:///org/gnome/shell/ui/remoteSearch.js:261 (1332883b970 @ 23)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: #6   7ffc91854d90 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (f90c0cce448 @ 312)
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: clutter_actor_remove_all_children: assertion 'CLUTTER_IS_ACTOR (self)' failed
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: Object .Gjs_ui_search_ListSearchResults (0x565233ab3ab0), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: clutter_actor_hide: assertion 'CLUTTER_IS_ACTOR (self)' failed
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: Received error from DBus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
>Mar 26 09:55:53 localhost.localdomain gnome-shell[1910]: Received error from DBus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
>Mar 26 10:05:49 localhost.localdomain gnome-shell[1910]: JS WARNING: [resource:///org/gnome/shell/ui/unlockDialog.js 764]: reference to undefined property "_authPrompt"
>Mar 26 10:05:49 localhost.localdomain gnome-shell[1910]: JS ERROR: TypeError: this._authPrompt is undefined
>                                                         _escape@resource:///org/gnome/shell/ui/unlockDialog.js:764:13
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: Object .Gjs_ui_messageTray_NotificationApplicationPolicy (0x56523561cd80), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: == Stack trace for context 0x5652331b6470 ==
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: #0   7ffc9184fa20 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (f90c0ca34c0 @ 25)
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: #1   5652356d4b30 i   resource:///org/gnome/shell/ui/unlockDialog.js:310 (2304c4f46178 @ 140)
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: #2   5652356d4a90 i   resource:///org/gnome/shell/ui/unlockDialog.js:299 (2304c4f46100 @ 23)
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: #3   5652356d49f8 i   resource:///org/gnome/shell/ui/unlockDialog.js:212 (2304c4f3eda8 @ 27)
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: #4   5652356d4948 i   resource:///org/gnome/shell/ui/messageTray.js:891 (33c5013769e8 @ 175)
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: #5   5652356d4898 i   resource:///org/gnome/shell/ui/notificationDaemon.js:518 (2304c4f01100 @ 89)
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: #6   5652356d47f0 i   resource:///org/gnome/shell/ui/messageTray.js:839 (33c501376808 @ 141)
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: #7   7ffc918520f0 b   self-hosted:1011 (33c50132ee98 @ 454)
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: #8   5652356d4748 i   resource:///org/gnome/shell/ui/messageTray.js:518 (33c501374718 @ 127)
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: #9   5652356d46a8 i   resource:///org/gnome/shell/ui/notificationDaemon.js:362 (2304c4f009e8 @ 94)
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: #10   5652356d45c0 i   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:327 (f90c0ccef10 @ 185)
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: #11   5652356d4508 i   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404 (f90c0cd7178 @ 34)
>Mar 26 10:16:43 localhost.localdomain gnome-shell[1910]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
>                                                         _init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24
>                                                         _removeSource@resource:///org/gnome/shell/ui/unlockDialog.js:310:23
>                                                         _onSourceDestroy@resource:///org/gnome/shell/ui/unlockDialog.js:299:14
>                                                         _sourceAdded/obj.sourceDestroyId<@resource:///org/gnome/shell/ui/unlockDialog.js:212:18
>                                                         destroy@resource:///org/gnome/shell/ui/messageTray.js:891:14
>                                                         destroy@resource:///org/gnome/shell/ui/notificationDaemon.js:518:15
>                                                         _onNotificationDestroy@resource:///org/gnome/shell/ui/messageTray.js:839:18
>                                                         destroy@resource:///org/gnome/shell/ui/messageTray.js:518:14
>                                                         CloseNotification@resource:///org/gnome/shell/ui/notificationDaemon.js:362:36
>                                                         _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:327:38
>                                                         _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404:34
>Mar 26 10:18:44 localhost.localdomain gnome-shell[1910]: JS ERROR: TypeError: this._authPrompt is undefined
>                                                         _escape@resource:///org/gnome/shell/ui/unlockDialog.js:764:13
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: Object .Gjs_ui_messageTray_NotificationApplicationPolicy (0x5652355464a0), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: == Stack trace for context 0x5652331b6470 ==
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: #0   7ffc9184fb10 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (f90c0ca34c0 @ 25)
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: #1   5652355f99a0 i   resource:///org/gnome/shell/ui/unlockDialog.js:310 (2304c4f46178 @ 140)
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: #2   5652355f9900 i   resource:///org/gnome/shell/ui/unlockDialog.js:299 (2304c4f46100 @ 23)
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: #3   5652355f9868 i   resource:///org/gnome/shell/ui/unlockDialog.js:212 (2304c4f3eda8 @ 27)
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: #4   5652355f97b8 i   resource:///org/gnome/shell/ui/messageTray.js:891 (33c5013769e8 @ 175)
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: #5   5652355f9708 i   resource:///org/gnome/shell/ui/notificationDaemon.js:518 (2304c4f01100 @ 89)
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: #6   5652355f9660 i   resource:///org/gnome/shell/ui/messageTray.js:839 (33c501376808 @ 141)
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: #7   7ffc918520f0 b   self-hosted:1011 (33c50132ee98 @ 454)
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: #8   5652355f95b8 i   resource:///org/gnome/shell/ui/messageTray.js:518 (33c501374718 @ 127)
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: #9   5652355f9518 i   resource:///org/gnome/shell/ui/notificationDaemon.js:362 (2304c4f009e8 @ 94)
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: #10   5652355f9430 i   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:327 (f90c0ccef10 @ 185)
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: #11   5652355f9378 i   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404 (f90c0cd7178 @ 34)
>Mar 26 10:32:47 localhost.localdomain gnome-shell[1910]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
>                                                         _init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24
>                                                         _removeSource@resource:///org/gnome/shell/ui/unlockDialog.js:310:23
>                                                         _onSourceDestroy@resource:///org/gnome/shell/ui/unlockDialog.js:299:14
>                                                         _sourceAdded/obj.sourceDestroyId<@resource:///org/gnome/shell/ui/unlockDialog.js:212:18
>                                                         destroy@resource:///org/gnome/shell/ui/messageTray.js:891:14
>                                                         destroy@resource:///org/gnome/shell/ui/notificationDaemon.js:518:15
>                                                         _onNotificationDestroy@resource:///org/gnome/shell/ui/messageTray.js:839:18
>                                                         destroy@resource:///org/gnome/shell/ui/messageTray.js:518:14
>                                                         CloseNotification@resource:///org/gnome/shell/ui/notificationDaemon.js:362:36
>                                                         _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:327:38
>                                                         _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404:34
>Mar 26 10:32:50 localhost.localdomain gnome-shell[1910]: JS ERROR: TypeError: obj.sourceBox is null
>                                                         _removeSource@resource:///org/gnome/shell/ui/unlockDialog.js:304:9
>                                                         _onDestroy@resource:///org/gnome/shell/ui/unlockDialog.js:68:18
>                                                         _completeDeactivate@resource:///org/gnome/shell/ui/screenShield.js:532:26
>                                                         onComplete@resource:///org/gnome/shell/ui/screenShield.js:526:36
>                                                         _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13
>                                                         _easeActor/<@resource:///org/gnome/shell/ui/environment.js:147:56
>Mar 26 10:32:53 localhost.localdomain gnome-shell[1910]: Received error from DBus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
>Mar 26 10:32:53 localhost.localdomain gnome-shell[1910]: Received error from DBus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
>Mar 26 10:32:54 localhost.localdomain gnome-shell[1910]: Received error from DBus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
>Mar 26 10:32:54 localhost.localdomain gnome-shell[1910]: Received error from DBus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
>Mar 26 10:32:54 localhost.localdomain gnome-shell[1910]: Received error from DBus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
>-- Reboot --
>Mar 26 10:39:15 localhost.localdomain gnome-shell[1358]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 9.0.1, 256 bits)), falling back to CPU copy path
>Mar 26 10:39:15 localhost.localdomain gnome-shell[1358]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:39:15 localhost.localdomain gnome-shell[1358]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:39:15 localhost.localdomain gnome-shell[1358]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
>Mar 26 10:39:15 localhost.localdomain gnome-shell[1358]: Will monitor session c1
>Mar 26 10:39:16 localhost.localdomain gnome-shell[1358]: Getting invalid resource scale property
>Mar 26 10:39:16 localhost.localdomain gnome-shell[1358]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
>Mar 26 10:39:16 localhost.localdomain gnome-shell[1358]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property "MetaWindowXwayland"
>Mar 26 10:39:17 localhost.localdomain gnome-shell[1358]: Registering session with GDM
>Mar 26 10:39:25 localhost.localdomain gnome-shell[1802]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 9.0.1, 256 bits)), falling back to CPU copy path
>Mar 26 10:39:26 localhost.localdomain gnome-shell[1358]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:39:26 localhost.localdomain gnome-shell[1358]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:39:26 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:39:26 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:39:26 localhost.localdomain gnome-shell[1802]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
>Mar 26 10:39:26 localhost.localdomain gnome-shell[1802]: Will monitor session 2
>Mar 26 10:39:27 localhost.localdomain gnome-shell[1802]: Telepathy is not available, chat integration will be disabled.
>Mar 26 10:39:27 localhost.localdomain gnome-shell[1802]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
>Mar 26 10:39:28 localhost.localdomain gnome-shell[1358]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied
>Mar 26 10:39:28 localhost.localdomain gnome-shell[1358]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied
>Mar 26 10:39:28 localhost.localdomain gnome-shell[1802]: GNOME Shell started at Thu Mar 26 2020 10:39:27 GMT-0600 (Mountain Daylight Time)
>Mar 26 10:39:28 localhost.localdomain gnome-shell[1802]: Registering session with GDM
>Mar 26 10:39:28 localhost.localdomain gnome-shell[1358]: Connection to xwayland lost
>Mar 26 10:44:10 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:44:10 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:44:10 localhost.localdomain gnome-shell[1802]: ../gobject/gsignal.c:2735: instance '0x55a2bc8888a0' has no handler with id '12754'
>Mar 26 10:44:10 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:44:10 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:44:10 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:44:10 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:44:11 localhost.localdomain gnome-shell[1802]: JS ERROR: TypeError: this._bgManager is null
>                                                         _backgroundDestroyed@/usr/share/gnome-shell/extensions/background-logo@fedorahosted.org/extension.js:232:13
>                                                         onComplete@resource:///org/gnome/shell/ui/background.js:703:50
>                                                         _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13
>                                                         _easeActor/<@resource:///org/gnome/shell/ui/environment.js:147:56
>Mar 26 10:45:46 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:45:46 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:45:46 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:45:46 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:45:47 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:45:47 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:45:49 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:45:49 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:45:49 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:45:49 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:45:49 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:45:49 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:46:07 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:46:07 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:46:07 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:46:07 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:46:07 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:46:07 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:47:33 localhost.localdomain gnome-shell[1802]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 2
>Mar 26 10:47:34 localhost.localdomain gnome-shell[1802]: Could not release device (13,66): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:34 localhost.localdomain gnome-shell[1802]: Could not release device (13,69): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:34 localhost.localdomain gnome-shell[1802]: Could not release device (13,68): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:34 localhost.localdomain gnome-shell[1802]: Could not release device (13,65): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:34 localhost.localdomain gnome-shell[1802]: Could not release device (13,64): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:34 localhost.localdomain gnome-shell[1802]: Could not release device (13,75): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:34 localhost.localdomain gnome-shell[1802]: Could not release device (13,76): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:34 localhost.localdomain gnome-shell[1802]: Could not release device (13,77): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:34 localhost.localdomain gnome-shell[1802]: Could not release device (13,78): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:34 localhost.localdomain gnome-shell[1802]: Could not release device (13,79): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:34 localhost.localdomain gnome-shell[1802]: Could not release device (13,80): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,81): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,70): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,73): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,74): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,82): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,83): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,84): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,85): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,86): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,87): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,88): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,89): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,90): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,67): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Could not release device (13,71): Cannot invoke method; proxy is for the well-known name org.freedesktop.login1 without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: clutter_input_device_get_device_type: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Error setting property 'Powered' on interface org.bluez.Adapter1: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable (g-dbus-error-quark, 2)
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Object Meta.BackgroundActor (0x55a2bc8893e0), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: #0   7ffe57d7a1c0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (2b0c377a34c0 @ 25)
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: #1   55a2bc18e058 i   /usr/share/gnome-shell/extensions/background-logo@fedorahosted.org/extension.js:246 (21236b96acb8 @ 86)
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: #2   7ffe57d7b500 b   self-hosted:1009 (269c8a52ee98 @ 423)
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
>                                                         _init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24
>                                                         _onDestroy@/usr/share/gnome-shell/extensions/background-logo@fedorahosted.org/extension.js:246:45
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: JS ERROR: TypeError: actor.get_meta_window(...) is null
>                                                         _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1574:32
>                                                         onStopped@resource:///org/gnome/shell/ui/windowManager.js:1544:39
>                                                         _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:71:13
>                                                         _easeActor/<@resource:///org/gnome/shell/ui/environment.js:147:56
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55a2bda1d450.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bd36b880.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bd36b880.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2be5e4310.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2be484bf0.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2be484bf0.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2bd357730.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2be6ac480.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2be6ac480.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2be6bd860.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bddcce40.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bddcce40.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2bddce1a0.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2be7d9080.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2be7d9080.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2bc97eaa0.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55a2bb697470 ==
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bc97e080.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bc97e080.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2bbcf3460.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2be78d720.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2be78d720.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2bdd61b50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bd6ed390.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bd6ed390.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2bc30f870.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2be7d7280.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2be7d7280.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2be883860.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2be808080.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2be808080.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2bc0abdd0.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bc02fc60.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bc02fc60.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2bbf928e0.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bdd3c480.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bdd3c480.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2bdb4d620.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bbfa06b0.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bbfa06b0.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2bc1d60e0.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bdcc8710.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bdcc8710.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2bdab6830.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bdb3d710.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55a2bdb3d710.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55a2bd45ab00.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55a2bd39fc50.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was notify on NMDeviceEthernet 0x55a2bdce0280.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was notify on NMDeviceWifi 0x7f945001d810.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was notify on NMActiveConnection 0x55a2bc201180.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was state-changed on NMDeviceEthernet 0x55a2bdce0280.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 10:47:35 localhost.localdomain gnome-shell[1802]: The offending signal was state-changed on NMDeviceWifi 0x7f945001d810.
>-- Reboot --
>Mar 26 10:52:42 localhost.localdomain gnome-shell[1361]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 10.0.0, 256 bits)), falling back to CPU copy path
>Mar 26 10:52:43 localhost.localdomain gnome-shell[1361]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
>Mar 26 10:52:43 localhost.localdomain gnome-shell[1361]: Will monitor session c1
>Mar 26 10:52:44 localhost.localdomain gnome-shell[1361]: Getting invalid resource scale property
>Mar 26 10:52:44 localhost.localdomain gnome-shell[1361]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
>Mar 26 10:52:44 localhost.localdomain gnome-shell[1361]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property "MetaWindowXwayland"
>Mar 26 10:52:44 localhost.localdomain gnome-shell[1361]: Registering session with GDM
>Mar 26 10:52:49 localhost.localdomain gnome-shell[1802]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 10.0.0, 256 bits)), falling back to CPU copy path
>Mar 26 10:52:49 localhost.localdomain gnome-shell[1802]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
>Mar 26 10:52:49 localhost.localdomain gnome-shell[1802]: Will monitor session 2
>Mar 26 10:52:51 localhost.localdomain gnome-shell[1802]: Telepathy is not available, chat integration will be disabled.
>Mar 26 10:52:51 localhost.localdomain gnome-shell[1802]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
>Mar 26 10:52:52 localhost.localdomain gnome-shell[1802]: GNOME Shell started at Thu Mar 26 2020 10:52:51 GMT-0600 (Mountain Daylight Time)
>Mar 26 10:52:52 localhost.localdomain gnome-shell[1802]: Registering session with GDM
>Mar 26 10:52:52 localhost.localdomain gnome-shell[1361]: Connection to xwayland lost
>Mar 26 10:54:03 localhost.localdomain gnome-shell[1802]: pushModal: invocation of begin_modal failed
>Mar 26 11:11:40 localhost.localdomain gnome-shell[1802]: JS WARNING: [resource:///org/gnome/shell/ui/unlockDialog.js 764]: reference to undefined property "_authPrompt"
>Mar 26 11:11:40 localhost.localdomain gnome-shell[1802]: JS ERROR: TypeError: this._authPrompt is undefined
>                                                         _escape@resource:///org/gnome/shell/ui/unlockDialog.js:764:13
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: An active wireless connection, in infrastructure mode, involves no access point?
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: Object .Gjs_ui_messageTray_NotificationApplicationPolicy (0x55cebf42f6c0), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: #0   7ffe0b446770 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (139c60ba34c0 @ 25)
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: #1   55cebf75a240 i   resource:///org/gnome/shell/ui/unlockDialog.js:310 (1a2ec5246178 @ 140)
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: #2   55cebf75a1a0 i   resource:///org/gnome/shell/ui/unlockDialog.js:299 (1a2ec5246100 @ 23)
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: #3   55cebf75a108 i   resource:///org/gnome/shell/ui/unlockDialog.js:212 (1a2ec523eda8 @ 27)
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: #4   55cebf75a058 i   resource:///org/gnome/shell/ui/messageTray.js:891 (2e69abc769e8 @ 175)
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: #5   55cebf759fa8 i   resource:///org/gnome/shell/ui/notificationDaemon.js:518 (1a2ec5201100 @ 89)
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: #6   55cebf759f00 i   resource:///org/gnome/shell/ui/messageTray.js:839 (2e69abc76808 @ 141)
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: #7   7ffe0b448ca0 b   self-hosted:1011 (2e69abc2ee98 @ 454)
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: #8   55cebf759e58 i   resource:///org/gnome/shell/ui/messageTray.js:518 (2e69abc74718 @ 127)
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: #9   55cebf759db8 i   resource:///org/gnome/shell/ui/notificationDaemon.js:362 (1a2ec52009e8 @ 94)
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: #10   55cebf759cd0 i   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:327 (139c60bcef10 @ 185)
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: #11   55cebf759c18 i   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404 (139c60bd7178 @ 34)
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
>                                                         _init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24
>                                                         _removeSource@resource:///org/gnome/shell/ui/unlockDialog.js:310:23
>                                                         _onSourceDestroy@resource:///org/gnome/shell/ui/unlockDialog.js:299:14
>                                                         _sourceAdded/obj.sourceDestroyId<@resource:///org/gnome/shell/ui/unlockDialog.js:212:18
>                                                         destroy@resource:///org/gnome/shell/ui/messageTray.js:891:14
>                                                         destroy@resource:///org/gnome/shell/ui/notificationDaemon.js:518:15
>                                                         _onNotificationDestroy@resource:///org/gnome/shell/ui/messageTray.js:839:18
>                                                         destroy@resource:///org/gnome/shell/ui/messageTray.js:518:14
>                                                         CloseNotification@resource:///org/gnome/shell/ui/notificationDaemon.js:362:36
>                                                         _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:327:38
>                                                         _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404:34
>Mar 26 11:45:06 localhost.localdomain gnome-shell[1802]: An active wireless connection, in infrastructure mode, involves no access point?
>Mar 26 11:45:10 localhost.localdomain gnome-shell[1802]: JS ERROR: TypeError: obj.sourceBox is null
>                                                         _removeSource@resource:///org/gnome/shell/ui/unlockDialog.js:304:9
>                                                         _onDestroy@resource:///org/gnome/shell/ui/unlockDialog.js:68:18
>                                                         _completeDeactivate@resource:///org/gnome/shell/ui/screenShield.js:532:26
>                                                         onComplete@resource:///org/gnome/shell/ui/screenShield.js:526:36
>                                                         _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13
>                                                         _easeActor/<@resource:///org/gnome/shell/ui/environment.js:147:56
>Mar 26 11:55:02 localhost.localdomain gnome-shell[1802]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: #0   7ffe0b449d90 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (139c60ba34c0 @ 25)
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: #1   55cebe1773b8 i   /usr/share/gnome-shell/extensions/background-logo@fedorahosted.org/extension.js:246 (30c70976acb8 @ 86)
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: #2   7ffe0b44b020 b   self-hosted:1009 (2e69abc2ee98 @ 423)
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Object Meta.BackgroundActor (0x55cebe4e5010), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
>                                                         _init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24
>                                                         _onDestroy@/usr/share/gnome-shell/extensions/background-logo@fedorahosted.org/extension.js:246:45
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55cebe4e7470.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebeff0480.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebeff0480.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cebf0b3dc0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebef8a480.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebef8a480.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cebe071550.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cec029b880.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cec029b880.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cec04e1e60.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebf97e380.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebf97e380.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cebdc2f930.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebf9e18c0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebf9e18c0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cec03ece60.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebd9fd7b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebd9fd7b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cebf69cea0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebefcc080.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebefcc080.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cebf992c60.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebdcd6b20.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebdcd6b20.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cebf92f860.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: == Stack trace for context 0x55cebd325430 ==
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebf861080.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebf861080.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cebf486860.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebf4666b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebf4666b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cebdd17860.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cec04ce480.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cec04ce480.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cec04d4060.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebe3aac80.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebe3aac80.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cec04cac60.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebd9b1080.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebd9b1080.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cebf9f5ac0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebf6f7e00.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebf6f7e00.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cebf6f9a20.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebe072080.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55cebe072080.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55cec03b0460.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was actor-removed on Gjs_ui_iconGrid_IconGrid 0x55cebef927b0.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was notify on NMDeviceEthernet 0x55cebf982260.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was notify on NMDeviceWifi 0x7fde0801f800.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was notify on NMActiveConnection 0x55cebfa49340.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was notify on NMAccessPoint 0x7fde08065110.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was state-changed on NMDeviceEthernet 0x55cebf982260.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
>Mar 26 11:56:33 localhost.localdomain gnome-shell[1802]: The offending signal was state-changed on NMDeviceWifi 0x7fde0801f800.
>Mar 26 11:56:35 localhost.localdomain gnome-shell[4873]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 10.0.0, 256 bits)), falling back to CPU copy path
>Mar 26 11:56:36 localhost.localdomain gnome-shell[4873]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
>Mar 26 11:56:36 localhost.localdomain gnome-shell[4873]: Will monitor session c2
>Mar 26 11:56:36 localhost.localdomain gnome-shell[4873]: Getting invalid resource scale property
>Mar 26 11:56:36 localhost.localdomain gnome-shell[4873]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
>Mar 26 11:56:37 localhost.localdomain gnome-shell[4873]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property "MetaWindowXwayland"
>Mar 26 11:56:37 localhost.localdomain gnome-shell[4873]: Registering session with GDM
>Mar 26 11:56:49 localhost.localdomain gnome-shell[5313]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 10.0.0, 256 bits)), falling back to CPU copy path
>Mar 26 11:56:49 localhost.localdomain gnome-shell[5313]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
>Mar 26 11:56:49 localhost.localdomain gnome-shell[5313]: Will monitor session 5
>Mar 26 11:56:51 localhost.localdomain gnome-shell[5313]: Telepathy is not available, chat integration will be disabled.
>Mar 26 11:56:51 localhost.localdomain gnome-shell[5313]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
>Mar 26 11:56:51 localhost.localdomain gnome-shell[4873]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied
>Mar 26 11:56:51 localhost.localdomain gnome-shell[4873]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied
>Mar 26 11:56:51 localhost.localdomain gnome-shell[5313]: GNOME Shell started at Thu Mar 26 2020 11:56:51 GMT-0600 (Mountain Daylight Time)
>Mar 26 11:56:51 localhost.localdomain gnome-shell[5313]: Registering session with GDM
>Mar 26 11:56:52 localhost.localdomain gnome-shell[4873]: Connection to xwayland lost
>Mar 26 11:57:22 localhost.localdomain gnome-shell[5313]: Failed to switch VT: Timeout was reached
>-- Reboot --
>Mar 26 13:38:44 localhost.localdomain gnome-shell[1365]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
>Mar 26 13:38:44 localhost.localdomain gnome-shell[1365]: Will monitor session c1
>Mar 26 13:38:45 localhost.localdomain gnome-shell[1365]: Getting invalid resource scale property
>Mar 26 13:38:45 localhost.localdomain gnome-shell[1365]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
>Mar 26 13:38:46 localhost.localdomain gnome-shell[1365]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property "MetaWindowXwayland"
>Mar 26 13:38:46 localhost.localdomain gnome-shell[1365]: Registering session with GDM
>Mar 26 13:38:51 localhost.localdomain gnome-shell[1782]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
>Mar 26 13:38:51 localhost.localdomain gnome-shell[1782]: Will monitor session 2
>Mar 26 13:38:52 localhost.localdomain gnome-shell[1782]: Telepathy is not available, chat integration will be disabled.
>Mar 26 13:38:52 localhost.localdomain gnome-shell[1782]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
>Mar 26 13:38:54 localhost.localdomain gnome-shell[1782]: GNOME Shell started at Thu Mar 26 2020 13:38:52 GMT-0600 (Mountain Daylight Time)
>Mar 26 13:38:54 localhost.localdomain gnome-shell[1782]: Registering session with GDM
>Mar 26 13:38:54 localhost.localdomain gnome-shell[1365]: Connection to xwayland lost
>Mar 26 13:39:36 localhost.localdomain gnome-shell[1782]: pushModal: invocation of begin_modal failed
>Mar 26 13:49:56 localhost.localdomain gnome-shell[1782]: JS WARNING: [resource:///org/gnome/shell/ui/unlockDialog.js 764]: reference to undefined property "_authPrompt"
>Mar 26 13:49:56 localhost.localdomain gnome-shell[1782]: JS ERROR: TypeError: this._authPrompt is undefined
>                                                         _escape@resource:///org/gnome/shell/ui/unlockDialog.js:764:13
>Mar 26 13:58:46 localhost.localdomain gnome-shell[1782]: libinput error: client bug: timer event5 debounce: scheduled expiry is in the past (-208ms), your system is too slow
>Mar 26 13:58:46 localhost.localdomain gnome-shell[1782]: libinput error: client bug: timer event5 debounce: scheduled expiry is in the past (-92ms), your system is too slow
>Mar 26 13:58:46 localhost.localdomain gnome-shell[1782]: libinput error: client bug: timer event5 debounce short: scheduled expiry is in the past (-105ms), your system is too slow
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: Object .Gjs_ui_messageTray_NotificationApplicationPolicy (0x55d1ef588020), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: == Stack trace for context 0x55d1ec679450 ==
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: #0   7ffc7fe838b0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571 (24da268a34c0 @ 25)
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: #1   55d1ecaa5930 i   resource:///org/gnome/shell/ui/unlockDialog.js:310 (af5a0246178 @ 140)
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: #2   55d1ecaa5890 i   resource:///org/gnome/shell/ui/unlockDialog.js:299 (af5a0246100 @ 23)
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: #3   55d1ecaa57f8 i   resource:///org/gnome/shell/ui/unlockDialog.js:212 (af5a023eda8 @ 27)
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: #4   55d1ecaa5748 i   resource:///org/gnome/shell/ui/messageTray.js:891 (1d87297769e8 @ 175)
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: #5   55d1ecaa5698 i   resource:///org/gnome/shell/ui/notificationDaemon.js:518 (af5a0201100 @ 89)
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: #6   55d1ecaa55f0 i   resource:///org/gnome/shell/ui/messageTray.js:839 (1d8729776808 @ 141)
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: #7   55d1ecaa5520 i   self-hosted:1011 (1d872972ead8 @ 454)
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: #8   55d1ecaa5478 i   resource:///org/gnome/shell/ui/messageTray.js:518 (1d8729774718 @ 127)
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: #9   55d1ecaa53d8 i   resource:///org/gnome/shell/ui/notificationDaemon.js:362 (af5a02009e8 @ 94)
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: #10   55d1ecaa52f0 i   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:327 (24da268cef10 @ 185)
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: #11   55d1ecaa5238 i   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404 (24da268d7178 @ 34)
>Mar 26 14:17:17 localhost.localdomain gnome-shell[1782]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
>                                                         _init/GObject.Object.prototype.disconnect@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:571:24
>                                                         _removeSource@resource:///org/gnome/shell/ui/unlockDialog.js:310:23
>                                                         _onSourceDestroy@resource:///org/gnome/shell/ui/unlockDialog.js:299:14
>                                                         _sourceAdded/obj.sourceDestroyId<@resource:///org/gnome/shell/ui/unlockDialog.js:212:18
>                                                         destroy@resource:///org/gnome/shell/ui/messageTray.js:891:14
>                                                         destroy@resource:///org/gnome/shell/ui/notificationDaemon.js:518:15
>                                                         _onNotificationDestroy@resource:///org/gnome/shell/ui/messageTray.js:839:18
>                                                         destroy@resource:///org/gnome/shell/ui/messageTray.js:518:14
>                                                         CloseNotification@resource:///org/gnome/shell/ui/notificationDaemon.js:362:36
>                                                         _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:327:38
>                                                         _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404:34
>Mar 26 14:19:17 localhost.localdomain gnome-shell[1782]: JS ERROR: TypeError: this._authPrompt is null
>                                                         _escape@resource:///org/gnome/shell/ui/unlockDialog.js:764:13
>Mar 26 14:32:10 localhost.localdomain gnome-shell[1782]: JS ERROR: TypeError: obj.sourceBox is null
>                                                         _removeSource@resource:///org/gnome/shell/ui/unlockDialog.js:304:9
>                                                         _onDestroy@resource:///org/gnome/shell/ui/unlockDialog.js:68:18
>                                                         _completeDeactivate@resource:///org/gnome/shell/ui/screenShield.js:532:26
>                                                         onComplete@resource:///org/gnome/shell/ui/screenShield.js:526:36
>                                                         _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13
>                                                         _easeActor/<@resource:///org/gnome/shell/ui/environment.js:147:56
>Mar 26 14:36:42 localhost.localdomain gnome-shell[1782]: Connection to xwayland lost
>-- Reboot --
>Mar 26 14:37:25 localhost.localdomain gnome-shell[1350]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 10.0.0, 256 bits)), falling back to CPU copy path
>Mar 26 14:37:25 localhost.localdomain gnome-shell[1350]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
>Mar 26 14:37:25 localhost.localdomain gnome-shell[1350]: Will monitor session c1
>Mar 26 14:37:26 localhost.localdomain gnome-shell[1350]: Getting invalid resource scale property
>Mar 26 14:37:26 localhost.localdomain gnome-shell[1350]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
>Mar 26 14:37:27 localhost.localdomain gnome-shell[1350]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 24]: reference to undefined property "MetaWindowXwayland"
>Mar 26 14:37:27 localhost.localdomain gnome-shell[1350]: Registering session with GDM
>Mar 26 14:37:36 localhost.localdomain gnome-shell[1797]: Failed to initialize accelerated iGPU/dGPU framebuffer sharing: Do not want to use software renderer (llvmpipe (LLVM 10.0.0, 256 bits)), falling back to CPU copy path
>Mar 26 14:37:37 localhost.localdomain gnome-shell[1797]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
>Mar 26 14:37:37 localhost.localdomain gnome-shell[1797]: Will monitor session 2
>Mar 26 14:37:38 localhost.localdomain gnome-shell[1797]: Telepathy is not available, chat integration will be disabled.
>Mar 26 14:37:38 localhost.localdomain gnome-shell[1797]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
>Mar 26 14:37:38 localhost.localdomain gnome-shell[1350]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied
>Mar 26 14:37:38 localhost.localdomain gnome-shell[1350]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 51 failed: Permission denied
>Mar 26 14:37:39 localhost.localdomain gnome-shell[1797]: GNOME Shell started at Thu Mar 26 2020 14:37:38 GMT-0600 (Mountain Daylight Time)
>Mar 26 14:37:39 localhost.localdomain gnome-shell[1797]: Registering session with GDM
>Mar 26 14:37:39 localhost.localdomain gnome-shell[1350]: Connection to xwayland lost
>Mar 26 14:37:53 localhost.localdomain gnome-shell[1797]: pushModal: invocation of begin_modal failed
>Mar 26 14:38:21 localhost.localdomain gnome-shell[1797]: Received error from DBus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
>Mar 26 14:38:21 localhost.localdomain gnome-shell[1797]: Received error from DBus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
>Mar 26 14:38:21 localhost.localdomain gnome-shell[1797]: Received error from DBus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: Received error from DBus search provider firefox.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: Object .Gjs_ui_search_ListSearchResults (0x5610dd9a6bf0), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: == Stack trace for context 0x5610db7b8450 ==
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #0   5610dbb9a178 i   resource:///org/gnome/shell/ui/search.js:284 (8b0ffd386a0 @ 59)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #1   5610dbb9a0c8 i   resource:///org/gnome/shell/ui/search.js:256 (8b0ffd384c0 @ 375)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #2   7ffeecf5e950 b   resource:///org/gnome/shell/ui/remoteSearch.js:298 (8b0ffd3bad8 @ 514)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #3   5610dbb9a028 i   resource:///org/gnome/shell/ui/remoteSearch.js:304 (8b0ffd3bc40 @ 23)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #4   7ffeecf5fc10 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2df42ce448 @ 312)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: == Stack trace for context 0x5610db7b8450 ==
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #0   7ffeecf5d590 b   resource:///org/gnome/shell/ui/search.js:332 (8b0ffd38970 @ 22)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: clutter_actor_hide: assertion 'CLUTTER_IS_ACTOR (self)' failed
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #1   5610dbb9a178 i   resource:///org/gnome/shell/ui/search.js:285 (8b0ffd386a0 @ 75)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #2   5610dbb9a0c8 i   resource:///org/gnome/shell/ui/search.js:256 (8b0ffd384c0 @ 375)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #3   7ffeecf5e950 b   resource:///org/gnome/shell/ui/remoteSearch.js:298 (8b0ffd3bad8 @ 514)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #4   5610dbb9a028 i   resource:///org/gnome/shell/ui/remoteSearch.js:304 (8b0ffd3bc40 @ 23)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #5   7ffeecf5fc10 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2df42ce448 @ 312)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: == Stack trace for context 0x5610db7b8450 ==
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #0   5610dbb9a208 i   resource:///org/gnome/shell/ui/search.js:341 (8b0ffd38a60 @ 25)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #1   7ffeecf5d480 b   resource:///org/gnome/shell/ui/search.js:287 (8b0ffd38718 @ 26)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #2   7ffeecf5d590 b   self-hosted:266 (2df42aab50 @ 259)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #3   5610dbb9a178 i   resource:///org/gnome/shell/ui/search.js:286 (8b0ffd386a0 @ 102)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #4   5610dbb9a0c8 i   resource:///org/gnome/shell/ui/search.js:256 (8b0ffd384c0 @ 375)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #5   7ffeecf5e950 b   resource:///org/gnome/shell/ui/remoteSearch.js:298 (8b0ffd3bad8 @ 514)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #6   5610dbb9a028 i   resource:///org/gnome/shell/ui/remoteSearch.js:304 (8b0ffd3bc40 @ 23)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #7   7ffeecf5fc10 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2df42ce448 @ 312)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: == Stack trace for context 0x5610db7b8450 ==
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #0   5610dbb9a208 i   resource:///org/gnome/shell/ui/search.js:341 (8b0ffd38a60 @ 25)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #1   7ffeecf5d480 b   resource:///org/gnome/shell/ui/search.js:287 (8b0ffd38718 @ 26)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #2   7ffeecf5d590 b   self-hosted:266 (2df42aab50 @ 259)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #3   5610dbb9a178 i   resource:///org/gnome/shell/ui/search.js:286 (8b0ffd386a0 @ 102)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #4   5610dbb9a0c8 i   resource:///org/gnome/shell/ui/search.js:256 (8b0ffd384c0 @ 375)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #5   7ffeecf5e950 b   resource:///org/gnome/shell/ui/remoteSearch.js:298 (8b0ffd3bad8 @ 514)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #6   5610dbb9a028 i   resource:///org/gnome/shell/ui/remoteSearch.js:304 (8b0ffd3bc40 @ 23)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #7   7ffeecf5fc10 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2df42ce448 @ 312)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: == Stack trace for context 0x5610db7b8450 ==
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: Object St.BoxLayout (0x5610dd9b69d0), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #0   5610dbb9a208 i   resource:///org/gnome/shell/ui/search.js:341 (8b0ffd38a60 @ 25)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #1   7ffeecf5d480 b   resource:///org/gnome/shell/ui/search.js:287 (8b0ffd38718 @ 26)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #2   7ffeecf5d590 b   self-hosted:266 (2df42aab50 @ 259)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #3   5610dbb9a178 i   resource:///org/gnome/shell/ui/search.js:286 (8b0ffd386a0 @ 102)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #4   5610dbb9a0c8 i   resource:///org/gnome/shell/ui/search.js:256 (8b0ffd384c0 @ 375)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #5   7ffeecf5e950 b   resource:///org/gnome/shell/ui/remoteSearch.js:298 (8b0ffd3bad8 @ 514)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #6   5610dbb9a028 i   resource:///org/gnome/shell/ui/remoteSearch.js:304 (8b0ffd3bc40 @ 23)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #7   7ffeecf5fc10 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2df42ce448 @ 312)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: == Stack trace for context 0x5610db7b8450 ==
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #0   5610dbb9a208 i   resource:///org/gnome/shell/ui/search.js:341 (8b0ffd38a60 @ 25)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #1   7ffeecf5d480 b   resource:///org/gnome/shell/ui/search.js:287 (8b0ffd38718 @ 26)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #2   7ffeecf5d590 b   self-hosted:266 (2df42aab50 @ 259)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #3   5610dbb9a178 i   resource:///org/gnome/shell/ui/search.js:286 (8b0ffd386a0 @ 102)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #4   5610dbb9a0c8 i   resource:///org/gnome/shell/ui/search.js:256 (8b0ffd384c0 @ 375)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #5   7ffeecf5e950 b   resource:///org/gnome/shell/ui/remoteSearch.js:298 (8b0ffd3bad8 @ 514)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #6   5610dbb9a028 i   resource:///org/gnome/shell/ui/remoteSearch.js:304 (8b0ffd3bc40 @ 23)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #7   7ffeecf5fc10 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2df42ce448 @ 312)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: == Stack trace for context 0x5610db7b8450 ==
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #0   5610dbb9a208 i   resource:///org/gnome/shell/ui/search.js:341 (8b0ffd38a60 @ 25)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #1   7ffeecf5d480 b   resource:///org/gnome/shell/ui/search.js:287 (8b0ffd38718 @ 26)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #2   7ffeecf5d590 b   self-hosted:266 (2df42aab50 @ 259)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #3   5610dbb9a178 i   resource:///org/gnome/shell/ui/search.js:286 (8b0ffd386a0 @ 102)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #4   5610dbb9a0c8 i   resource:///org/gnome/shell/ui/search.js:256 (8b0ffd384c0 @ 375)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #5   7ffeecf5e950 b   resource:///org/gnome/shell/ui/remoteSearch.js:298 (8b0ffd3bad8 @ 514)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: clutter_actor_remove_all_children: assertion 'CLUTTER_IS_ACTOR (self)' failed
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #6   5610dbb9a028 i   resource:///org/gnome/shell/ui/remoteSearch.js:304 (8b0ffd3bc40 @ 23)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #7   7ffeecf5fc10 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2df42ce448 @ 312)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: == Stack trace for context 0x5610db7b8450 ==
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #0   5610dbb9a2a0 i   resource:///org/gnome/shell/ui/search.js:822 (8b0ffd3b358 @ 54)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #1   5610dbb9a208 i   resource:///org/gnome/shell/ui/search.js:324 (8b0ffd38880 @ 25)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #2   5610dbb9a178 i   resource:///org/gnome/shell/ui/search.js:289 (8b0ffd386a0 @ 169)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #3   5610dbb9a0c8 i   resource:///org/gnome/shell/ui/search.js:256 (8b0ffd384c0 @ 375)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #4   7ffeecf5e950 b   resource:///org/gnome/shell/ui/remoteSearch.js:298 (8b0ffd3bad8 @ 514)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #5   5610dbb9a028 i   resource:///org/gnome/shell/ui/remoteSearch.js:304 (8b0ffd3bc40 @ 23)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #6   7ffeecf5fc10 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2df42ce448 @ 312)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: == Stack trace for context 0x5610db7b8450 ==
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #0   5610dbb9a2a0 i   resource:///org/gnome/shell/ui/search.js:823 (8b0ffd3b358 @ 74)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #1   5610dbb9a208 i   resource:///org/gnome/shell/ui/search.js:324 (8b0ffd38880 @ 25)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #2   5610dbb9a178 i   resource:///org/gnome/shell/ui/search.js:289 (8b0ffd386a0 @ 169)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #3   5610dbb9a0c8 i   resource:///org/gnome/shell/ui/search.js:256 (8b0ffd384c0 @ 375)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #4   7ffeecf5e950 b   resource:///org/gnome/shell/ui/remoteSearch.js:298 (8b0ffd3bad8 @ 514)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #5   5610dbb9a028 i   resource:///org/gnome/shell/ui/remoteSearch.js:304 (8b0ffd3bc40 @ 23)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #6   7ffeecf5fc10 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2df42ce448 @ 312)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: Object St.BoxLayout (0x5610dd9b69d0), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: == Stack trace for context 0x5610db7b8450 ==
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #0   5610dbb9a178 i   resource:///org/gnome/shell/ui/search.js:290 (8b0ffd386a0 @ 185)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #1   5610dbb9a0c8 i   resource:///org/gnome/shell/ui/search.js:256 (8b0ffd384c0 @ 375)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #2   7ffeecf5e950 b   resource:///org/gnome/shell/ui/remoteSearch.js:298 (8b0ffd3bad8 @ 514)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #3   5610dbb9a028 i   resource:///org/gnome/shell/ui/remoteSearch.js:304 (8b0ffd3bc40 @ 23)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #4   7ffeecf5fc10 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2df42ce448 @ 312)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: clutter_container_add_actor: assertion 'CLUTTER_IS_CONTAINER (container)' failed
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: Object St.BoxLayout (0x5610dd9b69d0), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: clutter_container_add_actor: assertion 'CLUTTER_IS_CONTAINER (container)' failed
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: Object St.BoxLayout (0x5610dd9b69d0), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: clutter_container_add_actor: assertion 'CLUTTER_IS_CONTAINER (container)' failed
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: Object St.BoxLayout (0x5610dd9b69d0), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: clutter_container_add_actor: assertion 'CLUTTER_IS_CONTAINER (container)' failed
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: Object St.BoxLayout (0x5610dd9b69d0), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: clutter_container_add_actor: assertion 'CLUTTER_IS_CONTAINER (container)' failed
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: Object St.Label (0x5610dd9b3b00), has been already deallocated â impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: Object St.Label (0x5610dd9b3b00), has been already deallocated â impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: Object .Gjs_ui_search_ListSearchResults (0x5610dd9a6bf0), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: clutter_actor_show: assertion 'CLUTTER_IS_ACTOR (self)' failed
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: Object St.BoxLayout (0x5610dd9a3f70), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: == Stack trace for context 0x5610db7b8450 ==
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #0   7ffeecf5f640 b   resource:///org/gnome/shell/ui/search.js:332 (8b0ffd38970 @ 22)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #1   7ffeecf5f6f0 b   resource:///org/gnome/shell/ui/search.js:264 (8b0ffd38628 @ 53)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #2   7ffeecf5f7e0 b   resource:///org/gnome/shell/ui/search.js:704 (8b0ffd39da8 @ 71)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #3   7ffeecf5f8b0 b   resource:///org/gnome/shell/ui/search.js:522 (8b0ffd39448 @ 45)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #4   7ffeecf5f980 b   resource:///org/gnome/shell/ui/search.js:557 (8b0ffd396a0 @ 20)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #5   7ffeecf5fa40 b   resource:///org/gnome/shell/ui/remoteSearch.js:255 (8b0ffd3b880 @ 157)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #6   7ffeecf5fb20 b   resource:///org/gnome/shell/ui/remoteSearch.js:269 (8b0ffd3ba60 @ 23)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #7   7ffeecf5fc10 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2df42ce448 @ 312)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: == Stack trace for context 0x5610db7b8450 ==
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: clutter_actor_remove_all_children: assertion 'CLUTTER_IS_ACTOR (self)' failed
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #0   7ffeecf5f6f0 b   resource:///org/gnome/shell/ui/search.js:265 (8b0ffd38628 @ 69)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #1   7ffeecf5f7e0 b   resource:///org/gnome/shell/ui/search.js:704 (8b0ffd39da8 @ 71)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #2   7ffeecf5f8b0 b   resource:///org/gnome/shell/ui/search.js:522 (8b0ffd39448 @ 45)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #3   7ffeecf5f980 b   resource:///org/gnome/shell/ui/search.js:557 (8b0ffd396a0 @ 20)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: Object .Gjs_ui_search_ListSearchResults (0x5610dd9981e0), has been already deallocated â impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #4   7ffeecf5fa40 b   resource:///org/gnome/shell/ui/remoteSearch.js:255 (8b0ffd3b880 @ 157)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #5   7ffeecf5fb20 b   resource:///org/gnome/shell/ui/remoteSearch.js:269 (8b0ffd3ba60 @ 23)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: #6   7ffeecf5fc10 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:132 (2df42ce448 @ 312)
>Mar 26 14:38:22 localhost.localdomain gnome-shell[1797]: clutter_actor_hide: assertion 'CLUTTER_IS_ACTOR (self)' failed

Actions: View

Attachments on bug 1814015: 1674031 | 1674103 | 1674105