[ 9.090640] corrado-n2-jammy gnome-shell[970]: Running GNOME Shell (using mutter 42.1) as a Wayland display server [ 9.205928] corrado-n2-jammy gnome-shell[970]: Device '/dev/dri/card0' prefers shadow buffer [ 9.212382] corrado-n2-jammy gnome-shell[970]: Added device '/dev/dri/card0' (i915) using atomic mode setting. [ 9.390592] corrado-n2-jammy gnome-shell[970]: Created gbm renderer for '/dev/dri/card0' [ 9.390942] corrado-n2-jammy gnome-shell[970]: Boot VGA GPU /dev/dri/card0 selected as primary [ 10.206197] corrado-n2-jammy gnome-shell[970]: Using public X11 display :1024, (using :1025 for managed services) [ 10.206722] corrado-n2-jammy gnome-shell[970]: Using Wayland display name 'wayland-0' [ 10.991978] corrado-n2-jammy gnome-shell[970]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 10.992594] corrado-n2-jammy gnome-shell[970]: Will monitor session c1 [ 11.440932] corrado-n2-jammy gnome-shell[970]: Extension ding@rastersoft.com already installed in /usr/share/gnome-shell/extensions/ding@rastersoft.com. /usr/share/gnome-shell/extensions/ding@rastersoft.com will not be loaded [ 11.441513] corrado-n2-jammy gnome-shell[970]: Extension ubuntu-appindicators@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com will not be loaded [ 11.441957] corrado-n2-jammy gnome-shell[970]: Extension ubuntu-dock@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com will not be loaded [ 11.473758] corrado-n2-jammy org.gnome.Shell.desktop[970]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10369984469ffc98a3165479775754547200000009520000.ms”: No such file or directory [ 11.653740] corrado-n2-jammy gnome-shell[970]: JS ERROR: TypeError: this._managerProxy is undefined _onGeoclueVanished@resource:///org/gnome/shell/ui/status/location.js:169:9 [ 11.699961] corrado-n2-jammy gnome-shell[970]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 12.381026] corrado-n2-jammy gnome-shell[970]: ATK Bridge is disabled but a11y has already been enabled. [ 12.612745] corrado-n2-jammy gnome-shell[970]: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 [ 12.677331] corrado-n2-jammy gnome-shell[970]: Registering session with GDM [ 24.322790] corrado-n2-jammy gnome-shell[1788]: Running GNOME Shell (using mutter 42.1) as a Wayland display server [ 24.374262] corrado-n2-jammy gnome-shell[1788]: Device '/dev/dri/card0' prefers shadow buffer [ 24.378670] corrado-n2-jammy gnome-shell[1788]: Added device '/dev/dri/card0' (i915) using atomic mode setting. [ 24.481335] corrado-n2-jammy gnome-shell[1788]: Created gbm renderer for '/dev/dri/card0' [ 24.481682] corrado-n2-jammy gnome-shell[1788]: Boot VGA GPU /dev/dri/card0 selected as primary [ 25.139043] corrado-n2-jammy gnome-shell[1788]: Using public X11 display :0, (using :1 for managed services) [ 25.139383] corrado-n2-jammy gnome-shell[1788]: Using Wayland display name 'wayland-0' [ 25.821124] corrado-n2-jammy gnome-shell[1788]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 25.821679] corrado-n2-jammy gnome-shell[1788]: Will monitor session 2 [ 26.299575] corrado-n2-jammy gnome-shell[1788]: Telepathy is not available, chat integration will be disabled. [ 27.262165] corrado-n2-jammy gnome-shell[1788]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 27.586836] corrado-n2-jammy gnome-shell[1788]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 27.587528] corrado-n2-jammy gnome-shell[1788]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 27.587975] corrado-n2-jammy gnome-shell[1788]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 27.588669] corrado-n2-jammy gnome-shell[1788]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 27.589150] corrado-n2-jammy gnome-shell[1788]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 27.589682] corrado-n2-jammy gnome-shell[1788]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 27.590240] corrado-n2-jammy gnome-shell[1788]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 27.592064] corrado-n2-jammy gnome-shell[1788]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 27.592817] corrado-n2-jammy gnome-shell[1788]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 29.681637] corrado-n2-jammy gnome-shell[1788]: GNOME Shell started at Thu Jun 09 2022 20:02:55 GMT+0200 (CEST) [ 29.683997] corrado-n2-jammy gnome-shell[1788]: Registering session with GDM [ 30.895122] corrado-n2-jammy gnome-shell[1788]: DING: Detected async api for thumbnails [ 31.027215] corrado-n2-jammy gnome-shell[1788]: DING: GNOME nautilus 42.1.1 [ 90.073516] corrado-n2-jammy ubuntu-appindicators@ubuntu.com[1788]: unable to update icon for software-update-available [ 90.111198] corrado-n2-jammy ubuntu-appindicators@ubuntu.com[1788]: unable to update icon for livepatch [ 153.964326] corrado-n2-jammy gnome-shell[1788]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 1157.532667] corrado-n2-jammy gnome-shell[1788]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 1555.740738] corrado-n2-jammy gnome-shell[1788]: ATK Bridge is disabled but a11y has already been enabled. [ 1793.736814] corrado-n2-jammy gnome-shell[1788]: Could not create transient scope for PID 0: GDBus.Error:org.freedesktop.systemd1.UnitExists: Unit app-gnome-org.gnome.Nautilus-0.scope already exists. [ 1823.301400] corrado-n2-jammy gnome-shell[1788]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 1823.920590] corrado-n2-jammy gnome-shell[1788]: An active wireless connection, in infrastructure mode, involves no access point? [ 1834.046655] corrado-n2-jammy gnome-shell[1788]: Could not create transient scope for PID 0: GDBus.Error:org.freedesktop.systemd1.UnitExists: Unit app-gnome-org.gnome.Nautilus-0.scope already exists. [ 1843.113491] corrado-n2-jammy gnome-shell[1788]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 1876.447052] corrado-n2-jammy gnome-shell[1788]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 1889.290956] corrado-n2-jammy gnome-shell[1788]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 1943.832709] corrado-n2-jammy gnome-shell[1788]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 2167.955838] corrado-n2-jammy gnome-shell[1788]: Could not create transient scope for PID 0: GDBus.Error:org.freedesktop.systemd1.UnitExists: Unit app-gnome-org.gnome.Nautilus-0.scope already exists. [ 2178.749098] corrado-n2-jammy gnome-shell[1788]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 2298.140940] corrado-n2-jammy gnome-shell[1788]: Could not create transient scope for PID 0: GDBus.Error:org.freedesktop.systemd1.UnitExists: Unit app-gnome-org.gnome.Nautilus-0.scope already exists. [ 2323.451270] corrado-n2-jammy gnome-shell[1788]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 2532.562831] corrado-n2-jammy gnome-shell[1788]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 2720.069565] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.070399] corrado-n2-jammy gnome-shell[1788]: The offending signal was notify on NMDeviceEthernet 0x55ce91ca0340. [ 2720.070609] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.070609] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.070609] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.070609] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.070609] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.070609] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.071057] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.071177] corrado-n2-jammy gnome-shell[1788]: The offending signal was notify on NMDeviceWifi 0x55ce91ca42a0. [ 2720.071284] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.071385] corrado-n2-jammy gnome-shell[1788]: The offending signal was notify on NMActiveConnection 0x55ce91ca9180. [ 2720.071489] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.071596] corrado-n2-jammy gnome-shell[1788]: The offending signal was notify on NMAccessPoint 0x55ce900f34b0. [ 2720.071708] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.071810] corrado-n2-jammy gnome-shell[1788]: The offending signal was state-changed on NMDeviceEthernet 0x55ce91ca0340. [ 2720.071922] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.072027] corrado-n2-jammy gnome-shell[1788]: The offending signal was state-changed on NMDeviceWifi 0x55ce91ca42a0. [ 2720.076725] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.077111] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.077283] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.077283] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.077283] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.077283] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.077283] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.077283] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.077283] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.077283] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.077283] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.077283] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.077283] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.077283] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.077283] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078450] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.078619] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079871] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.079991] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081422] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.081539] corrado-n2-jammy gnome-shell[1788]: == Stack trace for context 0x55ce8fec0490 == [ 2720.082533] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.082659] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.082772] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94ccb930. [ 2720.082888] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.082998] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94ccb930. [ 2720.083107] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.083214] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94ccb930. [ 2720.083313] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.083417] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94ccb930. [ 2720.083516] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.083636] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ce94dab6c0. [ 2720.083745] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.083847] corrado-n2-jammy gnome-shell[1788]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.083954] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.084054] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce911dfe90. [ 2720.084161] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.084272] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce911dfe90. [ 2720.084378] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.084482] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce911dfe90. [ 2720.084584] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.084688] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce911dfe90. [ 2720.084790] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.084896] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ce91e31c30. [ 2720.085011] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.085116] corrado-n2-jammy gnome-shell[1788]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.085231] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.085339] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94cc5be0. [ 2720.085450] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.085558] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94cc5be0. [ 2720.085670] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.085911] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94cc5be0. [ 2720.086047] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.086180] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94cc5be0. [ 2720.086296] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.086406] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ce91cc0600. [ 2720.086524] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.086647] corrado-n2-jammy gnome-shell[1788]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.086941] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.087298] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94d275f0. [ 2720.087526] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.087718] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94d275f0. [ 2720.088084] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.088412] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94d275f0. [ 2720.088736] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.088954] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94d275f0. [ 2720.089288] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.089638] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ce91cb9dd0. [ 2720.089970] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.090285] corrado-n2-jammy gnome-shell[1788]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.090654] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.090958] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce904e7880. [ 2720.091180] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.091375] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce904e7880. [ 2720.091671] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.091879] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce904e7880. [ 2720.092051] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.092256] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce904e7880. [ 2720.092463] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.092662] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ce90f6c2f0. [ 2720.092930] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.093079] corrado-n2-jammy gnome-shell[1788]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.093188] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.093292] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce90f42430. [ 2720.093461] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.093980] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce90f42430. [ 2720.094319] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.094532] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce90f42430. [ 2720.094728] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.094936] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce90f42430. [ 2720.095123] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.095321] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ce90f629a0. [ 2720.095492] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.095658] corrado-n2-jammy gnome-shell[1788]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.095836] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.096060] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce90f46570. [ 2720.096279] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.096462] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce90f46570. [ 2720.096661] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.096856] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce90f46570. [ 2720.097070] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.097255] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce90f46570. [ 2720.097414] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.097565] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ce90f5dd80. [ 2720.097752] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.097972] corrado-n2-jammy gnome-shell[1788]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.098170] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.098328] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce90f4a1d0. [ 2720.098487] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.098635] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce90f4a1d0. [ 2720.098771] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.098912] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce90f4a1d0. [ 2720.099043] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.099187] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce90f4a1d0. [ 2720.099328] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.099475] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ce90f52ab0. [ 2720.099613] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.099753] corrado-n2-jammy gnome-shell[1788]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.099894] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.100025] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94cacb80. [ 2720.100165] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.100314] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94cacb80. [ 2720.100463] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.100591] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94cacb80. [ 2720.100731] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.100877] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94cacb80. [ 2720.101020] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.101162] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ce94d98a80. [ 2720.101314] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.101457] corrado-n2-jammy gnome-shell[1788]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.101597] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.101759] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94d123f0. [ 2720.101916] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.102056] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94d123f0. [ 2720.102194] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.102338] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94d123f0. [ 2720.102482] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.102629] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94d123f0. [ 2720.102762] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.102890] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ce94d05180. [ 2720.103026] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.103174] corrado-n2-jammy gnome-shell[1788]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.103317] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.103448] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94cd6aa0. [ 2720.103581] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.103727] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94cd6aa0. [ 2720.103872] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.104012] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94cd6aa0. [ 2720.104159] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.104301] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55ce94cd6aa0. [ 2720.104442] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.104586] corrado-n2-jammy gnome-shell[1788]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55ce94cdcd80. [ 2720.104715] corrado-n2-jammy gnome-shell[1788]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2720.104859] corrado-n2-jammy gnome-shell[1788]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55ce91cda5d0. [ 2720.105004] corrado-n2-jammy gnome-shell[1788]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. [ 2720.105139] corrado-n2-jammy gnome-shell[1788]: The offending callback was set_container(), a vfunc. [ 2721.285557] corrado-n2-jammy gnome-shell[13075]: Running GNOME Shell (using mutter 42.1) as a Wayland display server [ 2721.338533] corrado-n2-jammy gnome-shell[13075]: Device '/dev/dri/card0' prefers shadow buffer [ 2721.343251] corrado-n2-jammy gnome-shell[13075]: Added device '/dev/dri/card0' (i915) using atomic mode setting. [ 2721.441411] corrado-n2-jammy gnome-shell[13075]: Created gbm renderer for '/dev/dri/card0' [ 2721.441755] corrado-n2-jammy gnome-shell[13075]: Boot VGA GPU /dev/dri/card0 selected as primary [ 2722.052439] corrado-n2-jammy gnome-shell[13075]: Using public X11 display :1024, (using :1025 for managed services) [ 2722.052789] corrado-n2-jammy gnome-shell[13075]: Using Wayland display name 'wayland-0' [ 2722.750064] corrado-n2-jammy gnome-shell[13075]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 2722.750840] corrado-n2-jammy gnome-shell[13075]: Will monitor session c2 [ 2723.196662] corrado-n2-jammy gnome-shell[13075]: Extension ding@rastersoft.com already installed in /usr/share/gnome-shell/extensions/ding@rastersoft.com. /usr/share/gnome-shell/extensions/ding@rastersoft.com will not be loaded [ 2723.196973] corrado-n2-jammy gnome-shell[13075]: Extension ubuntu-appindicators@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com will not be loaded [ 2723.197272] corrado-n2-jammy gnome-shell[13075]: Extension ubuntu-dock@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com will not be loaded [ 2723.224569] corrado-n2-jammy org.gnome.Shell.desktop[13075]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10c3f826afc30237eb165480046977406100000130100000.ms”: No such file or directory [ 2723.487394] corrado-n2-jammy gnome-shell[13075]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 2723.920181] corrado-n2-jammy gnome-shell[13075]: ATK Bridge is disabled but a11y has already been enabled. [ 2724.152750] corrado-n2-jammy gnome-shell[13075]: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 [ 2724.277992] corrado-n2-jammy gnome-shell[13075]: Registering session with GDM [ 2743.923956] corrado-n2-jammy gnome-shell[14276]: Running GNOME Shell (using mutter 42.1) as a X11 window and compositing manager [ 2744.498052] corrado-n2-jammy gnome-shell[14276]: ATK Bridge is disabled but a11y has already been enabled. [ 2745.450397] corrado-n2-jammy gnome-shell[14276]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 2745.451213] corrado-n2-jammy gnome-shell[14276]: Will monitor session 7 [ 2745.955896] corrado-n2-jammy gnome-shell[14276]: Telepathy is not available, chat integration will be disabled. [ 2747.265843] corrado-n2-jammy gnome-shell[14276]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 2749.267948] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 2749.268592] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 2749.268592] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 2749.268592] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 2749.268592] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 2749.268592] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 2749.268592] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 2749.268592] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 2749.269395] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 2751.241093] corrado-n2-jammy gnome-shell[14276]: GNOME Shell started at Thu Jun 09 2022 20:48:14 GMT+0200 (CEST) [ 2751.242918] corrado-n2-jammy gnome-shell[14276]: Registering session with GDM [ 2751.247265] corrado-n2-jammy gnome-shell[13075]: Connection to xwayland lost [ 2752.155849] corrado-n2-jammy gnome-shell[14276]: DING: Detected async api for thumbnails [ 2752.285763] corrado-n2-jammy gnome-shell[14276]: DING: GNOME nautilus 42.1.1 [ 2769.655271] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 2769.655271] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 2769.655271] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 2769.656507] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 2769.656507] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 2769.656507] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 2769.656507] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 2769.656507] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 2769.656507] corrado-n2-jammy gnome-shell[14276]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 2808.283044] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.283687] corrado-n2-jammy gnome-shell[14276]: The offending signal was notify on NMDeviceEthernet 0x561a723c05d0. [ 2808.283901] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.283901] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.283901] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.283901] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.283901] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.284409] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.284555] corrado-n2-jammy gnome-shell[14276]: The offending signal was notify on NMDeviceWifi 0x561a74120340. [ 2808.284710] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.284710] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.284710] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.284710] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.284710] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.284710] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.284710] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.284710] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.285255] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.285389] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.285389] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.285389] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.285389] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.285389] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.285389] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.285389] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.285910] corrado-n2-jammy gnome-shell[14276]: The offending signal was notify on NMActiveConnection 0x561a74124180. [ 2808.286061] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286061] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286061] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286061] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286061] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286061] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286061] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286061] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286061] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286061] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286061] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286778] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.286915] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286915] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286915] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286915] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286915] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286915] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286915] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286915] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286915] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286915] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286915] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.286915] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.287712] corrado-n2-jammy gnome-shell[14276]: The offending signal was state-changed on NMDeviceEthernet 0x561a723c05d0. [ 2808.287849] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.287849] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.287849] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.287849] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.287849] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.287849] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.287849] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.287849] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.287849] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.287849] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.287849] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.287849] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.288636] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.288768] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.288768] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.288768] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.288768] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.288768] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.288768] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.288768] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.288768] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.288768] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.288768] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.288768] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.288768] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.288768] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.289605] corrado-n2-jammy gnome-shell[14276]: The offending signal was state-changed on NMDeviceWifi 0x561a74120340. [ 2808.289769] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.289769] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.289769] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.289769] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.289769] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.289769] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.289769] corrado-n2-jammy gnome-shell[14276]: == Stack trace for context 0x561a71eb4170 == [ 2808.290342] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.290499] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.290651] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.290792] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.290934] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.291125] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.291262] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.291370] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7728a2f0. [ 2808.291476] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.291585] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7728a2f0. [ 2808.291684] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.291837] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7728a2f0. [ 2808.291984] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.292111] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7728a2f0. [ 2808.292282] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.292483] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x561a733dbd30. [ 2808.292678] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.292844] corrado-n2-jammy gnome-shell[14276]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.292996] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.293109] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a773105e0. [ 2808.293225] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.293334] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a773105e0. [ 2808.293451] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.293560] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a773105e0. [ 2808.293654] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.293814] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a773105e0. [ 2808.293987] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.294126] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x561a733cb430. [ 2808.294262] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.294558] corrado-n2-jammy gnome-shell[14276]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.294717] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.294856] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a733b69b0. [ 2808.294999] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.295128] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a733b69b0. [ 2808.295264] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.295399] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a733b69b0. [ 2808.295540] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.295671] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a733b69b0. [ 2808.295797] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.295929] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x561a733c3190. [ 2808.296115] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.296258] corrado-n2-jammy gnome-shell[14276]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.296394] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.296529] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a733bb390. [ 2808.296669] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.296808] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a733bb390. [ 2808.296945] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.297081] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a733bb390. [ 2808.297212] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.297346] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a733bb390. [ 2808.297489] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.297625] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x561a733bbab0. [ 2808.297787] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.297931] corrado-n2-jammy gnome-shell[14276]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.298072] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.298213] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7730f900. [ 2808.298351] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.298484] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7730f900. [ 2808.298616] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.298761] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7730f900. [ 2808.298895] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.299028] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7730f900. [ 2808.299162] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.299293] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x561a772f3ea0. [ 2808.299427] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.299560] corrado-n2-jammy gnome-shell[14276]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.299701] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.299836] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a772b23b0. [ 2808.299972] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.300107] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a772b23b0. [ 2808.300240] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.300373] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a772b23b0. [ 2808.300508] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.300641] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a772b23b0. [ 2808.300773] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.300909] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x561a7724ae10. [ 2808.301045] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.301175] corrado-n2-jammy gnome-shell[14276]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.301307] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.301445] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a73a5cc60. [ 2808.301589] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.301796] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a73a5cc60. [ 2808.301935] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.302072] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a73a5cc60. [ 2808.302200] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.302342] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a73a5cc60. [ 2808.302474] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.302616] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x561a733da060. [ 2808.302749] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.302883] corrado-n2-jammy gnome-shell[14276]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.303013] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.303150] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a73da9070. [ 2808.303370] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.303520] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a73da9070. [ 2808.303655] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.303788] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a73da9070. [ 2808.303919] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.304047] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a73da9070. [ 2808.304175] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.304313] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x561a727a1770. [ 2808.304444] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.304588] corrado-n2-jammy gnome-shell[14276]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.304719] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.304850] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7733b9b0. [ 2808.304986] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.305128] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7733b9b0. [ 2808.305273] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.305411] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7733b9b0. [ 2808.305544] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.305680] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7733b9b0. [ 2808.305861] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.306003] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x561a7726cf20. [ 2808.306145] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.306279] corrado-n2-jammy gnome-shell[14276]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.306423] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.306566] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a77315140. [ 2808.306705] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.306840] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a77315140. [ 2808.306978] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.307107] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a77315140. [ 2808.307239] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.307371] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a77315140. [ 2808.307507] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.307640] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x561a772d9aa0. [ 2808.307773] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.307914] corrado-n2-jammy gnome-shell[14276]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.308047] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.308180] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7723a980. [ 2808.308316] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.308450] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7723a980. [ 2808.308581] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.308720] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7723a980. [ 2808.308846] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.308980] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x561a7723a980. [ 2808.309112] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.309242] corrado-n2-jammy gnome-shell[14276]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x561a7724c160. [ 2808.309384] corrado-n2-jammy gnome-shell[14276]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 2808.309522] corrado-n2-jammy gnome-shell[14276]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x561a74327e30. [ 2808.309661] corrado-n2-jammy gnome-shell[14276]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. [ 2808.309846] corrado-n2-jammy gnome-shell[14276]: The offending callback was set_container(), a vfunc. [ 2809.813418] corrado-n2-jammy gnome-shell[18805]: Running GNOME Shell (using mutter 42.1) as a Wayland display server [ 2809.869983] corrado-n2-jammy gnome-shell[18805]: Device '/dev/dri/card0' prefers shadow buffer [ 2809.874654] corrado-n2-jammy gnome-shell[18805]: Added device '/dev/dri/card0' (i915) using atomic mode setting. [ 2809.969988] corrado-n2-jammy gnome-shell[18805]: Created gbm renderer for '/dev/dri/card0' [ 2809.970364] corrado-n2-jammy gnome-shell[18805]: Boot VGA GPU /dev/dri/card0 selected as primary [ 2810.608674] corrado-n2-jammy gnome-shell[18805]: Using public X11 display :1024, (using :1025 for managed services) [ 2810.609044] corrado-n2-jammy gnome-shell[18805]: Using Wayland display name 'wayland-0' [ 2811.302686] corrado-n2-jammy gnome-shell[18805]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 2811.303164] corrado-n2-jammy gnome-shell[18805]: Will monitor session c3 [ 2811.739894] corrado-n2-jammy gnome-shell[18805]: Extension ding@rastersoft.com already installed in /usr/share/gnome-shell/extensions/ding@rastersoft.com. /usr/share/gnome-shell/extensions/ding@rastersoft.com will not be loaded [ 2811.740222] corrado-n2-jammy gnome-shell[18805]: Extension ubuntu-appindicators@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com will not be loaded [ 2811.740520] corrado-n2-jammy gnome-shell[18805]: Extension ubuntu-dock@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com will not be loaded [ 2811.772302] corrado-n2-jammy org.gnome.Shell.desktop[18805]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm3/.config/mutter/sessions/10dee9fbc18ce372e1165480055830168400000187690000.ms”: No such file or directory [ 2811.996815] corrado-n2-jammy gnome-shell[18805]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 2812.539435] corrado-n2-jammy gnome-shell[18805]: ATK Bridge is disabled but a11y has already been enabled. [ 2812.806964] corrado-n2-jammy gnome-shell[18805]: JS ERROR: Failed to initialize fprintd service: Gio.IOErrorEnum: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 [ 2812.915324] corrado-n2-jammy gnome-shell[18805]: Registering session with GDM [ 2829.605612] corrado-n2-jammy gnome-shell[19511]: Running GNOME Shell (using mutter 42.1) as a Wayland display server [ 2829.655652] corrado-n2-jammy gnome-shell[19511]: Device '/dev/dri/card0' prefers shadow buffer [ 2829.660759] corrado-n2-jammy gnome-shell[19511]: Added device '/dev/dri/card0' (i915) using atomic mode setting. [ 2829.754038] corrado-n2-jammy gnome-shell[19511]: Created gbm renderer for '/dev/dri/card0' [ 2829.754383] corrado-n2-jammy gnome-shell[19511]: Boot VGA GPU /dev/dri/card0 selected as primary [ 2830.332573] corrado-n2-jammy gnome-shell[19511]: Using public X11 display :0, (using :1 for managed services) [ 2830.332956] corrado-n2-jammy gnome-shell[19511]: Using Wayland display name 'wayland-0' [ 2831.047738] corrado-n2-jammy gnome-shell[19511]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 2831.048260] corrado-n2-jammy gnome-shell[19511]: Will monitor session 10 [ 2831.488687] corrado-n2-jammy gnome-shell[19511]: Telepathy is not available, chat integration will be disabled. [ 2832.390995] corrado-n2-jammy gnome-shell[19511]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 2832.596975] corrado-n2-jammy gnome-shell[19511]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 2832.597404] corrado-n2-jammy gnome-shell[19511]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 2832.602902] corrado-n2-jammy gnome-shell[19511]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 2832.603444] corrado-n2-jammy gnome-shell[19511]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 2832.603977] corrado-n2-jammy gnome-shell[19511]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 2832.604288] corrado-n2-jammy gnome-shell[19511]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 2832.604630] corrado-n2-jammy gnome-shell[19511]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 2832.605019] corrado-n2-jammy gnome-shell[19511]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 2832.605223] corrado-n2-jammy gnome-shell[19511]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 2834.339754] corrado-n2-jammy gnome-shell[19511]: GNOME Shell started at Thu Jun 09 2022 20:49:40 GMT+0200 (CEST) [ 2834.342598] corrado-n2-jammy gnome-shell[19511]: Registering session with GDM [ 2835.482870] corrado-n2-jammy gnome-shell[19511]: DING: Detected async api for thumbnails [ 2835.626674] corrado-n2-jammy gnome-shell[19511]: DING: GNOME nautilus 42.1.1 [ 2848.662283] corrado-n2-jammy gnome-shell[19511]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 2858.061320] corrado-n2-jammy gnome-shell[19511]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 2896.723059] corrado-n2-jammy ubuntu-appindicators@ubuntu.com[19511]: unable to update icon for software-update-available [ 2896.762768] corrado-n2-jammy ubuntu-appindicators@ubuntu.com[19511]: unable to update icon for livepatch [ 3073.913486] corrado-n2-jammy gnome-shell[19511]: g_object_get: assertion 'G_IS_OBJECT (object)' failed [ 3098.090906] corrado-n2-jammy gnome-shell[19511]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 3167.136669] corrado-n2-jammy gnome-shell[19511]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 3179.845529] corrado-n2-jammy gnome-shell[19511]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed [ 3193.783706] corrado-n2-jammy gnome-shell[19511]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed