[ 6.550139] base gnome-shell[1474]: Running GNOME Shell (using mutter 42.9) as a Wayland display server [ 6.634819] base gnome-shell[1474]: Device '/dev/dri/card0' prefers shadow buffer [ 6.636968] base gnome-shell[1474]: Added device '/dev/dri/card0' (amdgpu) using non-atomic mode setting. [ 6.963108] base gnome-shell[1474]: Created gbm renderer for '/dev/dri/card0' [ 6.963207] base gnome-shell[1474]: Boot VGA GPU /dev/dri/card0 selected as primary [ 7.741514] base gnome-shell[1474]: Using public X11 display :1024, (using :1025 for managed services) [ 7.741765] base gnome-shell[1474]: Using Wayland display name 'wayland-0' [ 8.149300] base gnome-shell[1474]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 8.149434] base gnome-shell[1474]: Will monitor session c1 [ 8.415084] base gnome-shell[1474]: Extension ding@rastersoft.com already installed in /usr/share/gnome-shell/extensions/ding@rastersoft.com. /usr/share/gnome-shell/extensions/ding@rastersoft.com will not be loaded [ 8.415208] base gnome-shell[1474]: Extension ubuntu-dock@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com will not be loaded [ 8.415477] base gnome-shell[1474]: Extension ubuntu-appindicators@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com will not be loaded [ 8.445556] base org.gnome.Shell.desktop[1474]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10783ed003b91b067a170289850755594900000014060000.ms”: No such file or directory [ 8.560099] base gnome-shell[1474]: JS ERROR: TypeError: this._managerProxy is undefined _onGeoclueVanished@resource:///org/gnome/shell/ui/status/location.js:169:9 [ 8.606772] base gnome-shell[1474]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 9.231282] base gnome-shell[1474]: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 [ 9.286204] base gnome-shell[1474]: ATK Bridge is disabled but a11y has already been enabled. [ 9.529224] base gnome-shell[1474]: Registering session with GDM [ 14.620667] base gnome-shell[3231]: Running GNOME Shell (using mutter 42.9) as a X11 window and compositing manager [ 14.633505] base gnome-shell[3231]: Enabling experimental feature 'x11-randr-fractional-scaling' [ 14.987950] base gnome-shell[3231]: ATK Bridge is disabled but a11y has already been enabled. [ 15.334317] base gnome-shell[3231]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 15.334455] base gnome-shell[3231]: Will monitor session 2 [ 15.529576] base gnome-shell[3231]: Telepathy is not available, chat integration will be disabled. [ 16.159108] base gnome-shell[3231]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 17.052745] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 17.053333] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 17.053333] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 17.053333] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 17.053333] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 17.053333] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 17.053333] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 17.053333] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 17.053333] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 17.882956] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 17.883228] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 17.883228] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 17.883228] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 17.883228] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 17.883228] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 17.883228] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 17.883228] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 17.883228] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 18.026670] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 18.026670] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 18.026670] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 18.026670] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 18.026670] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 18.026927] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 18.026927] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 18.026927] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 18.026927] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 18.429460] base gnome-shell[3231]: GNOME Shell started at Mon Dec 18 2023 17:21:56 GMT+0600 (+06) [ 18.430482] base gnome-shell[3231]: Registering session with GDM [ 18.835961] base gnome-shell[3231]: DING: Detected async api for thumbnails [ 18.882350] base gnome-shell[3231]: DING: GNOME nautilus 42.6 [ 19.473352] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 19.476114] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 20.216077] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 20.222605] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 39.089178] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 48.850115] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 78.372674] base ubuntu-appindicators@ubuntu.com[3231]: unable to update icon for software-update-available [ 78.377338] base ubuntu-appindicators@ubuntu.com[3231]: unable to update icon for livepatch [ 174.361664] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 188.325457] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 207.396866] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 213.964962] base gnome-shell[3231]: Window manager warning: Window 0x3c00003 sets an MWM hint indicating it isn't resizable, but sets min size 868 x 420 and max size 2147483647 x 2147483647; this doesn't make much sense. [ 214.324954] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3c0002b [ 221.009176] base gnome-shell[3231]: Window manager warning: Window 0x3c00003 sets an MWM hint indicating it isn't resizable, but sets min size 868 x 420 and max size 2147483647 x 2147483647; this doesn't make much sense. [ 221.009546] base gnome-shell[3231]: Window manager warning: Window 0x3c00003 sets an MWM hint indicating it isn't resizable, but sets min size 868 x 420 and max size 2147483647 x 2147483647; this doesn't make much sense. [ 233.709038] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c02aa1 for 0x3c0314b window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 235.885889] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c02aa1 for 0x3c03321 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 237.728788] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c02aa1 for 0x3c035cf window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 248.171499] base gnome-shell[3231]: Object .Gjs_ui_messageTray_Notification (0x55e46b142220), has been already disposed — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [ 248.171858] base gnome-shell[3231]: Object .Gjs_ui_messageTray_Notification (0x55e46b142220), has been already disposed — 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. [ 248.171927] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 248.171927] base gnome-shell[3231]: #0 55e46ca1f138 i resource:///org/gnome/shell/ui/messageTray.js:493 (3a52e6a51f60 @ 69) [ 248.171927] base gnome-shell[3231]: #1 55e46ca1f090 i resource:///org/gnome/shell/ui/messageTray.js:489 (3a52e6a51f10 @ 56) [ 248.171927] base gnome-shell[3231]: #2 55e46ca1f008 i resource:///org/gnome/shell/ui/calendar.js:796 (3a52e6a5e150 @ 22) [ 248.171927] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 248.171927] base gnome-shell[3231]: #0 55e46ca1f138 i resource:///org/gnome/shell/ui/messageTray.js:494 (3a52e6a51f60 @ 84) [ 248.171927] base gnome-shell[3231]: #1 55e46ca1f090 i resource:///org/gnome/shell/ui/messageTray.js:489 (3a52e6a51f10 @ 56) [ 248.171927] base gnome-shell[3231]: #2 55e46ca1f008 i resource:///org/gnome/shell/ui/calendar.js:796 (3a52e6a5e150 @ 22) [ 312.008878] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c08356 for 0x3c088e7 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 312.922428] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c08356 for 0x3c08c39 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 313.207116] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c08356 for 0x3c08ca9 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 313.492326] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c08356 for 0x3c08ca9 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 313.539149] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c08356 for 0x3c08ca9 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 313.579240] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c08356 for 0x3c08ca9 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 313.611314] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c08356 for 0x3c08ca9 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 313.637237] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c08356 for 0x3c08ca9 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 313.661269] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c08356 for 0x3c08ca9 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 313.689003] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c08356 for 0x3c08ca9 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 313.709234] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c08356 for 0x3c08ca9 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 313.738927] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3c08356 for 0x3c08ca9 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3c0183d. [ 324.174301] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 332.956943] base gnome-shell[3231]: Window manager warning: Window 0x4200003 sets an MWM hint indicating it isn't resizable, but sets min size 601 x 301 and max size 2147483647 x 2147483647; this doesn't make much sense. [ 334.063281] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200003 [ 336.075393] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200054 [ 337.876941] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 363.997367] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 393.717830] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 405.488255] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 414.264498] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 464.347389] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 464.859569] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 493.111601] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 496.154930] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 507.933010] base gnome-shell[3231]: Window manager warning: Window 0x3000003 sets an MWM hint indicating it isn't resizable, but sets min size 601 x 301 and max size 2147483647 x 2147483647; this doesn't make much sense. [ 508.769477] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3000003 [ 510.334417] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x300003e [ 515.754085] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 556.866428] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 586.044719] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3001c7c for 0x3001d99 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x300003e. [ 586.292873] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3001c7c for 0x3001d99 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x300003e. [ 618.023084] base gnome-shell[3231]: Window manager warning: WM_TRANSIENT_FOR window 0x3001c7c for 0x3003f84 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x300003e. [ 649.221466] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 650.590125] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 655.145471] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 744.265062] base gnome-shell[3231]: Object .Gjs_ui_search_ListSearchResult (0x55e46bf0c860), has been already disposed — 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. [ 744.266074] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 744.266074] base gnome-shell[3231]: #0 7ffd2ff3e4c0 b resource:///org/gnome/shell/ui/search.js:913 (3a52e6ae4b50 @ 111) [ 744.266074] base gnome-shell[3231]: #1 7ffd2ff3e5c0 b resource:///org/gnome/shell/ui/search.js:824 (3a52e6ae47e0 @ 278) [ 744.266074] base gnome-shell[3231]: #2 7ffd2ff3e670 b resource:///org/gnome/shell/ui/search.js:862 (3a52e6ae49c0 @ 24) [ 744.266074] base gnome-shell[3231]: #3 7ffd2ff3ed80 b resource:///org/gnome/shell/ui/search.js:283 (3a52e6ae34c0 @ 194) [ 744.266074] base gnome-shell[3231]: #4 55e47060e7c8 i resource:///org/gnome/shell/ui/search.js:248 (3a52e6ae3380 @ 399) [ 744.266074] base gnome-shell[3231]: #5 7ffd2ff3fa90 b resource:///org/gnome/shell/ui/appDisplay.js:1858 (3a52e6ac81a0 @ 564) [ 744.266074] base gnome-shell[3231]: #6 7ffd2ff40600 b resource:///org/gnome/shell/ui/search.js:222 (3a52e6ae32e0 @ 177) [ 744.266074] base gnome-shell[3231]: #7 7ffd2ff40c80 b resource:///org/gnome/shell/ui/search.js:266 (3a52e6ae3470 @ 256) [ 744.266074] base gnome-shell[3231]: #8 55e47060e640 i resource:///org/gnome/shell/ui/search.js:511 (3a52e6ae3c40 @ 291) [ 744.266074] base gnome-shell[3231]: #9 7ffd2ff41b90 b resource:///org/gnome/shell/ui/search.js:859 (3a52e6ae4970 @ 71) [ 744.266074] base gnome-shell[3231]: #10 7ffd2ff41c60 b resource:///org/gnome/shell/ui/search.js:650 (3a52e6ae4240 @ 45) [ 744.266074] base gnome-shell[3231]: #11 7ffd2ff41d30 b resource:///org/gnome/shell/ui/search.js:706 (3a52e6ae4510 @ 20) [ 744.266074] base gnome-shell[3231]: #12 55e47060e598 i resource:///org/gnome/shell/ui/appDisplay.js:1894 (3a52e6ac82e0 @ 269) [ 744.266074] base gnome-shell[3231]: #13 7ffd2ff42a40 b resource:///org/gnome/shell/ui/appDisplay.js:1898 (3a52e6ac8470 @ 26) [ 744.266074] base gnome-shell[3231]: #14 7ffd2ff430f0 b resource:///org/gnome/shell/ui/search.js:703 (3a52e6ae44c0 @ 126) [ 744.266074] base gnome-shell[3231]: #15 7ffd2ff43200 b self-hosted:202 (8be717e2ba0 @ 272) [ 744.266074] base gnome-shell[3231]: #16 55e47060e510 i resource:///org/gnome/shell/ui/search.js:698 (3a52e6ae4470 @ 79) [ 744.266074] base gnome-shell[3231]: #17 55e47060e488 i resource:///org/gnome/shell/ui/search.js:725 (3a52e6ae45b0 @ 28) [ 744.266074] base gnome-shell[3231]: #18 7ffd2ff43e20 b self-hosted:1178 (8be717b0a10 @ 398) [ 746.607025] base gnome-shell[3231]: Window manager warning: Window 0x4200003 sets an MWM hint indicating it isn't resizable, but sets min size 601 x 301 and max size 2147483647 x 2147483647; this doesn't make much sense. [ 747.712286] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200003 [ 749.359332] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200046 [ 753.790828] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 760.807169] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200007 [ 762.555997] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 775.608825] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 788.212447] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 789.535554] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 792.657580] base gnome-shell[3231]: Window manager warning: Window 0x4400003 sets an MWM hint indicating it isn't resizable, but sets min size 601 x 301 and max size 2147483647 x 2147483647; this doesn't make much sense. [ 793.570829] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400003 [ 795.331622] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400044 [ 801.514404] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4400439 [ 823.647844] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 828.153255] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 835.903677] base gnome-shell[3231]: Window manager warning: Window 0x4200003 sets an MWM hint indicating it isn't resizable, but sets min size 601 x 301 and max size 2147483647 x 2147483647; this doesn't make much sense. [ 836.758050] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200003 [ 838.287860] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200048 [ 860.057682] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 860.647595] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 861.067007] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 881.925866] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 891.301505] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 891.301505] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 891.301909] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 891.301909] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 891.301909] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 891.301909] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 891.301909] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 891.301909] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 891.301909] base gnome-shell[3231]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 891.855897] base gnome-shell[3231]: Could not load a pixbuf from icon theme. This may indicate that pixbuf loaders or the mime database could not be found. [ 893.756440] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 898.094915] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 951.138795] base gnome-shell[3231]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _registerItem/<@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:106:59 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 _nameOwnerChanged@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:162:14 Async*_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 AppIndicatorsNameWatcher/this._watcherId<@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/util.js:212:22 [ 959.123513] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 975.535108] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 985.530624] base gnome-shell[3231]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _registerItem/<@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:106:59 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 _nameOwnerChanged@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:162:14 Async*_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 AppIndicatorsNameWatcher/this._watcherId<@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/util.js:212:22 [ 986.798448] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 987.677988] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 1103.142644] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 1115.726554] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 1137.328683] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 1156.357628] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 1220.641462] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 1221.642452] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 1230.742245] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 1291.676677] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 1330.336638] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 1331.996661] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 1332.553307] base gnome-shell[3231]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 1342.141015] base gnome-shell[3231]: Can't update stage views actor [:0x55e46ae5e370] is on because it needs an allocation. [ 1342.141475] base gnome-shell[3231]: Can't update stage views actor [:0x55e46cfcd2f0] is on because it needs an allocation. [ 1342.141561] base gnome-shell[3231]: Can't update stage views actor [:0x55e46b891120] is on because it needs an allocation. [ 1344.336841] base gnome-shell[3231]: Can't update stage views actor [:0x55e46ae5e370] is on because it needs an allocation. [ 1344.337726] base gnome-shell[3231]: Can't update stage views actor [:0x55e46cfcd2f0] is on because it needs an allocation. [ 1344.338044] base gnome-shell[3231]: Can't update stage views actor [:0x55e46b891120] is on because it needs an allocation. [ 1363.623056] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.623456] base gnome-shell[3231]: The offending signal was notify on NMDeviceEthernet 0x55e46aefc5d0. [ 1363.623594] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.623736] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.623858] base gnome-shell[3231]: The offending signal was notify on NMActiveConnection 0x55e46d3a8340. [ 1363.623978] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.624183] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.624312] base gnome-shell[3231]: The offending signal was notify on NMActiveConnection 0x55e46d3a8340. [ 1363.624425] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.624543] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.624664] base gnome-shell[3231]: The offending signal was state-changed on NMDeviceEthernet 0x55e46aefc5d0. [ 1363.624783] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.625482] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.625788] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.625917] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.626238] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.626377] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.626495] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.626597] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.626716] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.626832] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.626944] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.627062] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2c2970. [ 1363.627181] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.627279] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.627397] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2c2970. [ 1363.627511] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.627609] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.627729] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2c2970. [ 1363.627841] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.627939] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.628076] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2c2970. [ 1363.628187] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.628290] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.628410] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e46c2d9de0. [ 1363.628530] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.628796] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.628912] base gnome-shell[3231]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.629024] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.629137] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.629252] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2ce9a0. [ 1363.629370] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.629465] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.629583] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2ce9a0. [ 1363.629692] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.629787] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.629899] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2ce9a0. [ 1363.630008] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.630106] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.630219] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2ce9a0. [ 1363.630328] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.630427] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.630541] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e46c2d1400. [ 1363.630656] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.630826] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.630945] base gnome-shell[3231]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.631054] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.631164] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.631277] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46dad3540. [ 1363.631387] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.631482] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.631598] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46dad3540. [ 1363.631716] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.631809] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.631923] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46dad3540. [ 1363.632065] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.632162] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.632274] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46dad3540. [ 1363.632385] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.632485] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.632632] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e47063e320. [ 1363.632747] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.632915] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.633030] base gnome-shell[3231]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.633138] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.633248] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.633360] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2be200. [ 1363.633474] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.633568] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.633680] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2be200. [ 1363.633789] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.633882] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.634000] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2be200. [ 1363.634114] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.634211] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.634323] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2be200. [ 1363.634431] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.634530] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.634647] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e46d3bca40. [ 1363.634755] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.634919] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.635037] base gnome-shell[3231]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.635145] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.635252] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.635368] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46d3ba1c0. [ 1363.635484] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.635576] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.635707] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46d3ba1c0. [ 1363.635820] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.635916] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.636047] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46d3ba1c0. [ 1363.636158] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.636250] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.636372] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46d3ba1c0. [ 1363.636480] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.636578] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.636690] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e46d3b7830. [ 1363.636802] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.636973] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.637088] base gnome-shell[3231]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.637202] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.637312] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.637423] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46dd83780. [ 1363.637536] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.637629] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.637740] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46dd83780. [ 1363.637851] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.637946] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.638057] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46dd83780. [ 1363.638165] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.638259] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.638370] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46dd83780. [ 1363.638478] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.638580] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.638699] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e46c5b4c50. [ 1363.638809] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.638978] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.639092] base gnome-shell[3231]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.639201] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.639316] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.639432] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2b8810. [ 1363.639542] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.639635] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.639751] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2b8810. [ 1363.639858] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.639952] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.640111] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2b8810. [ 1363.640208] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640208] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640208] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640399] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.640506] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640506] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640506] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640506] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640506] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640506] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640506] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640506] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640506] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640506] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640506] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640506] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.640506] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641250] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c2b8810. [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.641354] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.642815] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.642926] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.642926] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.642926] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.642926] base gnome-shell[3231]: == Stack trace for context 0x55e46abee190 == [ 1363.643162] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e46c29ab70. [ 1363.643260] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.643352] base gnome-shell[3231]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.643441] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.643533] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46acefa90. [ 1363.643628] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.643730] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46acefa90. [ 1363.643820] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.643907] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46acefa90. [ 1363.643994] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.644140] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46acefa90. [ 1363.644229] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.644319] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e46acb1170. [ 1363.644415] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.644507] base gnome-shell[3231]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.644597] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.644688] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c29a4b0. [ 1363.644777] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.644863] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c29a4b0. [ 1363.644951] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.645040] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c29a4b0. [ 1363.645128] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.645214] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46c29a4b0. [ 1363.645300] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.645388] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e46d97d120. [ 1363.645478] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.645565] base gnome-shell[3231]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.645651] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.645740] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46da3ee10. [ 1363.645828] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.645915] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46da3ee10. [ 1363.645999] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.646094] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46da3ee10. [ 1363.646182] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.646268] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46da3ee10. [ 1363.646355] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.646445] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e46b672e40. [ 1363.646533] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.646621] base gnome-shell[3231]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.646710] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.646797] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46d37eac0. [ 1363.646882] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.646970] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46d37eac0. [ 1363.647056] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.647145] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46d37eac0. [ 1363.647233] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.647323] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46d37eac0. [ 1363.647412] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.647502] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e46d3b6340. [ 1363.647591] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.647677] base gnome-shell[3231]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e46d745a60. [ 1363.647763] base gnome-shell[3231]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. [ 1363.647859] base gnome-shell[3231]: The offending callback was set_container(), a vfunc. [ 1363.647948] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.648204] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55e46c2ca2c0. [ 1363.648371] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.648483] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55e46c2ca2c0. [ 1363.648568] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.648729] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55e46c2ca2c0. [ 1363.648823] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.648913] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46b389060. [ 1363.649003] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.649097] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46b389060. [ 1363.649183] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.649271] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46b389060. [ 1363.649365] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.649453] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46b389060. [ 1363.649539] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.649625] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e46dd64aa0. [ 1363.649712] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.649798] base gnome-shell[3231]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e46c2ca2c0. [ 1363.649904] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.649996] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46dcf0630. [ 1363.650100] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.650189] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46dcf0630. [ 1363.650276] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.650362] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46dcf0630. [ 1363.650453] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.650545] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55e46dcf0630. [ 1363.650632] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.650717] base gnome-shell[3231]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55e46cffe770. [ 1363.650818] base gnome-shell[3231]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1363.650903] base gnome-shell[3231]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55e46c2ca2c0. [ 1363.650988] base gnome-shell[3231]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. [ 1363.651108] base gnome-shell[3231]: The offending callback was set_container(), a vfunc. [ 1364.612238] base gnome-shell[37664]: Running GNOME Shell (using mutter 42.9) as a Wayland display server [ 1364.632389] base gnome-shell[37664]: Device '/dev/dri/card0' prefers shadow buffer [ 1364.634678] base gnome-shell[37664]: Added device '/dev/dri/card0' (amdgpu) using non-atomic mode setting. [ 1364.677421] base gnome-shell[37664]: Created gbm renderer for '/dev/dri/card0' [ 1364.677549] base gnome-shell[37664]: Boot VGA GPU /dev/dri/card0 selected as primary [ 1365.397336] base gnome-shell[37664]: Using public X11 display :1024, (using :1025 for managed services) [ 1365.397528] base gnome-shell[37664]: Using Wayland display name 'wayland-0' [ 1365.632433] base gnome-shell[37664]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 1365.632721] base gnome-shell[37664]: Will monitor session c2 [ 1365.784532] base gnome-shell[37664]: Extension ding@rastersoft.com already installed in /usr/share/gnome-shell/extensions/ding@rastersoft.com. /usr/share/gnome-shell/extensions/ding@rastersoft.com will not be loaded [ 1365.784672] base gnome-shell[37664]: Extension ubuntu-dock@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com will not be loaded [ 1365.784838] base gnome-shell[37664]: Extension ubuntu-appindicators@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com will not be loaded [ 1365.798474] base org.gnome.Shell.desktop[37664]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10f98828b3b5265ee9170289986567101100000376070000.ms”: No such file or directory [ 1365.876528] base gnome-shell[37664]: JS ERROR: TypeError: this._managerProxy is undefined _onGeoclueVanished@resource:///org/gnome/shell/ui/status/location.js:169:9 [ 1365.906929] base gnome-shell[37664]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 1366.312117] base gnome-shell[37664]: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 [ 1366.331619] base gnome-shell[37664]: ATK Bridge is disabled but a11y has already been enabled. [ 1366.697202] base gnome-shell[37664]: Registering session with GDM [ 1374.074582] base gnome-shell[38088]: Running GNOME Shell (using mutter 42.9) as a Wayland display server [ 1374.097526] base gnome-shell[38088]: Device '/dev/dri/card0' prefers shadow buffer [ 1374.100093] base gnome-shell[38088]: Added device '/dev/dri/card0' (amdgpu) using non-atomic mode setting. [ 1374.101675] base gnome-shell[38088]: Enabling experimental feature 'x11-randr-fractional-scaling' [ 1374.145765] base gnome-shell[38088]: Created gbm renderer for '/dev/dri/card0' [ 1374.145976] base gnome-shell[38088]: Boot VGA GPU /dev/dri/card0 selected as primary [ 1374.736800] base gnome-shell[38088]: Using public X11 display :0, (using :1 for managed services) [ 1374.736938] base gnome-shell[38088]: Using Wayland display name 'wayland-0' [ 1374.961400] base gnome-shell[38088]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 1374.961623] base gnome-shell[38088]: Will monitor session 9 [ 1375.133310] base gnome-shell[38088]: Telepathy is not available, chat integration will be disabled. [ 1375.564282] base gnome-shell[38088]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 1375.777382] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 1375.777617] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 1375.777808] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 1375.778098] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 1375.778235] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 1375.778366] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 1375.778604] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 1375.778745] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 1375.778864] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 1376.947346] base gnome-shell[38088]: ATK Bridge is disabled but a11y has already been enabled. [ 1377.051488] base gnome-shell[38088]: GNOME Shell started at Mon Dec 18 2023 17:44:36 GMT+0600 (+06) [ 1377.052434] base gnome-shell[38088]: Registering session with GDM [ 1377.421811] base gnome-shell[38088]: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed [ 1377.665332] base gnome-shell[38088]: DING: Detected async api for thumbnails [ 1377.721225] base gnome-shell[38088]: DING: GNOME nautilus 42.6 [ 1380.197157] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 1380.203221] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 1395.404188] base gnome-shell[38088]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 1396.566680] base gnome-shell[38088]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 1396.567762] base gnome-shell[38088]: Window manager warning: Ping serial 1396566 was reused for window W5, previous use was for window W6. [ 1426.803997] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 1436.841072] base gnome-shell[38088]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 1438.522072] base ubuntu-appindicators@ubuntu.com[38088]: unable to update icon for software-update-available [ 1438.527075] base ubuntu-appindicators@ubuntu.com[38088]: unable to update icon for livepatch [ 1463.852339] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 1547.404537] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 1562.648695] base gnome-shell[38088]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 1571.053178] base gnome-shell[38088]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 1593.834977] base ubuntu-appindicators@ubuntu.com[38088]: unable to update icon for spotify-client [ 1600.335452] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 1627.530349] base gnome-shell[38088]: Removing a network device that was not added [ 1629.411335] base gnome-shell[38088]: Removing a network device that was not added [ 1643.595122] base gnome-shell[38088]: Removing a network device that was not added [ 1657.943922] base gnome-shell[38088]: Removing a network device that was not added [ 1710.571598] base gnome-shell[38088]: Removing a network device that was not added [ 1733.148846] base gnome-shell[38088]: Removing a network device that was not added [ 2234.404940] base gnome-shell[38088]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 2243.927112] base gnome-shell[38088]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 2291.457211] base gnome-shell[38088]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _registerItem/<@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:106:59 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 _nameOwnerChanged@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:162:14 Async*_emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 AppIndicatorsNameWatcher/this._watcherId<@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/util.js:212:22 [ 2300.808875] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 2346.048533] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 2358.510379] base gnome-shell[38088]: Object .Gjs_ui_messageTray_Notification (0x564d3f908e60), has been already disposed — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. [ 2358.510939] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 2358.510939] base gnome-shell[38088]: #0 564d42d9a148 i resource:///org/gnome/shell/ui/messageTray.js:493 (3dfdac351f60 @ 69) [ 2358.510939] base gnome-shell[38088]: #1 564d42d9a0a0 i resource:///org/gnome/shell/ui/messageTray.js:489 (3dfdac351f10 @ 56) [ 2358.510939] base gnome-shell[38088]: #2 564d42d9a018 i resource:///org/gnome/shell/ui/calendar.js:796 (3dfdac35e150 @ 22) [ 2358.510939] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 2358.510939] base gnome-shell[38088]: #0 564d42d9a148 i resource:///org/gnome/shell/ui/messageTray.js:494 (3dfdac351f60 @ 84) [ 2358.510939] base gnome-shell[38088]: #1 564d42d9a0a0 i resource:///org/gnome/shell/ui/messageTray.js:489 (3dfdac351f10 @ 56) [ 2358.510939] base gnome-shell[38088]: #2 564d42d9a018 i resource:///org/gnome/shell/ui/calendar.js:796 (3dfdac35e150 @ 22) [ 2358.511504] base gnome-shell[38088]: Object .Gjs_ui_messageTray_Notification (0x564d3f908e60), has been already disposed — 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. [ 2369.400065] base gnome-shell[38088]: libinput error: event9 - COMPANY USB Device Keyboard: client bug: event processing lagging behind by 39ms, your system is too slow [ 2369.483583] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 2390.524838] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 2431.625469] base gnome-shell[38088]: Could not create transient scope for PID 53671: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 53671 does not exist. [ 2432.370275] base ubuntu-appindicators@ubuntu.com[38088]: unable to update icon for Skype1 [ 2434.829621] base ubuntu-appindicators@ubuntu.com[38088]: Skype1, Impossible to lookup icon for 'Skype1_2-panel' in path /tmp/.org.chromium.Chromium.FGMLUT [ 2434.841222] base ubuntu-appindicators@ubuntu.com[38088]: unable to update icon for Skype1 [ 2434.873764] base ubuntu-appindicators@ubuntu.com[38088]: Skype1, Impossible to lookup icon for 'Skype1_2-panel' in path /tmp/.org.chromium.Chromium.FGMLUT [ 2434.883414] base ubuntu-appindicators@ubuntu.com[38088]: unable to update icon for Skype1 [ 2435.001533] base ubuntu-appindicators@ubuntu.com[38088]: Skype1, Impossible to lookup icon for 'Skype1_2-panel' in path /tmp/.org.chromium.Chromium.FGMLUT [ 2435.013737] base ubuntu-appindicators@ubuntu.com[38088]: Skype1, Impossible to lookup icon for 'Skype1_2-panel' in path /tmp/.org.chromium.Chromium.FGMLUT [ 2435.015069] base ubuntu-appindicators@ubuntu.com[38088]: unable to update icon for Skype1 [ 2435.015295] base ubuntu-appindicators@ubuntu.com[38088]: unable to update icon for Skype1 [ 2435.112798] base ubuntu-appindicators@ubuntu.com[38088]: Skype1, Impossible to lookup icon for 'Skype1_6-panel' in path /tmp/.org.chromium.Chromium.McyWmV [ 2435.124091] base ubuntu-appindicators@ubuntu.com[38088]: unable to update icon for Skype1 [ 5701.950205] base gnome-shell[38088]: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 [ 5708.458655] base ubuntu-appindicators@ubuntu.com[38088]: unable to update icon for software-update-available [ 5708.458935] base ubuntu-appindicators@ubuntu.com[38088]: unable to update icon for livepatch [ 5708.459128] base ubuntu-appindicators@ubuntu.com[38088]: unable to update icon for spotify-client [ 5708.459347] base ubuntu-appindicators@ubuntu.com[38088]: unable to update icon for Skype1 [ 5708.729045] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 5708.729390] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 5708.729626] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 5708.729721] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 5708.729772] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 5708.729852] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 5708.729903] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 5708.729940] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 5708.730063] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 5709.347288] base gnome-shell[38088]: DING: Detected async api for thumbnails [ 5709.395774] base gnome-shell[38088]: DING: GNOME nautilus 42.6 [ 5728.875136] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 5836.283703] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 5836.284340] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 5836.284651] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 5836.284708] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 5836.284831] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 5836.285009] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 5836.285064] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 5836.285064] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 5836.285348] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 5856.643319] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 5856.650096] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 5856.650096] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 5856.650096] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 5856.650096] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 5856.650096] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 5856.650096] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 5856.650096] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 5856.650096] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 5862.190759] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 5862.191398] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 5862.191717] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 5862.191841] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 5862.191893] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 5862.192082] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 5862.192156] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 5862.192156] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 5862.192395] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 5876.796228] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 5876.796689] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 5876.796968] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 5876.797043] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 5876.797093] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 5876.797238] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 5876.797311] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 5876.797311] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 5876.797490] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 5878.776302] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 5878.776978] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 5878.777284] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 5878.777350] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 5878.777494] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 5878.777664] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 5878.777730] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 5878.777730] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 5878.777997] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 5883.929861] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 5883.930226] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 5883.930493] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 5883.930548] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 5883.930586] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 5883.930730] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 5883.930782] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 5883.930782] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 5883.930950] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 5886.883932] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 5886.884585] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 5886.884871] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 5886.884922] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 5886.885021] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 5886.885178] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 5886.885230] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 5886.885230] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 5886.885438] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 5897.365058] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 5897.365477] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 5897.365779] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 5897.365845] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 5897.365896] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 5897.366039] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 5897.366118] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 5897.366118] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 5897.366311] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 5915.316613] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 6391.316107] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 6391.321886] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 6391.321886] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 6391.321886] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 6391.321886] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 6391.321886] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 6391.321886] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 6391.321886] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 6391.321886] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 6396.922959] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 6396.923361] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 6396.923603] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 6396.923697] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 6396.923756] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 6396.923849] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 6396.923895] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 6396.923928] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 6396.924089] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 6397.660823] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 6397.661451] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 6397.661759] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 6397.661837] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 6397.661965] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 6397.662163] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 6397.662228] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 6397.662228] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 6397.662472] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 6401.282968] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 6401.283414] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 6401.283509] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 6401.283600] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 6401.283645] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 6401.283763] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 6401.283813] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 6401.283813] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 6401.283959] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 6442.543857] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 6442.544514] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 6442.544824] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 6442.544902] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 6442.545028] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 6442.545229] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 6442.545300] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 6442.545300] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 6442.545542] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 6464.448055] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 6464.453761] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 6464.453761] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 6464.453761] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 6464.453761] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 6464.453761] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 6464.453761] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 6464.453761] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 6464.453761] base gnome-shell[38088]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 6761.206959] base gnome-shell[38088]: JS ERROR: TypeError: this.actor is null _syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:138:25 onStopped@resource:///org/gnome/shell/ui/windowManager.js:150:35 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:151:22 _easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:317:60 _destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1596:21 onStopped@resource:///org/gnome/shell/ui/windowManager.js:1564:39 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:151:22 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:240:64 [ 6951.396293] base gnome-shell[38088]: libinput error: event9 - COMPANY USB Device Keyboard: client bug: event processing lagging behind by 32ms, your system is too slow [ 6964.920550] base gnome-shell[38088]: D-Bus client with active sessions vanished [ 6964.922682] base gnome-shell[38088]: Error stopping screencast: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying [ 7009.690983] base gnome-shell[38088]: D-Bus client with active sessions vanished [ 7009.693172] base gnome-shell[38088]: Error stopping screencast: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying [ 7050.775257] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 7058.338859] base gnome-shell[38088]: D-Bus client with active sessions vanished [ 7058.340082] base gnome-shell[38088]: Error stopping screencast: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying [ 7086.892812] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 7107.835445] base gnome-shell[38088]: D-Bus client with active sessions vanished [ 7107.836704] base gnome-shell[38088]: Error stopping screencast: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying [ 7108.527505] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 7108.527874] base gnome-shell[38088]: Window manager warning: Ping serial 7108517 was reused for window W18, previous use was for window 0xa0000b. [ 7145.573460] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 7189.965012] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 7205.574526] base gnome-shell[38088]: D-Bus client with active sessions vanished [ 7205.575908] base gnome-shell[38088]: Error stopping screencast: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying [ 7206.112469] base gnome-shell[38088]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b [ 7262.284358] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.284838] base gnome-shell[38088]: The offending signal was notify on NMDeviceEthernet 0x564d417ca300. [ 7262.284950] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.284950] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.284950] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.284950] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.285184] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.285274] base gnome-shell[38088]: The offending signal was notify on NMActiveConnection 0x564d417d1c00. [ 7262.285377] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.285472] base gnome-shell[38088]: The offending signal was notify on NMActiveConnection 0x564d417d1c00. [ 7262.285559] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.285646] base gnome-shell[38088]: The offending signal was state-changed on NMDeviceEthernet 0x564d417ca300. [ 7262.290168] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.290348] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.290457] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.290457] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.290457] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.290457] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.290457] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.290457] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.290457] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.290457] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.290457] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.290457] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.290955] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291057] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291708] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.291784] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291784] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291784] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291784] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291784] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291784] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291784] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291784] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291784] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291784] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.291784] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292219] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292309] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292906] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.292987] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293581] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.293658] base gnome-shell[38088]: == Stack trace for context 0x564d3f54d4b0 == [ 7262.294257] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d42b7f860. [ 7262.294343] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.294419] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d42b7f860. [ 7262.294520] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.294676] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d42b7f860. [ 7262.294760] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.294836] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d42b7f860. [ 7262.294917] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.294993] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564d437ed430. [ 7262.295076] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.295147] base gnome-shell[38088]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.295232] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.295306] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d437f5c60. [ 7262.295380] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.295450] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d437f5c60. [ 7262.295521] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.295592] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d437f5c60. [ 7262.296581] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.296775] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d437f5c60. [ 7262.297000] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.297137] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564d437f8030. [ 7262.297287] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.297425] base gnome-shell[38088]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.297567] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.297710] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d43b90460. [ 7262.297862] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.297983] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d43b90460. [ 7262.298063] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.298136] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d43b90460. [ 7262.298210] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.298279] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d43b90460. [ 7262.298361] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.298435] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564d43b93830. [ 7262.298516] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.298590] base gnome-shell[38088]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.298659] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.298733] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d4273d260. [ 7262.298815] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.298891] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d4273d260. [ 7262.298968] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.299051] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d4273d260. [ 7262.299128] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.299203] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d4273d260. [ 7262.299276] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.299354] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564d41350310. [ 7262.299432] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.299500] base gnome-shell[38088]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.299566] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.299642] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41d6f540. [ 7262.299718] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.299795] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41d6f540. [ 7262.299866] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.299939] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41d6f540. [ 7262.300078] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.300203] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41d6f540. [ 7262.300325] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.300442] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564d41d745b0. [ 7262.300568] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.300685] base gnome-shell[38088]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.300803] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.300937] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41d90150. [ 7262.301060] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.301177] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41d90150. [ 7262.301297] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.301414] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41d90150. [ 7262.301530] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.301648] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41d90150. [ 7262.301764] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.301887] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564d41d92160. [ 7262.302004] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.302162] base gnome-shell[38088]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.302285] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.302430] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41da5cb0. [ 7262.302558] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.302700] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41da5cb0. [ 7262.304030] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.304227] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41da5cb0. [ 7262.304351] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.304470] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41da5cb0. [ 7262.304590] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.304964] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564d41dadce0. [ 7262.305107] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.305232] base gnome-shell[38088]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.305394] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.305513] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41dc1dd0. [ 7262.305639] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.305757] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41dc1dd0. [ 7262.305919] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.306036] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41dc1dd0. [ 7262.306158] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.306275] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41dc1dd0. [ 7262.306390] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.306515] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564d41dc4e00. [ 7262.306636] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.306753] base gnome-shell[38088]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.306871] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.306991] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41de7470. [ 7262.307110] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.307227] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41de7470. [ 7262.307348] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.307464] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41de7470. [ 7262.307582] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.307707] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41de7470. [ 7262.307823] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.307938] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564d3fbb3430. [ 7262.308436] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.308558] base gnome-shell[38088]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.308661] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.308732] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41ec47e0. [ 7262.308848] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.308920] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41ec47e0. [ 7262.308989] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.309052] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41ec47e0. [ 7262.309150] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.309241] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41ec47e0. [ 7262.309305] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.309365] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564d41f051c0. [ 7262.309426] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.309512] base gnome-shell[38088]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.309600] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.309662] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41f32890. [ 7262.309750] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.309863] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41f32890. [ 7262.309951] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.310039] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41f32890. [ 7262.310104] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.310160] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d41f32890. [ 7262.310211] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.310265] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564d41f4b120. [ 7262.310369] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.310475] base gnome-shell[38088]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564d441e0e40. [ 7262.310592] base gnome-shell[38088]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. [ 7262.310699] base gnome-shell[38088]: The offending callback was set_container(), a vfunc. [ 7262.310801] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.310902] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x564d4201d490. [ 7262.311038] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.311142] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x564d4201d490. [ 7262.311208] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.311261] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x564d4201d490. [ 7262.311315] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.311403] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d420538e0. [ 7262.311497] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.311592] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d420538e0. [ 7262.311676] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.311743] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d420538e0. [ 7262.311799] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.311858] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d420538e0. [ 7262.311915] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.311966] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564d42089360. [ 7262.312033] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.312086] base gnome-shell[38088]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564d4201d490. [ 7262.312137] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.312191] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d420e8530. [ 7262.312246] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.312302] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d420e8530. [ 7262.312365] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.312423] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d420e8530. [ 7262.312477] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.312667] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564d420e8530. [ 7262.312771] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.312855] base gnome-shell[38088]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564d4212d780. [ 7262.312985] base gnome-shell[38088]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7262.313049] base gnome-shell[38088]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564d4201d490. [ 7262.313105] base gnome-shell[38088]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. [ 7262.313189] base gnome-shell[38088]: The offending callback was set_container(), a vfunc. [ 7263.199630] base gnome-shell[100426]: Running GNOME Shell (using mutter 42.9) as a Wayland display server [ 7263.237668] base gnome-shell[100426]: Device '/dev/dri/card0' prefers shadow buffer [ 7263.239956] base gnome-shell[100426]: Added device '/dev/dri/card0' (amdgpu) using non-atomic mode setting. [ 7263.283962] base gnome-shell[100426]: Created gbm renderer for '/dev/dri/card0' [ 7263.284172] base gnome-shell[100426]: Boot VGA GPU /dev/dri/card0 selected as primary [ 7263.919428] base gnome-shell[100426]: Using public X11 display :1024, (using :1025 for managed services) [ 7263.919616] base gnome-shell[100426]: Using Wayland display name 'wayland-0' [ 7264.153522] base gnome-shell[100426]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 7264.153718] base gnome-shell[100426]: Will monitor session c3 [ 7264.305476] base gnome-shell[100426]: Extension ding@rastersoft.com already installed in /usr/share/gnome-shell/extensions/ding@rastersoft.com. /usr/share/gnome-shell/extensions/ding@rastersoft.com will not be loaded [ 7264.305720] base gnome-shell[100426]: Extension ubuntu-dock@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com will not be loaded [ 7264.305780] base gnome-shell[100426]: Extension ubuntu-appindicators@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com will not be loaded [ 7264.316532] base org.gnome.Shell.desktop[100426]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/102c427be4d30bcf0f170290576425272600001003790000.ms”: No such file or directory [ 7264.402561] base gnome-shell[100426]: JS ERROR: TypeError: this._managerProxy is undefined _onGeoclueVanished@resource:///org/gnome/shell/ui/status/location.js:169:9 [ 7264.471661] base gnome-shell[100426]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 7264.859494] base gnome-shell[100426]: ATK Bridge is disabled but a11y has already been enabled. [ 7264.943767] base gnome-shell[100426]: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 [ 7265.455531] base gnome-shell[100426]: Registering session with GDM [ 7269.897159] base gnome-shell[100837]: Running GNOME Shell (using mutter 42.9) as a Wayland display server [ 7269.921788] base gnome-shell[100837]: Device '/dev/dri/card0' prefers shadow buffer [ 7269.926746] base gnome-shell[100837]: Added device '/dev/dri/card0' (amdgpu) using non-atomic mode setting. [ 7269.928098] base gnome-shell[100837]: Enabling experimental feature 'x11-randr-fractional-scaling' [ 7269.970033] base gnome-shell[100837]: Created gbm renderer for '/dev/dri/card0' [ 7269.970478] base gnome-shell[100837]: Boot VGA GPU /dev/dri/card0 selected as primary [ 7270.614083] base gnome-shell[100837]: Using public X11 display :0, (using :1 for managed services) [ 7270.614244] base gnome-shell[100837]: Using Wayland display name 'wayland-0' [ 7270.835884] base gnome-shell[100837]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 7270.836092] base gnome-shell[100837]: Will monitor session 27 [ 7270.991245] base gnome-shell[100837]: Telepathy is not available, chat integration will be disabled. [ 7271.410674] base gnome-shell[100837]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 7271.583155] base gnome-shell[100837]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 7271.583334] base gnome-shell[100837]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 7271.583393] base gnome-shell[100837]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 7271.583439] base gnome-shell[100837]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 7271.583439] base gnome-shell[100837]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 7271.583506] base gnome-shell[100837]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 7271.583993] base gnome-shell[100837]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 7271.583993] base gnome-shell[100837]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 7271.583993] base gnome-shell[100837]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 7272.603762] base gnome-shell[100837]: GNOME Shell started at Mon Dec 18 2023 19:22:52 GMT+0600 (+06) [ 7272.604579] base gnome-shell[100837]: Registering session with GDM [ 7272.911341] base gnome-shell[100837]: ATK Bridge is disabled but a11y has already been enabled. [ 7273.343629] base gnome-shell[100837]: DING: Detected async api for thumbnails [ 7273.408181] base gnome-shell[100837]: DING: GNOME nautilus 42.6 [ 7273.447956] base gnome-shell[100837]: clutter_actor_iter_next: assertion 'ri->age == ri->root->priv->age' failed [ 7276.980254] base gnome-shell[100837]: endSessionDialog: No XDG_SESSION_ID, fetched from logind: 27 [ 7278.028324] base gnome-shell[100837]: Ignored exception from dbus method: Gio.IOErrorEnum: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code19: Operation was cancelled [ 7281.042194] base gnome-shell[100837]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7281.042445] base gnome-shell[100837]: The offending signal was notify on NMDeviceEthernet 0x55ec9e5302d0. [ 7281.042502] base gnome-shell[100837]: == Stack trace for context 0x55ec9c2804a0 == [ 7281.042502] base gnome-shell[100837]: == Stack trace for context 0x55ec9c2804a0 == [ 7281.042502] base gnome-shell[100837]: == Stack trace for context 0x55ec9c2804a0 == [ 7281.042502] base gnome-shell[100837]: == Stack trace for context 0x55ec9c2804a0 == [ 7281.042630] base gnome-shell[100837]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7281.042678] base gnome-shell[100837]: The offending signal was notify on NMActiveConnection 0x55ec9e534180. [ 7281.042723] base gnome-shell[100837]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7281.042773] base gnome-shell[100837]: The offending signal was notify on NMActiveConnection 0x55ec9e534180. [ 7281.042818] base gnome-shell[100837]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 7281.042867] base gnome-shell[100837]: The offending signal was state-changed on NMDeviceEthernet 0x55ec9e5302d0. [ 7281.697425] base gnome-shell[101429]: Running GNOME Shell (using mutter 42.9) as a Wayland display server [ 7281.717330] base gnome-shell[101429]: Device '/dev/dri/card0' prefers shadow buffer [ 7281.719680] base gnome-shell[101429]: Added device '/dev/dri/card0' (amdgpu) using non-atomic mode setting. [ 7281.759926] base gnome-shell[101429]: Created gbm renderer for '/dev/dri/card0' [ 7281.760133] base gnome-shell[101429]: Boot VGA GPU /dev/dri/card0 selected as primary [ 7282.591143] base gnome-shell[101429]: Using public X11 display :1024, (using :1025 for managed services) [ 7282.591293] base gnome-shell[101429]: Using Wayland display name 'wayland-0' [ 7282.824124] base gnome-shell[101429]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 7282.824349] base gnome-shell[101429]: Will monitor session c4 [ 7282.970842] base gnome-shell[101429]: Failed to create file /run/user/119/gnome-shell-disable-extensions: Error opening file “/run/user/119/gnome-shell-disable-extensions”: File exists [ 7282.973064] base gnome-shell[101429]: Extension ding@rastersoft.com already installed in /usr/share/gnome-shell/extensions/ding@rastersoft.com. /usr/share/gnome-shell/extensions/ding@rastersoft.com will not be loaded [ 7282.973176] base gnome-shell[101429]: Extension ubuntu-dock@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com will not be loaded [ 7282.973344] base gnome-shell[101429]: Extension ubuntu-appindicators@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com will not be loaded [ 7282.985921] base org.gnome.Shell.desktop[101429]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10ba88d5858c2d8808170290578274526100001014230000.ms”: No such file or directory [ 7283.108466] base gnome-shell[101429]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 7283.428666] base gnome-shell[101429]: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 [ 7283.504164] base gnome-shell[101429]: ATK Bridge is disabled but a11y has already been enabled. [ 7283.935397] base gnome-shell[101429]: Registering session with GDM [ 7291.881878] base gnome-shell[101851]: Running GNOME Shell (using mutter 42.9) as a X11 window and compositing manager [ 7291.894861] base gnome-shell[101851]: Enabling experimental feature 'x11-randr-fractional-scaling' [ 7292.341617] base gnome-shell[101851]: ATK Bridge is disabled but a11y has already been enabled. [ 7292.667638] base gnome-shell[101851]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 7292.667845] base gnome-shell[101851]: Will monitor session 28 [ 7292.843290] base gnome-shell[101851]: Telepathy is not available, chat integration will be disabled. [ 7292.971835] base gnome-shell[101851]: Failed to create file /run/user/1000/gnome-shell-disable-extensions: Error opening file “/run/user/1000/gnome-shell-disable-extensions”: File exists [ 7293.417458] base gnome-shell[101851]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 7294.417824] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 7294.417824] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 7294.422100] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 7294.422100] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 7294.422100] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 7294.422100] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 7294.422100] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 7294.422100] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 7294.422100] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 7295.219202] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 7295.219202] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 7295.219342] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 7295.219342] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 7295.219342] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 7295.219342] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 7295.219342] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 7295.219342] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 7295.219342] base gnome-shell[101851]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 7295.625692] base gnome-shell[101851]: GNOME Shell started at Mon Dec 18 2023 19:23:14 GMT+0600 (+06) [ 7295.626379] base gnome-shell[101851]: Registering session with GDM [ 7296.043046] base gnome-shell[101851]: DING: Detected async api for thumbnails [ 7296.102075] base gnome-shell[101851]: DING: GNOME nautilus 42.6 [ 7303.012496] base gnome-shell[101851]: D-Bus client with active sessions vanished [ 7303.013893] base gnome-shell[101851]: Error stopping screencast: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying [ 7306.137372] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7306.151314] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7306.885563] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7306.895512] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7316.428320] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7320.722710] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7329.389594] base gnome-shell[101851]: D-Bus client with active sessions vanished [ 7329.390933] base gnome-shell[101851]: Error stopping screencast: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying [ 7329.851531] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7356.093354] base ubuntu-appindicators@ubuntu.com[101851]: unable to update icon for software-update-available [ 7356.098133] base ubuntu-appindicators@ubuntu.com[101851]: unable to update icon for livepatch [ 7376.039655] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7436.001245] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7437.061611] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7478.042181] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7478.959669] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7479.519785] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7495.092083] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7554.634894] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7557.752681] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7558.063018] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7560.482476] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7570.042057] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7576.823779] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7577.146624] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7577.553345] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7589.044242] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7594.602946] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7626.933106] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7629.130155] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b [ 7641.180195] base gnome-shell[101851]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0000b