[   24.795267] xps gnome-shell[2520]: Running GNOME Shell (using mutter 43.rc) as a Wayland display server
[   30.769616] xps gnome-shell[2520]: Device '/dev/dri/card0' prefers shadow buffer
[   30.777132] xps gnome-shell[2520]: Added device '/dev/dri/card0' (i915) using atomic mode setting.
[   30.779149] xps gnome-shell[2520]: Created gbm renderer for '/dev/dri/card0'
[   30.779226] xps gnome-shell[2520]: Boot VGA GPU /dev/dri/card0 selected as primary
[   33.875187] xps gnome-shell[2520]: Using public X11 display :1024, (using :1025 for managed services)
[   33.875576] xps gnome-shell[2520]: Using Wayland display name 'wayland-0'
[   35.044784] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   35.051409] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   35.058790] xps gnome-shell[2520]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
[   35.059037] xps gnome-shell[2520]: Will monitor session c1
[   35.130633] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   35.169981] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   35.176183] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   35.202204] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   35.261308] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   35.352276] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   35.354830] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   35.355140] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   35.362764] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   35.376172] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   35.376415] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   35.494042] xps gnome-shell[2520]: 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
[   35.494323] xps gnome-shell[2520]: 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
[   35.494585] xps gnome-shell[2520]: 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
[   35.509968] xps org.gnome.Shell.desktop[2520]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/101f9bac455b1f228e166336989898027600000024870000.ms”: No such file or directory
[   35.690198] xps gnome-shell[2520]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
[   36.725976] xps gnome-shell[2520]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   37.118003] xps gnome-shell[2520]: JS ERROR: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
                                      asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
[   37.154326] xps gnome-shell[2520]: ATK Bridge is disabled but a11y has already been enabled.
[   37.449199] xps gnome-shell[2520]: Registering session with GDM
[   39.854629] xps gnome-shell[2520]: JS ERROR: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
                                      asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
[   46.867999] xps gnome-shell[5219]: Running GNOME Shell (using mutter 43.rc) as a Wayland display server
[   46.919693] xps gnome-shell[5219]: Device '/dev/dri/card0' prefers shadow buffer
[   46.923442] xps gnome-shell[5219]: Added device '/dev/dri/card0' (i915) using atomic mode setting.
[   46.925459] xps gnome-shell[5219]: Created gbm renderer for '/dev/dri/card0'
[   46.925595] xps gnome-shell[5219]: Boot VGA GPU /dev/dri/card0 selected as primary
[   47.457365] xps gnome-shell[5219]: Using public X11 display :0, (using :1 for managed services)
[   47.457487] xps gnome-shell[5219]: Using Wayland display name 'wayland-0'
[   47.741357] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   47.748330] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   47.750958] xps gnome-shell[5219]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
[   47.751195] xps gnome-shell[5219]: Will monitor session 2
[   47.784332] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   47.800155] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   47.802193] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   47.878124] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   47.937143] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   47.960860] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   47.963288] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   47.963588] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   47.970038] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   47.980768] xps gnome-shell[5219]: Telepathy is not available, chat integration will be disabled.
[   48.044715] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   48.045021] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   48.202161] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[   48.526014] xps gnome-shell[5219]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
[   48.548259] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[   48.548391] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[   48.548888] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[   48.549051] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[   48.549115] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[   48.549251] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[   48.549312] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[   48.549404] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[   48.549477] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[   48.873820] xps gnome-shell[5219]: Failed to query file info on '/home/fenris/.local/share/icc/.goutputstream-YYLKS1': Error when getting information for file “/home/fenris/.local/share/icc/.goutputstream-YYLKS1”: No such file or directory
[   49.786611] xps gnome-shell[5219]: GNOME Shell started at Fri Sep 16 2022 23:12:04 GMT+0800 (Malaysia Time)
[   49.787423] xps gnome-shell[5219]: Registering session with GDM
[   50.350896] xps gnome-shell[5219]: Launching DING process
[   52.972233] xps gnome-shell[5219]: ATK Bridge is disabled but a11y has already been enabled.
[   53.623155] xps gnome-shell[5219]: DING: Detected async api for thumbnails
[   53.678140] xps gnome-shell[5219]: DING: GNOME nautilus 43.rc
[   94.364214] xps gnome-shell[5219]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
[  115.513672] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[  115.518418] xps ubuntu-appindicators@ubuntu.com[5219]: unable to update icon for software-update-available
[  184.294305] xps gnome-shell[5219]: Could not load a pixbuf from icon theme.
                                      This may indicate that pixbuf loaders or the mime database could not be found.
