-- Journal begins at Thu 2019-04-11 18:28:36 CEST, ends at Wed 2021-03-31 11:44:16 CEST. -- [ 6.044423] vali gnome-shell[1034]: Boot VGA GPU /dev/dri/card0 selected as primary [ 6.614016] vali gnome-shell[1034]: Skipping parental controls support as it’s disabled [ 6.909502] vali gnome-shell[1034]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 6.910063] vali gnome-shell[1034]: Will monitor session 1 [ 7.431612] vali gnome-shell[1034]: Telepathy is not available, chat integration will be disabled. [ 8.088900] vali gnome-shell[1034]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 9.110175] vali gnome-shell[1034]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 9.110752] vali gnome-shell[1034]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 9.110752] vali gnome-shell[1034]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 9.111018] vali gnome-shell[1034]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 9.111018] vali gnome-shell[1034]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 9.111168] vali gnome-shell[1034]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 9.111233] vali gnome-shell[1034]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 9.111233] vali gnome-shell[1034]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 9.111233] vali gnome-shell[1034]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 10.828569] vali gnome-shell[1034]: GNOME Shell started at Wed Mar 31 2021 11:12:42 GMT+0200 (CEST) [ 10.831237] vali gnome-shell[1034]: Registering session with GDM [ 10.854242] vali gnome-shell[1034]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed [ 15.075506] vali gnome-shell[1034]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x80001a specified for 0x800018. [ 54.159667] vali gnome-shell[1034]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 59.939310] vali gnome-shell[1034]: libinput error: event6 - DLL0665:01 06CB:76AD Touchpad: client bug: event processing lagging behind by 23ms, your system is too slow [ 70.515334] vali gnome-shell[1034]: libinput error: event6 - DLL0665:01 06CB:76AD Touchpad: client bug: event processing lagging behind by 24ms, your system is too slow [ 74.752376] vali gnome-shell[1034]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 77.896428] vali gnome-shell[1034]: surface_state_changed: assertion 'wl_window->has_last_sent_configuration' failed [ 82.383395] vali gnome-shell[1034]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 84.222465] vali gnome-shell[1034]: libinput error: event6 - DLL0665:01 06CB:76AD Touchpad: client bug: event processing lagging behind by 17ms, your system is too slow [ 84.673818] vali gnome-shell[1034]: libinput error: event6 - DLL0665:01 06CB:76AD Touchpad: client bug: event processing lagging behind by 15ms, your system is too slow [ 90.244626] vali gnome-shell[1034]: surface_state_changed: assertion 'wl_window->has_last_sent_configuration' failed [ 313.619296] vali gnome-shell[1034]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 429.193393] vali gnome-shell[1034]: Window manager warning: last_user_time (429190) is greater than comparison timestamp (429189). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... [ 429.195278] vali gnome-shell[1034]: Window manager warning: W13 appears to be one of the offending windows with a timestamp of 429190. Working around... [ 467.242912] vali gnome-shell[1034]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. [ 468.099180] vali gnome-shell[1034]: libinput error: event6 - DLL0665:01 06CB:76AD Touchpad: client bug: event processing lagging behind by 24ms, your system is too slow [ 468.099180] vali gnome-shell[1034]: libinput error: event6 - DLL0665:01 06CB:76AD Touchpad: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages. [ 638.037772] vali gnome-shell[1034]: Window manager warning: last_user_time (638036) is greater than comparison timestamp (638033). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... [ 638.037772] vali gnome-shell[1034]: Window manager warning: W13 appears to be one of the offending windows with a timestamp of 638036. Working around... [ 727.258783] vali gnome-shell[1034]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct. [ 727.347704] vali gnome-shell[1034]: 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: _checkGC@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:110:1 add@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:62:14 _cacheOrCreateIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:452:37 async*_updateIconByType@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:702:36 _updateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:731:14 _invalidateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:755:14 _init/<@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:401:18 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 _checkIfReady@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:124:18 _onPropertiesChanged/<@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:315:27 _onPropertiesChanged@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:289:15 [ 727.347992] vali gnome-shell[1034]: 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: _seekStatusNotifierItems/<@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:140:1 _seekStatusNotifierItems@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:140:21 async*AppIndicatorsStatusNotifierWatcher@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:56:14 maybeEnableAfterNameAvailable@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/extension.js:53:33 enable@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/extension.js:58:5 _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:168:32 loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:351:26 _loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:597:18 collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:28 _loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:572:19 _enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:606:18 _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:637:18 init@resource:///org/gnome/shell/ui/extensionSystem.js:57:14 _initializeUI@resource:///org/gnome/shell/ui/main.js:272:22 start@resource:///org/gnome/shell/ui/main.js:162:5 @
:1:47 [ 727.348260] vali gnome-shell[1034]: 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: _seekStatusNotifierItems/<@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:140:1 _seekStatusNotifierItems@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:140:21 async*AppIndicatorsStatusNotifierWatcher@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:56:14 maybeEnableAfterNameAvailable@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/extension.js:53:33 enable@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/extension.js:58:5 _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:168:32 loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:351:26 _loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:597:18 collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:28 _loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:572:19 _enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:606:18 _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:637:18 init@resource:///org/gnome/shell/ui/extensionSystem.js:57:14 _initializeUI@resource:///org/gnome/shell/ui/main.js:272:22 start@resource:///org/gnome/shell/ui/main.js:162:5 @
:1:47 [ 727.348448] vali gnome-shell[1034]: 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: _checkGC@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:110:1 add@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:62:14 _cacheOrCreateIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:452:37 async*_updateIconByType@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:702:36 _updateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:731:14 _invalidateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:755:14 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 reset@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:328:14 _ensureItemRegistered@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:123:18 RegisterStatusNotifierItemAsync@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:185:14 _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354:35 _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387:34 [ 727.348711] vali gnome-shell[1034]: 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: _checkGC@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:110:1 add@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:62:14 _cacheOrCreateIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:452:37 async*_updateIconByType@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:702:36 _updateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:731:14 _invalidateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:755:14 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 reset@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:328:14 _ensureItemRegistered@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:123:18 RegisterStatusNotifierItemAsync@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:185:14 _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354:35 _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387:34 [ 727.348912] vali gnome-shell[1034]: 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: _checkGC@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:110:1 add@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:62:14 _cacheOrCreateIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:452:37 async*_updateIconByType@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:702:36 _updateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:731:14 _invalidateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:755:14 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 reset@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:328:14 _ensureItemRegistered@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:123:18 RegisterStatusNotifierItemAsync@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:185:14 _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354:35 _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387:34 [ 727.349103] vali gnome-shell[1034]: 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: _checkGC@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:110:1 add@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:62:14 _cacheOrCreateIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:452:37 async*_updateIconByType@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:702:36 _updateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:731:14 _invalidateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:755:14 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 reset@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:328:14 _ensureItemRegistered@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:123:18 RegisterStatusNotifierItemAsync@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:185:14 _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354:35 _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387:34 [ 727.424158] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.424408] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x559bfdfcb8d0. [ 727.424533] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.424533] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.424533] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.424533] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.424533] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.424533] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.424533] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.424994] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.425153] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfba3cb60. [ 727.425274] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.425391] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfba3cb60. [ 727.425511] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.425640] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfba3cb60. [ 727.425741] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.425839] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559c01ab2b50. [ 727.425940] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.426039] vali gnome-shell[1034]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x559bfdfcb8d0. [ 727.426132] vali gnome-shell[1034]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. [ 727.426242] vali gnome-shell[1034]: The offending callback was set_container(), a vfunc. [ 727.427339] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.427515] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x559c01d4ad00. [ 727.428321] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.428521] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.428521] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.428521] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.428521] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.428959] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.429140] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.429140] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.429140] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.429140] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.429140] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.429140] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.429140] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.429140] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.429990] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfdf976a0. [ 727.430175] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.430175] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.430407] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.430588] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfdf976a0. [ 727.430759] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.430915] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfdf976a0. [ 727.431067] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.431213] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559c01cd2950. [ 727.431368] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.431523] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.431523] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.431748] vali gnome-shell[1034]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x559c01d4ad00. [ 727.431908] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.431908] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.431908] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.432222] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.432381] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.432381] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.432381] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.432381] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.432381] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.432922] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfdfa2aa0. [ 727.433104] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.433258] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfdfa2aa0. [ 727.433413] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.433597] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.433732] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfdfa2aa0. [ 727.433902] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.434063] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.434063] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.434063] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.434402] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559c01d55530. [ 727.434574] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.434725] vali gnome-shell[1034]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x559c01d4ad00. [ 727.434877] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.434992] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.435143] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfe182a80. [ 727.435315] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.435315] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.435315] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.435315] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.435736] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.435920] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.436041] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfe182a80. [ 727.436210] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.436367] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfe182a80. [ 727.436519] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.436668] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559bfdf746b0. [ 727.436829] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.436981] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.436981] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.436981] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.436981] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.437401] vali gnome-shell[1034]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x559c01d4ad00. [ 727.437601] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.437601] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.437826] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.437982] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfd986ca0. [ 727.438138] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.438290] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfd986ca0. [ 727.438443] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.438443] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.438443] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.438443] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.438859] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.439015] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfd986ca0. [ 727.439175] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.439175] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.439404] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.439566] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559bfc726080. [ 727.439736] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.439898] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.439898] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.439898] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.440209] vali gnome-shell[1034]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x559c01d4ad00. [ 727.440369] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.440522] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559c025dfca0. [ 727.440690] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.440690] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.440690] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.443700] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.443899] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.443899] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.443899] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.443899] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.444323] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559c025dfca0. [ 727.444486] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.444639] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559c025dfca0. [ 727.444796] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.444945] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559bfc730160. [ 727.445107] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.445271] vali gnome-shell[1034]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x559c01d4ad00. [ 727.445469] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.445653] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfcf8fa20. [ 727.445842] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.446015] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfcf8fa20. [ 727.446189] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.446356] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfcf8fa20. [ 727.446534] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.446701] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559bfcf90190. [ 727.446884] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.447061] vali gnome-shell[1034]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x559c01d4ad00. [ 727.447237] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.447412] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfc638f30. [ 727.447587] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.447765] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfc638f30. [ 727.447939] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.448112] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfc638f30. [ 727.448281] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.448435] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559bfd036360. [ 727.448591] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.448755] vali gnome-shell[1034]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x559c01d4ad00. [ 727.448912] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.449077] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfd39d7a0. [ 727.449253] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.449426] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfd39d7a0. [ 727.449620] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.449795] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfd39d7a0. [ 727.449970] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.450138] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559bfbf4f3a0. [ 727.450309] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.450482] vali gnome-shell[1034]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x559c01d4ad00. [ 727.450667] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.450840] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfdff2b60. [ 727.451010] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.451174] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfdff2b60. [ 727.451339] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.451506] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfdff2b60. [ 727.451684] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.451844] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559bfdb76480. [ 727.452021] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.452190] vali gnome-shell[1034]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x559c01d4ad00. [ 727.452365] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.452523] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfbd882d0. [ 727.452682] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.452837] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfbd882d0. [ 727.452988] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.453136] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfbd882d0. [ 727.453352] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.453868] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559bfbc1f480. [ 727.454075] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.454254] vali gnome-shell[1034]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x559c01d4ad00. [ 727.454431] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.454609] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfe444410. [ 727.454790] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.454977] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfe444410. [ 727.455156] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.455335] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x559bfe444410. [ 727.455513] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.455708] vali gnome-shell[1034]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x559c0133ab20. [ 727.455912] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.456122] vali gnome-shell[1034]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x559c01d4ad00. [ 727.456325] vali gnome-shell[1034]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. [ 727.456562] vali gnome-shell[1034]: The offending callback was set_container(), a vfunc. [ 727.465388] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.465785] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.465785] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.465785] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.465785] vali gnome-shell[1034]: == Stack trace for context 0x559bfb9831e0 == [ 727.466297] vali gnome-shell[1034]: The offending signal was notify on NMDeviceWifi 0x559bfdf5c2b0. [ 727.466525] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.466729] vali gnome-shell[1034]: The offending signal was notify on NMAccessPoint 0x559bfde3bdd0. [ 727.466954] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.467177] vali gnome-shell[1034]: The offending signal was notify on NMActiveConnection 0x559c013da6c0. [ 727.467411] vali gnome-shell[1034]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 727.467659] vali gnome-shell[1034]: The offending signal was state-changed on NMDeviceWifi 0x559bfdf5c2b0. [ 728.376959] vali gnome-shell[6866]: Boot VGA GPU /dev/dri/card0 selected as primary [ 728.920715] vali gnome-shell[6866]: Skipping parental controls support as it’s disabled [ 729.029073] vali gnome-shell[6866]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 729.029805] vali gnome-shell[6866]: Will monitor session c1 [ 729.575591] vali gnome-shell[6866]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 729.950683] vali gnome-shell[6866]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed [ 729.950915] vali gnome-shell[6866]: cr_declaration_parse_list_from_buf: assertion 'parser' failed [ 730.031049] vali gnome-shell[6866]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed [ 730.031262] vali gnome-shell[6866]: cr_declaration_parse_list_from_buf: assertion 'parser' failed [ 730.458839] vali gnome-shell[6866]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed [ 730.459056] vali gnome-shell[6866]: cr_declaration_parse_list_from_buf: assertion 'parser' failed [ 731.002397] vali gnome-shell[6866]: Registering session with GDM [ 736.519368] vali gnome-shell[7296]: Failed to use stored monitor configuration: Invalid mode 1920x1080 (59.963345) for monitor 'SHP 0x1420' [ 737.019898] vali gnome-shell[7296]: Skipping parental controls support as it’s disabled [ 737.170412] vali gnome-shell[7296]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 737.170939] vali gnome-shell[7296]: Will monitor session 5 [ 737.780446] vali gnome-shell[7296]: Telepathy is not available, chat integration will be disabled. [ 738.531142] vali gnome-shell[7296]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 738.824124] vali gnome-shell[6866]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 45 failed: Permission denied [ 739.415396] vali gnome-shell[6866]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 45 failed: Permission denied [ 741.767477] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 741.767951] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 741.767951] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 741.767951] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 741.767951] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 741.767951] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 741.767951] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 741.767951] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 741.767951] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 742.751447] vali gnome-shell[7296]: GNOME Shell started at Wed Mar 31 2021 11:24:53 GMT+0200 (CEST) [ 742.754317] vali gnome-shell[7296]: Registering session with GDM [ 742.762860] vali gnome-shell[6866]: Connection to xwayland lost [ 743.430097] vali gnome-shell[7296]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x220001a specified for 0x2200018. [ 805.439749] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 805.439749] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 805.440258] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 805.440258] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 805.440258] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 805.440258] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 805.440258] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 805.440258] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 805.440258] vali gnome-shell[7296]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 866.414324] vali gnome-shell[7296]: An active wireless connection, in infrastructure mode, involves no access point? [ 1011.508173] vali gnome-shell[7296]: DING: GNOME nautilus 3.38.2 [ 1315.970733] vali gnome-shell[7296]: Failed to allocate DMA buffer, disabling DMA buffer based screen casting: CoglRenderer doesn't support creating DMA buffers [ 1342.253238] vali gnome-shell[7296]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct. [ 1342.323335] vali gnome-shell[7296]: 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: _checkGC@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:110:1 add@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/iconCache.js:62:14 _cacheOrCreateIconByName@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:452:37 async*_updateIconByType@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:702:36 _updateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:731:14 _invalidateIcon@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:755:14 _init@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:407:18 _init@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/indicatorStatusIcon.js:44:25 _registerItem@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:102:32 async*_ensureItemRegistered@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:127:14 RegisterStatusNotifierItemAsync@/usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:185:14 _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:354:35 _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:387:34 [ 1342.389906] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.390125] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x564972402990. [ 1342.390232] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.390232] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.390232] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.390232] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.390232] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.390232] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.390232] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.390636] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.390738] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564971cf84a0. [ 1342.390834] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.390923] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564971cf84a0. [ 1342.391017] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391017] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391017] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391017] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391017] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391273] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.391362] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391362] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391362] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391362] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391362] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391362] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391674] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564971cf84a0. [ 1342.391768] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391768] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391768] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391768] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391768] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391768] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391768] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391768] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.391768] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392230] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.392330] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392330] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392330] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392330] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392330] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392330] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392330] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392330] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392330] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392330] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392838] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x56496f9f2880. [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.392939] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.393747] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.393862] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.393862] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.393862] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.393862] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.393862] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.393862] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.393862] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.393862] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.393862] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.393862] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.393862] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.393862] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.394490] vali gnome-shell[7296]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564972402990. [ 1342.394610] vali gnome-shell[7296]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. [ 1342.394716] vali gnome-shell[7296]: The offending callback was set_container(), a vfunc. [ 1342.394810] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.394901] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x564970f71af0. [ 1342.394991] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.395081] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564975dbbc10. [ 1342.395183] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.395292] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564975dbbc10. [ 1342.395393] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.395515] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564975dbbc10. [ 1342.395619] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.395708] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564975df32e0. [ 1342.395801] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.395893] vali gnome-shell[7296]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564970f71af0. [ 1342.395989] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.396073] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5649712e4920. [ 1342.396164] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.396251] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5649712e4920. [ 1342.396347] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.396435] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5649712e4920. [ 1342.396524] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.396611] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5649706529f0. [ 1342.396704] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.396791] vali gnome-shell[7296]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564970f71af0. [ 1342.396881] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.396967] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56497016f8d0. [ 1342.397057] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.397151] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56497016f8d0. [ 1342.397243] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.397344] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56497016f8d0. [ 1342.398497] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.398754] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564972224f40. [ 1342.398949] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.399164] vali gnome-shell[7296]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564970f71af0. [ 1342.399370] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.399559] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564971e02e70. [ 1342.399766] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.399970] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564971e02e70. [ 1342.400147] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.400320] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564971e02e70. [ 1342.400496] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.400658] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x56496f5fb610. [ 1342.400847] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.401025] vali gnome-shell[7296]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564970f71af0. [ 1342.401200] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.401371] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564975d95f30. [ 1342.401567] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.401737] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564975d95f30. [ 1342.401901] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.402072] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564975d95f30. [ 1342.402241] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.402412] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564970fa5130. [ 1342.402587] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.402773] vali gnome-shell[7296]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564970f71af0. [ 1342.402944] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.403112] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564976093000. [ 1342.403282] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.403451] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564976093000. [ 1342.403619] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.403797] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564976093000. [ 1342.403966] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.404136] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564976093c60. [ 1342.404305] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.404472] vali gnome-shell[7296]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564970f71af0. [ 1342.404632] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.404803] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56496f67e000. [ 1342.404983] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.405156] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56496f67e000. [ 1342.405321] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.409600] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56496f67e000. [ 1342.409849] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.410046] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564970fd79e0. [ 1342.410243] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.410422] vali gnome-shell[7296]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564970f71af0. [ 1342.410596] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.410596] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.410596] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.410596] vali gnome-shell[7296]: == Stack trace for context 0x56496f3b0120 == [ 1342.411034] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.411233] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5649719320a0. [ 1342.411424] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.411616] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5649719320a0. [ 1342.411798] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.411970] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5649719320a0. [ 1342.412143] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.412319] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x56496fafde80. [ 1342.412502] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.412676] vali gnome-shell[7296]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564970f71af0. [ 1342.412842] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.413029] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564971eb5fa0. [ 1342.413216] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.413408] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564971eb5fa0. [ 1342.413592] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.413790] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564971eb5fa0. [ 1342.413987] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.414184] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564976024be0. [ 1342.414365] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.414541] vali gnome-shell[7296]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564970f71af0. [ 1342.414713] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.414897] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56497109af10. [ 1342.415070] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.415239] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56497109af10. [ 1342.415409] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.415590] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x56497109af10. [ 1342.415763] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.415951] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5649756f8f10. [ 1342.416214] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.416421] vali gnome-shell[7296]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564970f71af0. [ 1342.416622] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.416799] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564971b11300. [ 1342.416990] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.417187] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564971b11300. [ 1342.417376] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.419338] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x564971b11300. [ 1342.419561] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.419743] vali gnome-shell[7296]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x564971ac2650. [ 1342.419923] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.420102] vali gnome-shell[7296]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x564970f71af0. [ 1342.420287] vali gnome-shell[7296]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. [ 1342.420475] vali gnome-shell[7296]: The offending callback was set_container(), a vfunc. [ 1342.420646] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.420836] vali gnome-shell[7296]: The offending signal was notify on NMDeviceWifi 0x564971f5a290. [ 1342.421010] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.421188] vali gnome-shell[7296]: The offending signal was notify on NMActiveConnection 0x564971f63340. [ 1342.421361] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.421578] vali gnome-shell[7296]: The offending signal was notify on NMAccessPoint 0x7f8484007a50. [ 1342.421758] vali gnome-shell[7296]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 1342.421933] vali gnome-shell[7296]: The offending signal was state-changed on NMDeviceWifi 0x564971f5a290. [ 1343.571203] vali gnome-shell[9792]: Boot VGA GPU /dev/dri/card0 selected as primary [ 1344.092388] vali gnome-shell[9792]: Skipping parental controls support as it’s disabled [ 1344.193047] vali gnome-shell[9792]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 1344.193730] vali gnome-shell[9792]: Will monitor session c2 [ 1344.767871] vali gnome-shell[9792]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 1345.055991] vali gnome-shell[9792]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed [ 1345.056223] vali gnome-shell[9792]: cr_declaration_parse_list_from_buf: assertion 'parser' failed [ 1345.125078] vali gnome-shell[9792]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed [ 1345.125296] vali gnome-shell[9792]: cr_declaration_parse_list_from_buf: assertion 'parser' failed [ 1345.652246] vali gnome-shell[9792]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed [ 1345.652444] vali gnome-shell[9792]: cr_declaration_parse_list_from_buf: assertion 'parser' failed [ 1346.168352] vali gnome-shell[9792]: Registering session with GDM [ 1358.800438] vali gnome-shell[10244]: Boot VGA GPU /dev/dri/card0 selected as primary [ 1359.356248] vali gnome-shell[10244]: Skipping parental controls support as it’s disabled [ 1359.512720] vali gnome-shell[10244]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 1359.513509] vali gnome-shell[10244]: Will monitor session 8 [ 1359.963882] vali gnome-shell[10244]: Telepathy is not available, chat integration will be disabled. [ 1360.793139] vali gnome-shell[10244]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 1361.532586] vali gnome-shell[10244]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 1361.533076] vali gnome-shell[10244]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 1361.533076] vali gnome-shell[10244]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 1361.533076] vali gnome-shell[10244]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 1361.533076] vali gnome-shell[10244]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 1361.533365] vali gnome-shell[10244]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 1361.533365] vali gnome-shell[10244]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 1361.533515] vali gnome-shell[10244]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 1361.533582] vali gnome-shell[10244]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 1361.818954] vali gnome-shell[9792]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 45 failed: Permission denied [ 1362.052222] vali gnome-shell[9792]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 45 failed: Permission denied [ 1363.603376] vali gnome-shell[10244]: GNOME Shell started at Wed Mar 31 2021 11:35:15 GMT+0200 (CEST) [ 1363.605403] vali gnome-shell[10244]: Registering session with GDM [ 1363.611738] vali gnome-shell[9792]: Connection to xwayland lost [ 1365.305788] vali gnome-shell[10244]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x80001a specified for 0x800018. [ 1365.407170] vali gnome-shell[10244]: libinput error: event6 - DLL0665:01 06CB:76AD Touchpad: client bug: event processing lagging behind by 16ms, your system is too slow [ 1370.173326] vali gnome-shell[10244]: libinput error: event6 - DLL0665:01 06CB:76AD Touchpad: client bug: event processing lagging behind by 12ms, your system is too slow [ 1375.569749] vali gnome-shell[10244]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 1391.769714] vali gnome-shell[10244]: DING: GNOME nautilus 3.38.2 [ 1474.607216] vali gnome-shell[10244]: libinput error: event6 - DLL0665:01 06CB:76AD Touchpad: client bug: event processing lagging behind by 14ms, your system is too slow [ 1475.408376] vali gnome-shell[10244]: libinput error: event6 - DLL0665:01 06CB:76AD Touchpad: client bug: event processing lagging behind by 14ms, your system is too slow [ 1475.609595] vali gnome-shell[10244]: libinput error: event6 - DLL0665:01 06CB:76AD Touchpad: client bug: event processing lagging behind by 12ms, your system is too slow [ 1475.609595] vali gnome-shell[10244]: libinput error: event6 - DLL0665:01 06CB:76AD Touchpad: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages. [ 1833.114447] vali gnome-shell[10244]: Window manager warning: last_user_time (1833113) is greater than comparison timestamp (1833110). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around... [ 1833.114447] vali gnome-shell[10244]: Window manager warning: W3 appears to be one of the offending windows with a timestamp of 1833113. Working around...