[ 1349.154046] xps gnome-shell[5219]: JS ERROR: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
                                      asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
[ 1352.910791] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 1352.997295] xps gnome-shell[5219]: Launching DING process
[ 1353.007996] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 1353.011349] xps ubuntu-appindicators@ubuntu.com[5219]: unable to update icon for software-update-available
[ 1353.226393] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[ 1353.227235] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[ 1353.227235] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[ 1353.227235] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[ 1353.227235] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[ 1353.227235] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[ 1353.227235] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[ 1353.227235] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[ 1353.227235] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[ 1353.748952] xps gnome-shell[5219]: DING: Detected async api for thumbnails
[ 1353.792626] xps gnome-shell[5219]: DING: GNOME nautilus 43.rc
[ 5948.893701] xps gnome-shell[5219]: JS ERROR: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
                                      asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
[ 5952.676849] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 5952.759413] xps gnome-shell[5219]: Launching DING process
[ 5952.778901] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 5952.781238] xps ubuntu-appindicators@ubuntu.com[5219]: unable to update icon for software-update-available
[ 5953.024428] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[ 5953.024889] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[ 5953.024978] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[ 5953.024978] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[ 5953.025067] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[ 5953.025116] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[ 5953.025179] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[ 5953.025179] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[ 5953.025398] xps gnome-shell[5219]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[ 5953.527154] xps gnome-shell[5219]: DING: Detected async api for thumbnails
[ 5953.567222] xps gnome-shell[5219]: DING: GNOME nautilus 43.rc
[ 6240.436164] xps gnome-shell[5219]: libinput error: event9  - DLL08B0:01 06CB:CD7A Touchpad: kernel bug: Touch jump detected and discarded.
[ 6240.436164] xps gnome-shell[5219]: See https://wayland.freedesktop.org/libinput/doc/1.21.0/touchpad-jumping-cursors.html for details
[ 6616.888982] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 6616.889876] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 6616.898935] xps gnome-shell[5219]: Received faulty track artist metadata from org.mpris.MediaPlayer2.plasma-browser-integration; expected an array of strings, got UOB (string)
[ 6616.959731] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 6616.960334] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 6626.875904] xps gnome-shell[5219]: Received faulty track artist metadata from org.mpris.MediaPlayer2.plasma-browser-integration; expected an array of strings, got Sweet Life Lanta (string)
[ 6626.954607] xps gnome-shell[5219]: Received faulty track artist metadata from org.mpris.MediaPlayer2.plasma-browser-integration; expected an array of strings, got Sweet Life Lanta (string)
[ 6638.061743] xps gnome-shell[5219]: Received faulty track artist metadata from org.mpris.MediaPlayer2.plasma-browser-integration; expected an array of strings, got BE AMAZED (string)
[ 6638.148528] xps gnome-shell[5219]: Received faulty track artist metadata from org.mpris.MediaPlayer2.plasma-browser-integration; expected an array of strings, got BE AMAZED (string)
[ 6808.675224] xps gnome-shell[5219]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7967.477241] xps gnome-shell[5219]: 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:150:22
                                      _easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:316: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:150:22
                                      _easeActor/<@resource:///org/gnome/shell/ui/environment.js:239:64
[ 7978.347015] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.347275] xps gnome-shell[5219]: The offending signal was access-point-removed on NMDeviceWifi 0x5588a2682400.
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347329] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.347703] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.347751] xps gnome-shell[5219]: The offending signal was access-point-removed on NMDeviceWifi 0x5588a2682400.
[ 7978.347789] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.347828] xps gnome-shell[5219]: The offending signal was notify on NMDeviceEthernet 0x5588a2672280.
[ 7978.347867] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.347906] xps gnome-shell[5219]: The offending signal was notify on NMDeviceEthernet 0x5588a2672280.
[ 7978.347944] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.347982] xps gnome-shell[5219]: The offending signal was notify on NMAccessPoint 0x5588a2671110.
[ 7978.348021] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.348061] xps gnome-shell[5219]: The offending signal was notify on NMAccessPoint 0x5588a2671110.
[ 7978.348099] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.348136] xps gnome-shell[5219]: The offending signal was notify on NMAccessPoint 0x5588a2671110.
[ 7978.348173] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.348210] xps gnome-shell[5219]: The offending signal was notify on NMDeviceWifi 0x5588a2682400.
[ 7978.348251] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.348291] xps gnome-shell[5219]: The offending signal was notify on NMDeviceWifi 0x5588a2682400.
[ 7978.348330] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.348369] xps gnome-shell[5219]: The offending signal was notify on NMDeviceWifi 0x5588a2682400.
[ 7978.348405] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.348442] xps gnome-shell[5219]: The offending signal was notify on NMActiveConnection 0x5588a2686180.
[ 7978.348479] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.348515] xps gnome-shell[5219]: The offending signal was notify on NMActiveConnection 0x5588a2686180.
[ 7978.348553] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.348656] xps gnome-shell[5219]: The offending signal was notify on NMAccessPoint 0x7fa778144240.
[ 7978.348700] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.348739] xps gnome-shell[5219]: The offending signal was state-changed on NMDeviceEthernet 0x5588a2672280.
[ 7978.348777] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.348814] xps gnome-shell[5219]: The offending signal was state-changed on NMDeviceWifi 0x5588a2682400.
[ 7978.348856] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.348895] xps gnome-shell[5219]: The offending signal was state-changed on NMDeviceWifi 0x5588a2682400.
[ 7978.349492] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.349548] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.349591] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349591] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349591] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349591] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349591] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349591] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349591] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349591] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349782] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.349826] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349826] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349826] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349826] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349826] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349826] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.349969] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.350013] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350013] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350013] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350013] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350013] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350013] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350013] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350013] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350202] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.350247] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350247] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350247] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350247] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350247] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350247] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350247] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350247] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350247] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350247] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350481] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.350524] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350524] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350524] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350524] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350524] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350524] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350524] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350524] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350524] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350524] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350524] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350524] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350800] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.350842] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350842] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350842] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350842] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350842] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350842] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350842] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350842] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350842] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350842] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350842] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.350842] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351129] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a02d7870.
[ 7978.351173] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351173] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351173] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351173] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351173] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351173] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351173] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351173] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351173] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351173] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351173] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351173] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351451] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.351500] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351500] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351500] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351500] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351500] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351500] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351500] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351500] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351685] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a02d7870.
[ 7978.351726] xps gnome-shell[5219]: == Stack trace for context 0x55889fd85640 ==
[ 7978.351751] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.351788] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a02d7870.
[ 7978.351822] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.351878] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a02d7870.
[ 7978.351910] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.351943] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5588a0580440.
[ 7978.351976] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352010] xps gnome-shell[5219]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.352044] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352076] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a250aec0.
[ 7978.352108] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352141] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a250aec0.
[ 7978.352176] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352217] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a250aec0.
[ 7978.352258] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352299] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a250aec0.
[ 7978.352339] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352375] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5588a244eae0.
[ 7978.352414] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352451] xps gnome-shell[5219]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.352489] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352526] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a23d17b0.
[ 7978.352563] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352612] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a23d17b0.
[ 7978.352650] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352685] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a23d17b0.
[ 7978.352717] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352756] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a23d17b0.
[ 7978.352792] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352855] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5588a6f7b800.
[ 7978.352890] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352926] xps gnome-shell[5219]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.352961] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.352995] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a24d46e0.
[ 7978.353035] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.353075] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a24d46e0.
[ 7978.353119] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.353159] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a24d46e0.
[ 7978.353198] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.353240] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a24d46e0.
[ 7978.353280] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.353320] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5588a2484f40.
[ 7978.353360] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.353408] xps gnome-shell[5219]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.353454] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.353500] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a2400160.
[ 7978.353550] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.353598] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a2400160.
[ 7978.353646] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.353688] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a2400160.
[ 7978.353736] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.353787] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a2400160.
[ 7978.353833] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.353879] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5588a6f74bc0.
[ 7978.353926] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.353971] xps gnome-shell[5219]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.354019] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.354063] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a6f72870.
[ 7978.354105] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.354147] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a6f72870.
[ 7978.354190] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.354234] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a6f72870.
[ 7978.354284] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.354327] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a6f72870.
[ 7978.354365] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.354405] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5588a1c79f30.
[ 7978.354441] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.354483] xps gnome-shell[5219]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.354526] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.354571] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a1b6e120.
[ 7978.354613] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.354649] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a1b6e120.
[ 7978.354688] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.354730] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a1b6e120.
[ 7978.354769] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.354810] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a1b6e120.
[ 7978.354853] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.354895] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5588a239f990.
[ 7978.354939] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.354977] xps gnome-shell[5219]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.355033] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.355073] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a05e6870.
[ 7978.355111] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.355150] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a05e6870.
[ 7978.355189] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.355226] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a05e6870.
[ 7978.355266] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.355307] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a05e6870.
[ 7978.355353] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.355396] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5588a198f440.
[ 7978.355441] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.355482] xps gnome-shell[5219]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.355521] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.355562] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a6c09c20.
[ 7978.355606] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.355644] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a6c09c20.
[ 7978.355680] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.355718] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a6c09c20.
[ 7978.355756] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.355793] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a6c09c20.
[ 7978.355832] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.355873] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5588a249d9a0.
[ 7978.355913] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.355950] xps gnome-shell[5219]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.355990] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.356031] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a18d9730.
[ 7978.356074] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.356118] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a18d9730.
[ 7978.356159] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.356201] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a18d9730.
[ 7978.356244] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.356290] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a18d9730.
[ 7978.356332] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.356373] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5588a700f080.
[ 7978.356417] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.356460] xps gnome-shell[5219]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.356493] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.356523] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a05a3e70.
[ 7978.356560] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.356794] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a05a3e70.
[ 7978.356890] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.356951] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a05a3e70.
[ 7978.357009] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.357059] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a05a3e70.
[ 7978.357117] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.357175] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5588a2439c10.
[ 7978.357233] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.357284] xps gnome-shell[5219]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.357336] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.357386] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a317c070.
[ 7978.357426] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.357480] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a317c070.
[ 7978.357529] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.357566] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a317c070.
[ 7978.357603] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.357657] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5588a317c070.
[ 7978.357728] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.357841] xps gnome-shell[5219]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5588a2520c40.
[ 7978.357903] xps gnome-shell[5219]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 7978.357943] xps gnome-shell[5219]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x5588a26fd7a0.
[ 7978.357977] xps gnome-shell[5219]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
[ 7978.358052] xps gnome-shell[5219]: The offending callback was set_container(), a vfunc.
[ 7978.358124] xps gnome-shell[5219]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked.
[ 7978.358168] xps gnome-shell[5219]: The offending callback was set_container(), a vfunc.
[ 7979.212284] xps gnome-shell[167161]: Running GNOME Shell (using mutter 43.rc) as a Wayland display server
[ 7979.254789] xps gnome-shell[167161]: Device '/dev/dri/card0' prefers shadow buffer
[ 7979.258585] xps gnome-shell[167161]: Added device '/dev/dri/card0' (i915) using atomic mode setting.
[ 7979.260465] xps gnome-shell[167161]: Created gbm renderer for '/dev/dri/card0'
[ 7979.260518] xps gnome-shell[167161]: Boot VGA GPU /dev/dri/card0 selected as primary
[ 7979.820061] xps gnome-shell[167161]: Using public X11 display :1024, (using :1025 for managed services)
[ 7979.820193] xps gnome-shell[167161]: Using Wayland display name 'wayland-0'
[ 7982.048327] xps gnome-shell[167321]: Running GNOME Shell (using mutter 43.rc) as a X11 window and compositing manager
[ 7982.203908] xps gnome-shell[167321]: ATK Bridge is disabled but a11y has already been enabled.
[ 7982.491665] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7982.498551] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7982.504603] xps gnome-shell[167321]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
[ 7982.504825] xps gnome-shell[167321]: Will monitor session c4
[ 7982.538954] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7982.546568] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7982.549973] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7982.552015] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7982.612721] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7982.633179] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7982.635641] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7982.635865] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7982.642010] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7982.656075] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7982.656262] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7982.660595] xps gnome-shell[167321]: 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
[ 7982.660770] xps gnome-shell[167321]: 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
[ 7982.660940] xps gnome-shell[167321]: 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
[ 7982.679792] xps org.gnome.Shell.desktop[167321]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/107735f9a732d73a6166334905798614900001672900000.ms”: No such file or directory
[ 7982.811005] xps gnome-shell[167321]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
[ 7983.273625] xps gnome-shell[167321]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7983.357129] xps gnome-shell[167321]: JS ERROR: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
                                        asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
[ 7983.830010] xps gnome-shell[167321]: Registering session with GDM
[ 7984.851156] xps gnome-shell[167321]: JS ERROR: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available
                                        asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
[ 7988.743988] xps gnome-shell[167736]: Running GNOME Shell (using mutter 43.rc) as a X11 window and compositing manager
[ 7988.929013] xps gnome-shell[167736]: ATK Bridge is disabled but a11y has already been enabled.
[ 7989.213138] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.220214] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.222366] xps gnome-shell[167736]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
[ 7989.222606] xps gnome-shell[167736]: Will monitor session 9
[ 7989.252448] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.268198] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.270227] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.297899] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.371824] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.396995] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.400244] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.400687] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.408472] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.419098] xps gnome-shell[167736]: Telepathy is not available, chat integration will be disabled.
[ 7989.519511] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.519795] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.555712] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 7989.989520] xps gnome-shell[167736]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
[ 7990.328740] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[ 7990.328842] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[ 7990.328842] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[ 7990.328842] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[ 7990.328842] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[ 7990.328842] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[ 7990.328842] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[ 7990.328977] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[ 7990.328977] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[ 7991.398314] xps gnome-shell[167736]: GNOME Shell started at Sat Sep 17 2022 01:24:25 GMT+0800 (Malaysia Time)
[ 7991.398896] xps gnome-shell[167736]: Registering session with GDM
[ 7991.410625] xps gnome-shell[167736]: Launching DING process
[ 7992.472175] xps gnome-shell[167736]: DING: Detected async api for thumbnails
[ 7992.541071] xps gnome-shell[167736]: DING: GNOME nautilus 43.rc
[ 8016.232782] xps gnome-shell[167736]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
[ 8045.460815] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[ 8045.461067] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[ 8045.461067] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[ 8045.461067] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[ 8045.461067] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[ 8045.461067] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[ 8045.461067] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[ 8045.461067] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[ 8045.461067] xps gnome-shell[167736]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[ 8051.891050] xps gnome-shell[167736]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4
[ 8051.894351] xps ubuntu-appindicators@ubuntu.com[167736]: unable to update icon for software-update-available
[ 8224.601170] xps gnome-shell[167736]: Window manager warning: last_focus_time (8224517) is greater than comparison timestamp (8222125).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[ 8224.601170] xps gnome-shell[167736]: Window manager warning: last_user_time (8224085) is greater than comparison timestamp (8222125).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[ 8224.601170] xps gnome-shell[167736]: Window manager warning: 0x2e00010 appears to be one of the offending windows with a timestamp of 8224085.  Working around...