Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal' can see all messages.
      Pass -q to turn off this notice.
[   19.363211] darkstar-xps gnome-shell[7066]: Running GNOME Shell (using mutter 42.0) as a Wayland display server
[   19.385593] darkstar-xps gnome-shell[7066]: Device '/dev/dri/card0' prefers shadow buffer
[   19.388545] darkstar-xps gnome-shell[7066]: Added device '/dev/dri/card0' (i915) using atomic mode setting.
[   19.444663] darkstar-xps gnome-shell[7066]: Created gbm renderer for '/dev/dri/card0'
[   19.444829] darkstar-xps gnome-shell[7066]: Boot VGA GPU /dev/dri/card0 selected as primary
[   19.741730] darkstar-xps gnome-shell[7066]: Using public X11 display :0, (using :1 for managed services)
[   19.741918] darkstar-xps gnome-shell[7066]: Using Wayland display name 'wayland-0'
[   20.079661] darkstar-xps gnome-shell[7066]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
[   20.079824] darkstar-xps gnome-shell[7066]: Will monitor session 2
[   20.348086] darkstar-xps gnome-shell[7066]: Telepathy is not available, chat integration will be disabled.
[   20.620949] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[   20.653795] darkstar-xps gnome-shell[7066]: Extension user-theme@gnome-shell-extensions.gcampax.github.com already installed in /home/christoph/.local/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com will not be loaded
[   22.114920] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[   22.116582] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[   22.116916] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[   22.117533] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[   22.118112] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[   22.118390] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[   22.118931] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[   22.119413] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[   22.119708] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[   24.302815] darkstar-xps gnome-shell[7066]: GNOME Shell started at Thu May 05 2022 10:34:51 GMT+0200 (CEST)
[   24.304822] darkstar-xps gnome-shell[7066]: Registering session with GDM
[   25.280395] darkstar-xps gnome-shell[7066]: ATK Bridge is disabled but a11y has already been enabled.
[   27.130152] darkstar-xps gnome-shell[7066]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[  413.121546] darkstar-xps gnome-shell[7066]: Buggy client caused popup to be placed outside of parent window
[  420.732460] darkstar-xps gnome-shell[7066]: Buggy client caused popup to be placed outside of parent window
[  491.921539] darkstar-xps gnome-shell[7066]: Window manager warning: last_user_time (491920) is greater than comparison timestamp (491919).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[  491.921539] darkstar-xps gnome-shell[7066]: Window manager warning: W5 appears to be one of the offending windows with a timestamp of 491920.  Working around...
[  609.181707] darkstar-xps gnome-shell[7066]: An active wireless connection, in infrastructure mode, involves no access point?
[  625.311930] darkstar-xps gnome-shell[7066]: Timelines with detached actors are not supported. <dashtodockContainer>[<StBin>:0x563b37007070] in animation of duration 500ms but not on stage.
[  625.928451] darkstar-xps gnome-shell[7066]: Removing a network device that was not added
[  625.936661] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[  625.936840] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[  625.937025] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[  625.937129] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[  625.937198] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[  625.937246] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[  625.937294] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[  625.937340] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[  625.937383] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[  652.065679] darkstar-xps gnome-shell[7066]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[  654.664423] darkstar-xps gnome-shell[7066]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[  657.378331] darkstar-xps gnome-shell[7066]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[  660.746930] darkstar-xps gnome-shell[7066]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[  663.796648] darkstar-xps gnome-shell[7066]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe00035.
[  666.278966] darkstar-xps gnome-shell[7066]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0003b.
[  755.065227] darkstar-xps gnome-shell[7066]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[ 1453.456202] darkstar-xps gnome-shell[7066]: Window manager warning: last_user_time (1453441) is greater than comparison timestamp (1453436).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[ 1453.456202] darkstar-xps gnome-shell[7066]: Window manager warning: W0 appears to be one of the offending windows with a timestamp of 1453441.  Working around...
[ 1510.611678] darkstar-xps gnome-shell[7066]: Window manager warning: last_user_time (1510604) is greater than comparison timestamp (1510598).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[ 1510.611678] darkstar-xps gnome-shell[7066]: Window manager warning: W0 appears to be one of the offending windows with a timestamp of 1510604.  Working around...
[ 2454.895939] darkstar-xps gnome-shell[7066]: Window manager warning: last_user_time (2454895) is greater than comparison timestamp (2454894).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[ 2454.895939] darkstar-xps gnome-shell[7066]: Window manager warning: W0 appears to be one of the offending windows with a timestamp of 2454895.  Working around...
[ 2470.010523] darkstar-xps gnome-shell[7066]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
[ 2475.234505] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gray-Theme/gnome-shell/gnome-shell.css
[ 2478.289624] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2522.868445] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Dark-Glass-Pro/gnome-shell/gnome-shell.css
[ 2525.743854] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2540.465446] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Transparent shell theme 3.0.4/gnome-shell/gnome-shell.css
[ 2540.494758] darkstar-xps gnome-shell[7066]: length values must specify a unit
[ 2545.563622] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2581.566095] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[ 2584.470610] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2626.568006] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[ 2628.868604] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2641.301905] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[ 2646.319860] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2667.454800] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[ 2669.538311] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2684.818607] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[ 2686.850351] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2717.885330] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Dark-Glass-Pro/gnome-shell/gnome-shell.css
[ 2720.337458] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2789.855162] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Dark-Glass-Pro/gnome-shell/gnome-shell.css
[ 2796.759870] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2820.462423] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Dark-Glass-Pro/gnome-shell/gnome-shell.css
[ 2823.287360] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2836.606696] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Dark-Glass-Pro/gnome-shell/gnome-shell.css
[ 2841.053955] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2873.518044] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Cloudy-Light-Blue-GnomeShell/gnome-shell/gnome-shell.css
[ 2873.545655] darkstar-xps gnome-shell[7066]: Ignoring length property that isn't a number at line 711, col 24
[ 2876.624944] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2925.270417] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Cloudy-Light-Blue-GnomeShell/gnome-shell/gnome-shell.css
[ 2925.297322] darkstar-xps gnome-shell[7066]: Ignoring length property that isn't a number at line 711, col 24
[ 2927.506772] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2948.749575] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Dark-Glass-Pro/gnome-shell/gnome-shell.css
[ 2950.804253] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 2980.584609] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Dark-Glass-Pro/gnome-shell/gnome-shell.css
[ 2985.758856] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 3097.687213] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Dark-Glass-Pro/gnome-shell/gnome-shell.css
[ 3099.853966] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 3134.966396] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Glass-Gnome/gnome-shell/gnome-shell.css
[ 3138.221404] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 3246.411213] darkstar-xps gnome-shell[7066]: loading user theme: /usr/share/themes/Greybird/gnome-shell/gnome-shell.css
[ 3249.126300] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 3642.492156] darkstar-xps gnome-shell[7066]: An active wireless connection, in infrastructure mode, involves no access point?
[ 3642.877825] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[ 3642.877825] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[ 3642.877825] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[ 3642.877825] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[ 3642.877825] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[ 3642.877825] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[ 3642.877825] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[ 3642.877825] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[ 3642.878370] darkstar-xps gnome-shell[7066]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[ 3643.214751] darkstar-xps gnome-shell[7066]: Removing a network device that was not added
[ 3764.031711] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[ 3767.621784] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 3836.954683] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[ 3839.857198] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 4387.164523] darkstar-xps gnome-shell[7066]: loading user theme: /usr/share/themes/Yaru/gnome-shell/gnome-shell.css
[ 4396.141900] darkstar-xps gnome-shell[7066]: loading user theme: /usr/share/themes/Yaru-blue/gnome-shell/gnome-shell.css
[ 4406.268425] darkstar-xps gnome-shell[7066]: loading user theme: /usr/share/themes/Adapta-Eta/gnome-shell/gnome-shell.css
[ 4412.558892] darkstar-xps gnome-shell[7066]: loading user theme: /usr/share/themes/Adapta/gnome-shell/gnome-shell.css
[ 4418.489508] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Dark-Glass-Pro/gnome-shell/gnome-shell.css
[ 4427.625097] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Cloudy-Light-Blue-GnomeShell/gnome-shell/gnome-shell.css
[ 4427.650268] darkstar-xps gnome-shell[7066]: Ignoring length property that isn't a number at line 711, col 24
[ 4494.051525] darkstar-xps gnome-shell[7066]: Ignoring length property that isn't a number at line 711, col 24
[ 4494.081274] darkstar-xps gnome-shell[7066]: Ignoring length property that isn't a number at line 711, col 24
[ 4495.203352] darkstar-xps gnome-shell[7066]: Ignoring length property that isn't a number at line 711, col 24
[ 4611.664148] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 5014.455734] darkstar-xps gnome-shell[7066]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_search_ListSearchResult>:0x563b38b42590] in animation of duration 100ms but not on stage.
[ 5082.026907] darkstar-xps gnome-shell[7066]: loading user theme: /usr/share/themes/Yaru/gnome-shell/gnome-shell.css
[ 5243.445437] darkstar-xps gnome-shell[7066]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[ 5643.230725] darkstar-xps gnome-shell[7066]: Window manager warning: last_user_time (5643130) is greater than comparison timestamp (5643118).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[ 5643.230725] darkstar-xps gnome-shell[7066]: Window manager warning: W62 appears to be one of the offending windows with a timestamp of 5643130.  Working around...
[ 5736.046711] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 5769.440047] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[ 5771.660143] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 5944.549224] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[ 5946.947757] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 5982.552565] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Dark-Glass-Pro/gnome-shell/gnome-shell.css
[ 5984.911258] darkstar-xps gnome-shell[7066]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 6101.541440] darkstar-xps gnome-shell[7066]: Lost or failed to acquire name org.gnome.Mutter.ScreenCast
[ 6101.541681] darkstar-xps gnome-shell[7066]: Lost or failed to acquire name org.gnome.Mutter.RemoteDesktop
[ 6101.546944] darkstar-xps gnome-shell[7066]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
[ 6101.553435] darkstar-xps gnome-shell[7066]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
[ 6101.554316] darkstar-xps gnome-shell[7066]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
[ 6101.555160] darkstar-xps gnome-shell[7066]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
[ 6101.560357] darkstar-xps gnome-shell[7066]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
[ 6101.613615] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.613777] darkstar-xps gnome-shell[7066]: The offending signal was notify on NMDeviceWifi 0x563b36832390.
[ 6101.613865] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.613865] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.613865] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.613865] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.614048] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.614110] darkstar-xps gnome-shell[7066]: The offending signal was notify on NMAccessPoint 0x563b363fae40.
[ 6101.614182] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.614248] darkstar-xps gnome-shell[7066]: The offending signal was notify on NMActiveConnection 0x563b36836a40.
[ 6101.614311] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.614375] darkstar-xps gnome-shell[7066]: The offending signal was state-changed on NMDeviceWifi 0x563b36832390.
[ 6101.614725] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.614818] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.615003] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615003] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615003] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615003] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615003] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615003] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615003] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615003] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615410] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.615480] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615480] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615480] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615480] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615480] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615480] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615480] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615854] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.615924] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615924] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615924] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615924] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615924] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615924] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615924] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615924] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615924] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615924] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.615924] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616337] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.616405] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617092] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.617200] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618582] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.618656] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.619891] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b371be540.
[ 6101.619955] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.619985] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.620029] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b371be540.
[ 6101.620071] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.620114] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b371be540.
[ 6101.620152] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.620202] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b371be540.
[ 6101.620245] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.620295] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b371b7be0.
[ 6101.620349] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.620415] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.620473] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.620520] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b370f6660.
[ 6101.620563] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.620602] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b370f6660.
[ 6101.620644] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.620686] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b370f6660.
[ 6101.620730] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.620769] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b370f6660.
[ 6101.620809] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.620851] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b35924730.
[ 6101.620893] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.620932] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.620974] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.621018] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b358d8890.
[ 6101.621063] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.621105] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b358d8890.
[ 6101.621146] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.621188] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b358d8890.
[ 6101.621237] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.621300] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b358d8890.
[ 6101.621364] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.621424] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b371ee6c0.
[ 6101.621489] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.621537] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.621579] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.621624] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37128840.
[ 6101.621666] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.621707] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37128840.
[ 6101.621748] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.621789] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37128840.
[ 6101.622253] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.622331] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37128840.
[ 6101.622400] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.622467] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b370fb830.
[ 6101.622532] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.622597] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.622766] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.622831] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37131980.
[ 6101.622903] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.622967] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37131980.
[ 6101.623101] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.623196] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37131980.
[ 6101.623250] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.623314] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37131980.
[ 6101.623530] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.623635] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b370feeb0.
[ 6101.623691] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.623743] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.623798] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.623850] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35d40d30.
[ 6101.623913] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.623996] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35d40d30.
[ 6101.624085] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.624178] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35d40d30.
[ 6101.624243] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.624299] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35d40d30.
[ 6101.624351] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.624401] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b34d87890.
[ 6101.624457] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.624512] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.624563] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.624614] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b34b29460.
[ 6101.624666] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.624720] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b34b29460.
[ 6101.624773] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.624832] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b34b29460.
[ 6101.624885] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.624941] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b34b29460.
[ 6101.624994] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.625049] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b35eaf5c0.
[ 6101.625113] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.625223] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.625287] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.625376] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b355525a0.
[ 6101.625440] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.625511] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b355525a0.
[ 6101.625577] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.625645] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b355525a0.
[ 6101.625709] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.625774] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b355525a0.
[ 6101.625951] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.626026] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b34abf0f0.
[ 6101.626094] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.626161] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.626229] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.626302] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b371886c0.
[ 6101.626372] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.626432] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b371886c0.
[ 6101.626493] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.626555] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b371886c0.
[ 6101.626615] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.626677] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b371886c0.
[ 6101.626738] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.626800] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b3591a800.
[ 6101.626864] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.626925] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.626983] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.627045] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37e04450.
[ 6101.627103] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.627167] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37e04450.
[ 6101.627227] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.627288] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37e04450.
[ 6101.627344] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.627403] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37e04450.
[ 6101.627464] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.627533] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b371a1c20.
[ 6101.627634] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.627700] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.627763] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.627832] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35c85e10.
[ 6101.627900] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.627969] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35c85e10.
[ 6101.628040] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.628107] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35c85e10.
[ 6101.628169] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.628235] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35c85e10.
[ 6101.628306] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.628371] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b37118cc0.
[ 6101.628462] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.628572] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.628640] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.628702] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b348b8750.
[ 6101.628765] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.628827] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b348b8750.
[ 6101.628885] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.628947] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b348b8750.
[ 6101.629010] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.629070] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b348b8750.
[ 6101.629131] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.629190] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b3587df40.
[ 6101.629252] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.629317] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.629383] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.629442] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35926860.
[ 6101.629505] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.629563] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35926860.
[ 6101.629623] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.629683] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35926860.
[ 6101.629874] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.629944] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35926860.
[ 6101.629999] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.630058] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b37129ac0.
[ 6101.630127] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.630196] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.630262] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.630334] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35919930.
[ 6101.630412] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.630477] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630477] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630477] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630477] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630477] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630477] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630477] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630811] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35919930.
[ 6101.630864] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630864] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630864] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630864] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630864] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630864] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630864] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630864] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630864] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630864] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630864] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.630864] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.631162] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.631208] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.631208] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.631208] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.631208] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.631208] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.631208] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.631208] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.631208] darkstar-xps gnome-shell[7066]: == Stack trace for context 0x563b34705490 ==
[ 6101.631409] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35919930.
[ 6101.631453] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.631497] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b35919930.
[ 6101.631541] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.631585] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b349bdc30.
[ 6101.631633] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.631675] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.631715] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.631757] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b3591bc60.
[ 6101.631804] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.631849] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b3591bc60.
[ 6101.631892] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.631938] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b3591bc60.
[ 6101.631981] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.632023] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b3591bc60.
[ 6101.632065] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.632106] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b36dd5430.
[ 6101.632146] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.632189] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.632233] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.632274] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b3716d900.
[ 6101.632315] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.632358] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b3716d900.
[ 6101.632401] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.632445] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b3716d900.
[ 6101.632488] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.632532] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b3716d900.
[ 6101.632573] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.632614] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b370bb880.
[ 6101.632656] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.632698] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.632742] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.632783] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b3480bc60.
[ 6101.632826] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.632869] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b3480bc60.
[ 6101.632911] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.632951] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b3480bc60.
[ 6101.632992] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.633036] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b3480bc60.
[ 6101.633084] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.633136] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b35933e80.
[ 6101.633184] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.633232] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b3590e770.
[ 6101.633281] darkstar-xps gnome-shell[7066]: 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.
[ 6101.633336] darkstar-xps gnome-shell[7066]: The offending callback was set_container(), a vfunc.
[ 6101.633389] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.633437] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x563b37dd2460.
[ 6101.633489] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.633540] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x563b37dd2460.
[ 6101.633590] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.633640] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x563b37dd2460.
[ 6101.633692] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.633744] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b36803660.
[ 6101.633794] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.633908] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b36803660.
[ 6101.634100] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.634174] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b36803660.
[ 6101.634242] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.634309] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b36803660.
[ 6101.634419] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.634516] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b36805030.
[ 6101.634606] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.634668] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b37dd2460.
[ 6101.634863] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.634956] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37caf060.
[ 6101.635030] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.635099] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37caf060.
[ 6101.635171] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.635240] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37caf060.
[ 6101.635308] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.635377] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37caf060.
[ 6101.635446] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.635514] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b37cb3630.
[ 6101.635577] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.635772] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b37dd2460.
[ 6101.635877] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.635941] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37d90460.
[ 6101.636036] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.636103] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37d90460.
[ 6101.636171] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.636235] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37d90460.
[ 6101.636303] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.636375] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37d90460.
[ 6101.636436] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.636497] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b37d93c30.
[ 6101.636562] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.636630] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b37dd2460.
[ 6101.636800] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.636867] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37d9e260.
[ 6101.636936] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.637040] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37d9e260.
[ 6101.637164] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.637227] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37d9e260.
[ 6101.637286] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.637350] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x563b37d9e260.
[ 6101.637414] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.637475] darkstar-xps gnome-shell[7066]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x563b3486c030.
[ 6101.637542] darkstar-xps gnome-shell[7066]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6101.637635] darkstar-xps gnome-shell[7066]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x563b37dd2460.
[ 6101.637774] darkstar-xps gnome-shell[7066]: 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.
[ 6101.637852] darkstar-xps gnome-shell[7066]: The offending callback was set_container(), a vfunc.
[ 6111.432499] darkstar-xps gnome-shell[823630]: Running GNOME Shell (using mutter 42.0) as a Wayland display server
[ 6111.474985] darkstar-xps gnome-shell[823630]: Device '/dev/dri/card0' prefers shadow buffer
[ 6111.482041] darkstar-xps gnome-shell[823630]: Added device '/dev/dri/card0' (i915) using atomic mode setting.
[ 6111.568516] darkstar-xps gnome-shell[823630]: Created gbm renderer for '/dev/dri/card0'
[ 6111.568814] darkstar-xps gnome-shell[823630]: Boot VGA GPU /dev/dri/card0 selected as primary
[ 6112.069286] darkstar-xps gnome-shell[823630]: Using public X11 display :0, (using :1 for managed services)
[ 6112.069565] darkstar-xps gnome-shell[823630]: Using Wayland display name 'wayland-0'
[ 6112.844687] darkstar-xps gnome-shell[823630]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
[ 6112.845211] darkstar-xps gnome-shell[823630]: Will monitor session 24
[ 6113.340363] darkstar-xps gnome-shell[823630]: Telepathy is not available, chat integration will be disabled.
[ 6113.520479] darkstar-xps gnome-shell[823630]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 6113.543678] darkstar-xps gnome-shell[823630]: Extension user-theme@gnome-shell-extensions.gcampax.github.com already installed in /home/christoph/.local/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com will not be loaded
[ 6114.736212] darkstar-xps gnome-shell[823630]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[ 6114.736797] darkstar-xps gnome-shell[823630]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[ 6114.736797] darkstar-xps gnome-shell[823630]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[ 6114.736797] darkstar-xps gnome-shell[823630]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[ 6114.737049] darkstar-xps gnome-shell[823630]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[ 6114.737049] darkstar-xps gnome-shell[823630]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[ 6114.737049] darkstar-xps gnome-shell[823630]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[ 6114.737321] darkstar-xps gnome-shell[823630]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[ 6114.737321] darkstar-xps gnome-shell[823630]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[ 6116.153443] darkstar-xps gnome-shell[823630]: GNOME Shell started at Fri May 06 2022 17:40:27 GMT+0200 (CEST)
[ 6116.154662] darkstar-xps gnome-shell[823630]: Registering session with GDM
[ 6117.099372] darkstar-xps gnome-shell[823630]: ATK Bridge is disabled but a11y has already been enabled.
[ 6118.773770] darkstar-xps gnome-shell[823630]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[ 6118.820713] darkstar-xps gnome-shell[823630]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[ 6143.771406] darkstar-xps gnome-shell[823630]: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor2
[ 6145.355444] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.355790] darkstar-xps gnome-shell[823630]: The offending signal was notify on NMDeviceWifi 0x55768fd083e0.
[ 6145.355882] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.355882] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.355882] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.356148] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.356212] darkstar-xps gnome-shell[823630]: The offending signal was notify on NMActiveConnection 0x55768fd0b6c0.
[ 6145.356394] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.356464] darkstar-xps gnome-shell[823630]: The offending signal was state-changed on NMDeviceWifi 0x55768fd083e0.
[ 6145.359171] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.359348] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.359442] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359442] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359442] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359442] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359442] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359442] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359442] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359442] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359833] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.359916] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359916] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359916] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359916] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359916] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359916] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359916] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359916] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359916] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359916] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.359916] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.360451] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.360535] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.360535] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.360535] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.360535] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.360535] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.360535] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.360535] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.360535] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.360535] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.360535] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.360535] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.360535] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.360535] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361194] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.361282] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.362855] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.363010] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365107] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365211] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.365767] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55769137f2b0.
[ 6145.366107] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.366184] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55769137f2b0.
[ 6145.366257] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.366324] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55769137f2b0.
[ 6145.366395] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.366460] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55769137f2b0.
[ 6145.366630] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.366695] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55768ded4e00.
[ 6145.366812] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.367028] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.367136] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.367348] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768edb6e60.
[ 6145.367457] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.367564] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768edb6e60.
[ 6145.367799] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.367915] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768edb6e60.
[ 6145.368014] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.368087] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768edb6e60.
[ 6145.368189] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.368254] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55768fc4e100.
[ 6145.368323] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.368390] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.368500] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.369387] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768ed83a50.
[ 6145.369515] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.369578] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768ed83a50.
[ 6145.369635] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.369696] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768ed83a50.
[ 6145.369750] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.369820] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768ed83a50.
[ 6145.369917] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.370008] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55768edc3b90.
[ 6145.370135] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.370413] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.370631] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.370723] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768ed9b830.
[ 6145.370926] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.371024] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768ed9b830.
[ 6145.371230] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.371434] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768ed9b830.
[ 6145.371533] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.371734] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768ed9b830.
[ 6145.371828] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.372067] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55768edbc9f0.
[ 6145.372218] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.372367] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.372564] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.372664] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768edafe60.
[ 6145.372865] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.373059] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768edafe60.
[ 6145.373200] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.373295] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768edafe60.
[ 6145.373389] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.373482] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768edafe60.
[ 6145.373585] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.373685] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55768f90a6d0.
[ 6145.373787] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.373895] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.373994] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.374193] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557690586ff0.
[ 6145.374287] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.374484] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557690586ff0.
[ 6145.374625] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.374797] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557690586ff0.
[ 6145.374859] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.374912] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557690586ff0.
[ 6145.375005] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.375066] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5576905fd4e0.
[ 6145.375122] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.375175] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.375229] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.375283] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768f79f390.
[ 6145.375432] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.375487] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768f79f390.
[ 6145.375540] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.375593] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768f79f390.
[ 6145.375645] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.375699] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768f79f390.
[ 6145.375752] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.375913] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5576905a8110.
[ 6145.375970] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.376020] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.376073] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.376127] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5576905191d0.
[ 6145.376286] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.376338] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5576905191d0.
[ 6145.376396] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.376449] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5576905191d0.
[ 6145.376501] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.376584] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5576905191d0.
[ 6145.376640] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.376798] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55768f34d330.
[ 6145.376851] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.376907] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.376959] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.377011] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768ed73230.
[ 6145.377064] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.377116] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768ed73230.
[ 6145.377274] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.377329] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768ed73230.
[ 6145.377382] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.377434] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768ed73230.
[ 6145.377486] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.377646] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5576905256f0.
[ 6145.377700] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.377753] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.377832] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.377890] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557690512d00.
[ 6145.377964] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.378097] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557690512d00.
[ 6145.378150] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.378203] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557690512d00.
[ 6145.378256] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.378311] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557690512d00.
[ 6145.378364] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.378418] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x557690599960.
[ 6145.378578] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.378633] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.378689] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.378745] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55769056fae0.
[ 6145.378811] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.378875] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55769056fae0.
[ 6145.378931] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.379084] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55769056fae0.
[ 6145.379131] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.379193] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55769056fae0.
[ 6145.379361] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.379413] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x557690559e00.
[ 6145.379475] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.379562] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.379718] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.379781] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768f1d4210.
[ 6145.379841] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.379905] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768f1d4210.
[ 6145.380068] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.380132] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768f1d4210.
[ 6145.380189] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.380343] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768f1d4210.
[ 6145.380435] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.380507] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55768f1e8310.
[ 6145.380654] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.380744] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.380803] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.380867] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5576904c8060.
[ 6145.381073] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.381141] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5576904c8060.
[ 6145.381204] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.381419] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5576904c8060.
[ 6145.381483] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.381544] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x5576904c8060.
[ 6145.381845] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.381971] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55769136d430.
[ 6145.382189] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.382403] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.382511] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.382730] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768dcc9930.
[ 6145.382840] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.382840] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.382840] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.382840] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.382840] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.382840] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.382840] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.384046] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.384199] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.384199] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.384199] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.384199] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.384199] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.384199] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.384557] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768dcc9930.
[ 6145.384687] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.384792] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768dcc9930.
[ 6145.384888] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.384987] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768dcc9930.
[ 6145.385051] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.385215] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55768edba9f0.
[ 6145.385315] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.385425] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.385635] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.385635] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.385635] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.385635] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.385635] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.385635] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.385635] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.385635] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.386556] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.386802] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.386802] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.386802] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.386802] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.387196] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557691341f50.
[ 6145.387384] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.387534] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557691341f50.
[ 6145.387633] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.387833] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557691341f50.
[ 6145.387916] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.388010] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557691341f50.
[ 6145.388198] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.388198] darkstar-xps gnome-shell[823630]: == Stack trace for context 0x55768db974b0 ==
[ 6145.388329] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.388531] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55769137c9e0.
[ 6145.388629] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.388828] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.388922] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.389117] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768e9e6d00.
[ 6145.389188] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.389502] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768e9e6d00.
[ 6145.389644] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.389744] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768e9e6d00.
[ 6145.389984] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.390074] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768e9e6d00.
[ 6145.390170] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.390325] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x557690508240.
[ 6145.390457] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.390551] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.390643] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.390840] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55769059e4e0.
[ 6145.390937] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.391026] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55769059e4e0.
[ 6145.391217] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.391316] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55769059e4e0.
[ 6145.391410] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.391611] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55769059e4e0.
[ 6145.391703] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.391802] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x5576905efc00.
[ 6145.391904] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.392004] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55768f095910.
[ 6145.392205] darkstar-xps gnome-shell[823630]: 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.
[ 6145.392294] darkstar-xps gnome-shell[823630]: The offending callback was set_container(), a vfunc.
[ 6145.392399] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.392606] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55769054dd00.
[ 6145.392697] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.392764] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55769054dd00.
[ 6145.392934] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.393004] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55769054dd00.
[ 6145.393094] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.393287] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768f34b280.
[ 6145.393357] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.393583] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768f34b280.
[ 6145.393675] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.394092] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768f34b280.
[ 6145.394245] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.394339] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768f34b280.
[ 6145.394531] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.394628] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x557690d300a0.
[ 6145.394827] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.394918] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55769054dd00.
[ 6145.395035] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.395216] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768dfa0570.
[ 6145.395306] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.395499] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768dfa0570.
[ 6145.395590] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.395786] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768dfa0570.
[ 6145.395879] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.396077] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768dfa0570.
[ 6145.396228] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.396361] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55768f044290.
[ 6145.396457] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.396651] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55769054dd00.
[ 6145.396843] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.396937] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557691406590.
[ 6145.397132] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.397220] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557691406590.
[ 6145.397412] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.397500] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557691406590.
[ 6145.397692] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.397787] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x557691406590.
[ 6145.397887] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.398103] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55768dee7e70.
[ 6145.398294] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.398462] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55769054dd00.
[ 6145.398652] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.398742] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768edb9aa0.
[ 6145.398942] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.399030] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768edb9aa0.
[ 6145.399249] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.399344] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768edb9aa0.
[ 6145.399537] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.399626] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55768edb9aa0.
[ 6145.399840] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.399934] darkstar-xps gnome-shell[823630]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55768ed8eba0.
[ 6145.400130] darkstar-xps gnome-shell[823630]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[ 6145.400218] darkstar-xps gnome-shell[823630]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55769054dd00.
[ 6145.400456] darkstar-xps gnome-shell[823630]: 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.
[ 6145.400548] darkstar-xps gnome-shell[823630]: The offending callback was set_container(), a vfunc.
[ 6153.876380] darkstar-xps gnome-shell[829808]: Running GNOME Shell (using mutter 42.0) as a Wayland display server
[ 6153.896556] darkstar-xps gnome-shell[829808]: Device '/dev/dri/card0' prefers shadow buffer
[ 6153.899358] darkstar-xps gnome-shell[829808]: Added device '/dev/dri/card0' (i915) using atomic mode setting.
[ 6153.952084] darkstar-xps gnome-shell[829808]: Created gbm renderer for '/dev/dri/card0'
[ 6153.952219] darkstar-xps gnome-shell[829808]: Boot VGA GPU /dev/dri/card0 selected as primary
[ 6154.218966] darkstar-xps gnome-shell[829808]: Using public X11 display :0, (using :1 for managed services)
[ 6154.219157] darkstar-xps gnome-shell[829808]: Using Wayland display name 'wayland-0'
[ 6154.525356] darkstar-xps gnome-shell[829808]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
[ 6154.525556] darkstar-xps gnome-shell[829808]: Will monitor session 27
[ 6154.755350] darkstar-xps gnome-shell[829808]: Telepathy is not available, chat integration will be disabled.
[ 6154.976247] darkstar-xps gnome-shell[829808]: Failed to create file /run/user/1000/gnome-shell-disable-extensions: Error opening file “/run/user/1000/gnome-shell-disable-extensions”: File exists
[ 6154.988505] darkstar-xps gnome-shell[829808]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[ 6155.011059] darkstar-xps gnome-shell[829808]: Extension user-theme@gnome-shell-extensions.gcampax.github.com already installed in /home/christoph/.local/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com will not be loaded
[ 6157.101909] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[ 6157.101909] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[ 6157.101909] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[ 6157.101909] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[ 6157.101909] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[ 6157.101909] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[ 6157.101909] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[ 6157.101909] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[ 6157.101909] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[ 6159.592409] darkstar-xps gnome-shell[829808]: GNOME Shell started at Fri May 06 2022 17:41:08 GMT+0200 (CEST)
[ 6159.598540] darkstar-xps gnome-shell[829808]: Registering session with GDM
[ 6161.742029] darkstar-xps gnome-shell[829808]: ATK Bridge is disabled but a11y has already been enabled.
[ 6163.192923] darkstar-xps gnome-shell[829808]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[ 6175.328387] darkstar-xps gnome-shell[829808]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[ 6179.775994] darkstar-xps gnome-shell[829808]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[ 6182.245857] darkstar-xps gnome-shell[829808]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe00037.
[ 6183.779757] darkstar-xps gnome-shell[829808]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0003d.
[ 6197.106129] darkstar-xps gnome-shell[829808]: An active wireless connection, in infrastructure mode, involves no access point?
[ 6197.600866] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[ 6197.600866] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[ 6197.601037] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[ 6197.601037] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[ 6197.601037] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[ 6197.601037] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[ 6197.601196] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[ 6197.601196] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[ 6197.601196] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[ 6197.660345] darkstar-xps gnome-shell[829808]: Removing a network device that was not added
[ 6451.983020] darkstar-xps gnome-shell[829808]: An active wireless connection, in infrastructure mode, involves no access point?
[ 6452.259012] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[ 6452.259012] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[ 6452.259012] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[ 6452.259012] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[ 6452.259012] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[ 6452.259012] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[ 6452.259012] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[ 6452.259012] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[ 6452.259012] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[ 6452.659755] darkstar-xps gnome-shell[829808]: Removing a network device that was not added
[ 6647.461625] darkstar-xps gnome-shell[829808]: libinput error: event6  - DLL075B:01 06CB:76AF Touchpad: kernel bug: Touch jump detected and discarded.
[ 6647.461625] darkstar-xps gnome-shell[829808]: See https://wayland.freedesktop.org/libinput/doc/1.20.0/touchpad-jumping-cursors.html for details
[ 6648.602535] darkstar-xps gnome-shell[829808]: libinput error: event6  - DLL075B:01 06CB:76AF Touchpad: kernel bug: Touch jump detected and discarded.
[ 6648.602535] darkstar-xps gnome-shell[829808]: See https://wayland.freedesktop.org/libinput/doc/1.20.0/touchpad-jumping-cursors.html for details
[ 7203.448131] darkstar-xps gnome-shell[829808]: Window manager warning: last_user_time (7203447) is greater than comparison timestamp (7203446).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[ 7203.448131] darkstar-xps gnome-shell[829808]: Window manager warning: W0 appears to be one of the offending windows with a timestamp of 7203447.  Working around...
[ 7526.825685] darkstar-xps gnome-shell[829808]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_iconGrid_BaseIcon>:0x55d52cb7d5a0] in animation of duration 100ms but not on stage.
[ 9090.544771] darkstar-xps gnome-shell[829808]: Window manager warning: last_user_time (9090512) is greater than comparison timestamp (9090510).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[ 9090.544771] darkstar-xps gnome-shell[829808]: Window manager warning: W0 appears to be one of the offending windows with a timestamp of 9090512.  Working around...
[ 9130.886309] darkstar-xps gnome-shell[829808]: An active wireless connection, in infrastructure mode, involves no access point?
[ 9131.473854] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[ 9131.473854] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[ 9131.473854] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[ 9131.473854] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[ 9131.473854] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[ 9131.473854] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[ 9131.473854] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[ 9131.473854] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[ 9131.473854] darkstar-xps gnome-shell[829808]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[ 9131.539074] darkstar-xps gnome-shell[829808]: Removing a network device that was not added
[ 9749.995070] darkstar-xps gnome-shell[829808]: Window manager warning: Window 0x120002e sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
[ 9852.195380] darkstar-xps gnome-shell[829808]: Object .Gjs_ui_search_ListSearchResult (0x55d530c0aca0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[ 9852.225524] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[ 9852.225524] darkstar-xps gnome-shell[829808]: #0   55d52d86e648 i   resource:///org/gnome/shell/ui/search.js:910 (2cedd77e3240 @ 54)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #1   55d52d86e5b0 i   resource:///org/gnome/shell/ui/search.js:878 (2cedd77e3150 @ 42)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #2   55d52d86e528 i   resource:///org/gnome/shell/ui/searchController.js:58 (c5a1a020b50 @ 18)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #3   55d52d86e490 i   resource:///org/gnome/shell/ui/searchController.js:230 (c5a1a0230b0 @ 32)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #4   55d52d86e3f8 i   resource:///org/gnome/shell/ui/searchController.js:153 (c5a1a020e70 @ 280)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #5   7ffd510ac1e0 b   self-hosted:1181 (32084d2b0a10 @ 454)
[ 9852.225524] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[ 9852.225524] darkstar-xps gnome-shell[829808]: #0   55d52d86e6e0 i   resource:///org/gnome/shell/misc/util.js:384 (2cedd7762470 @ 729)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #1   55d52d86e648 i   resource:///org/gnome/shell/ui/search.js:911 (2cedd77e3240 @ 82)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #2   55d52d86e5b0 i   resource:///org/gnome/shell/ui/search.js:878 (2cedd77e3150 @ 42)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #3   55d52d86e528 i   resource:///org/gnome/shell/ui/searchController.js:58 (c5a1a020b50 @ 18)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #4   55d52d86e490 i   resource:///org/gnome/shell/ui/searchController.js:230 (c5a1a0230b0 @ 32)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #5   55d52d86e3f8 i   resource:///org/gnome/shell/ui/searchController.js:153 (c5a1a020e70 @ 280)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #6   7ffd510ac1e0 b   self-hosted:1181 (32084d2b0a10 @ 454)
[ 9852.225524] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[ 9852.225524] darkstar-xps gnome-shell[829808]: #0   55d52d86e6e0 i   resource:///org/gnome/shell/misc/util.js:387 (2cedd7762470 @ 775)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #1   55d52d86e648 i   resource:///org/gnome/shell/ui/search.js:911 (2cedd77e3240 @ 82)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #2   55d52d86e5b0 i   resource:///org/gnome/shell/ui/search.js:878 (2cedd77e3150 @ 42)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #3   55d52d86e528 i   resource:///org/gnome/shell/ui/searchController.js:58 (c5a1a020b50 @ 18)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #4   55d52d86e490 i   resource:///org/gnome/shell/ui/searchController.js:230 (c5a1a0230b0 @ 32)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #5   55d52d86e3f8 i   resource:///org/gnome/shell/ui/searchController.js:153 (c5a1a020e70 @ 280)
[ 9852.225524] darkstar-xps gnome-shell[829808]: #6   7ffd510ac1e0 b   self-hosted:1181 (32084d2b0a10 @ 454)
[ 9852.226810] darkstar-xps gnome-shell[829808]: Object .Gjs_ui_search_ListSearchResult (0x55d530c0aca0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[ 9852.226887] darkstar-xps gnome-shell[829808]: Object .Gjs_ui_search_ListSearchResult (0x55d530c0aca0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[ 9852.226946] darkstar-xps gnome-shell[829808]: JS ERROR: Error: actor not in scroll view
                                                 ensureActorVisibleInScrollView@resource:///org/gnome/shell/misc/util.js:390:19
                                                 _setSelected@resource:///org/gnome/shell/ui/search.js:911:18
                                                 highlightDefault@resource:///org/gnome/shell/ui/search.js:878:14
                                                 _init/<@resource:///org/gnome/shell/ui/searchController.js:58:33
                                                 startSearch@resource:///org/gnome/shell/ui/searchController.js:230:22
                                                 _onStageKeyPress@resource:///org/gnome/shell/ui/searchController.js:153:18
[ 9852.444938] darkstar-xps gnome-shell[829808]: Object .Gjs_ui_search_ListSearchResult (0x55d530c0aca0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[ 9852.445135] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[ 9852.445135] darkstar-xps gnome-shell[829808]: #0   55d52d86ed48 i   resource:///org/gnome/shell/ui/search.js:913 (2cedd77e3240 @ 111)
[ 9852.445135] darkstar-xps gnome-shell[829808]: #1   55d52d86ec80 i   resource:///org/gnome/shell/ui/search.js:824 (2cedd77e2e70 @ 278)
[ 9852.445135] darkstar-xps gnome-shell[829808]: #2   55d52d86ec00 i   resource:///org/gnome/shell/ui/search.js:862 (2cedd77e30b0 @ 24)
[ 9852.445135] darkstar-xps gnome-shell[829808]: #3   55d52d86eb78 i   resource:///org/gnome/shell/ui/search.js:283 (2cedd77d7b50 @ 194)
[ 9852.445135] darkstar-xps gnome-shell[829808]: #4   55d52d86eae0 i   resource:///org/gnome/shell/ui/search.js:248 (2cedd77d7a10 @ 399)
[ 9852.445135] darkstar-xps gnome-shell[829808]: #5   7ffd510aa3a0 b   resource:///org/gnome/shell/ui/appDisplay.js:1855 (2cedd77c5830 @ 564)
[ 9852.445135] darkstar-xps gnome-shell[829808]: #6   55d52d86e970 i   resource:///org/gnome/shell/ui/search.js:222 (2cedd77d7970 @ 177)
[ 9852.445135] darkstar-xps gnome-shell[829808]: #7   55d52d86e8d8 i   resource:///org/gnome/shell/ui/search.js:266 (2cedd77d7b00 @ 256)
[ 9852.445135] darkstar-xps gnome-shell[829808]: #8   55d52d86e828 i   resource:///org/gnome/shell/ui/search.js:511 (2cedd77e2330 @ 291)
[ 9852.445135] darkstar-xps gnome-shell[829808]: #9   55d52d86e780 i   resource:///org/gnome/shell/ui/search.js:859 (2cedd77e3060 @ 71)
[ 9852.445135] darkstar-xps gnome-shell[829808]: #10   55d52d86e6e8 i   resource:///org/gnome/shell/ui/search.js:650 (2cedd77e28d0 @ 45)
[ 9852.445135] darkstar-xps gnome-shell[829808]: #11   55d52d86e658 i   resource:///org/gnome/shell/ui/search.js:712 (2cedd77e2bf0 @ 20)
[ 9852.445846] darkstar-xps gnome-shell[829808]: #12   55d52d86e5b0 i   resource:///org/gnome/shell/ui/appDisplay.js:1891 (2cedd77c5970 @ 269)
[ 9852.445846] darkstar-xps gnome-shell[829808]: #13   55d52d86e508 i   resource:///org/gnome/shell/ui/search.js:710 (2cedd77e2b50 @ 178)
[ 9852.445846] darkstar-xps gnome-shell[829808]: #14   7ffd510ab6f0 b   self-hosted:205 (32084d2862e0 @ 272)
[ 9852.445846] darkstar-xps gnome-shell[829808]: #15   55d52d86e480 i   resource:///org/gnome/shell/ui/search.js:698 (2cedd77e2b00 @ 79)
[ 9852.445846] darkstar-xps gnome-shell[829808]: #16   55d52d86e3f8 i   resource:///org/gnome/shell/ui/search.js:725 (2cedd77e2c40 @ 28)
[ 9852.445846] darkstar-xps gnome-shell[829808]: #17   7ffd510ac3e0 b   self-hosted:1181 (32084d2b0a10 @ 398)
[10016.056325] darkstar-xps gnome-shell[829808]: Received error from D-Bus search provider org.gnome.Calendar.desktop: Gio.IOErrorEnum: Timeout was reached
[10016.056998] darkstar-xps gnome-shell[829808]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop: Gio.IOErrorEnum: Timeout was reached
[10191.652782] darkstar-xps gnome-shell[829808]: Window manager warning: Window 0x120002e sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
[10217.782131] darkstar-xps gnome-shell[829808]: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor2
[10219.239287] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.239603] darkstar-xps gnome-shell[829808]: The offending signal was notify on NMDeviceWifi 0x55d52ea52290.
[10219.239694] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.239694] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.239694] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.239694] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.239904] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.239982] darkstar-xps gnome-shell[829808]: The offending signal was notify on NMAccessPoint 0x7f9264012120.
[10219.240051] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.240117] darkstar-xps gnome-shell[829808]: The offending signal was notify on NMActiveConnection 0x55d52ea58c00.
[10219.240187] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.240252] darkstar-xps gnome-shell[829808]: The offending signal was state-changed on NMDeviceWifi 0x55d52ea52290.
[10219.241701] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.241883] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.241973] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.241973] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.241973] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.241973] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.241973] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.241973] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.241973] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.241973] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.241973] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242539] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.242614] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243378] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.243449] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244678] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.244753] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246576] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.246666] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.247587] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.247659] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d08e460.
[10219.247731] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.247899] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d08e460.
[10219.247970] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.248020] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d08e460.
[10219.248062] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.248105] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d08e460.
[10219.248146] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.248188] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52e636a40.
[10219.248231] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.248275] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.248320] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.248361] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52f2ebed0.
[10219.248407] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.248456] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52f2ebed0.
[10219.248621] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.248694] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52f2ebed0.
[10219.248761] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.248828] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52f2ebed0.
[10219.248997] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.249061] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52faf3c30.
[10219.249110] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.249152] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.249197] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.249239] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52dafa2c0.
[10219.249283] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.249325] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52dafa2c0.
[10219.249366] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.249413] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52dafa2c0.
[10219.249459] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.249510] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52dafa2c0.
[10219.249568] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.249628] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52f2bba40.
[10219.249850] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.249912] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.249965] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.250022] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52db01420.
[10219.250076] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.250130] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52db01420.
[10219.250214] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.250277] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52db01420.
[10219.250436] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.250499] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52db01420.
[10219.250557] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.250618] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52db2bef0.
[10219.250679] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.250842] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.250900] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.250958] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52f32a8e0.
[10219.251016] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.251071] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52f32a8e0.
[10219.251123] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.251179] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52f32a8e0.
[10219.251239] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.251305] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52f32a8e0.
[10219.251473] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.251565] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52f2de9f0.
[10219.251633] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.251727] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.251918] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.252010] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52f051370.
[10219.252104] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.252196] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52f051370.
[10219.252258] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.252311] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52f051370.
[10219.252364] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.252418] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52f051370.
[10219.252470] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.252524] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52db34dd0.
[10219.252607] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.252659] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.252709] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.252761] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d8df860.
[10219.252817] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.252871] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d8df860.
[10219.252924] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.252978] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d8df860.
[10219.253027] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.253080] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d8df860.
[10219.253131] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.253187] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52db50e60.
[10219.253239] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.253290] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.253352] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.253427] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d5300c4c00.
[10219.253588] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.253640] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d5300c4c00.
[10219.253691] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.253746] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d5300c4c00.
[10219.253815] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.253878] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d5300c4c00.
[10219.254031] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.254086] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52c935620.
[10219.254141] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.254233] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.254296] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.254455] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52e0c29a0.
[10219.254510] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.254566] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52e0c29a0.
[10219.254727] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.254783] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52e0c29a0.
[10219.254875] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.255052] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52e0c29a0.
[10219.255121] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.255193] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52db38f60.
[10219.255250] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.255314] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.255371] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.255429] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d530029860.
[10219.255485] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.255542] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d530029860.
[10219.255595] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.255650] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d530029860.
[10219.255703] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.255760] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d530029860.
[10219.255814] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.255871] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52cffe370.
[10219.255928] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.255982] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.256035] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.256091] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52e10b430.
[10219.256150] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.256204] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52e10b430.
[10219.256257] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.256311] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52e10b430.
[10219.256362] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.256415] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52e10b430.
[10219.256470] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.256522] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52fffa730.
[10219.256576] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.256629] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.256685] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.256739] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52cce3da0.
[10219.256793] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.256848] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52cce3da0.
[10219.256901] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.256954] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52cce3da0.
[10219.257008] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.257063] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52cce3da0.
[10219.257117] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.257173] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52f2a7e20.
[10219.257226] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.257280] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.257334] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.257385] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52cf9d2c0.
[10219.257438] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.257493] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52cf9d2c0.
[10219.257551] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.257605] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52cf9d2c0.
[10219.257659] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.257712] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52cf9d2c0.
[10219.257763] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.258055] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52dafcb00.
[10219.258174] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.258272] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.258386] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.258494] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52fbd3370.
[10219.258597] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.258706] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52fbd3370.
[10219.258815] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.258891] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52fbd3370.
[10219.258960] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.259027] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52fbd3370.
[10219.259094] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.259160] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52cdcac30.
[10219.259225] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.259293] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.259367] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.259433] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52db10160.
[10219.259499] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.259566] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.259566] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.259566] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.259566] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.259566] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.259786] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52db10160.
[10219.259855] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.259855] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.259855] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.259855] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.259855] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.259855] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.259855] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.259855] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.259855] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260470] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.260545] darkstar-xps gnome-shell[829808]: == Stack trace for context 0x55d52c9464b0 ==
[10219.261544] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52db10160.
[10219.261648] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.261846] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52db10160.
[10219.261946] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.262014] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52cff6760.
[10219.262207] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.262300] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.262496] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.262585] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52df5ec80.
[10219.262788] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.262854] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52df5ec80.
[10219.263045] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.263137] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52df5ec80.
[10219.263232] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.263407] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52df5ec80.
[10219.263499] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.263696] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52cc89830.
[10219.263783] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.263850] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.263943] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.264036] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52ff33db0.
[10219.264231] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.264330] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52ff33db0.
[10219.264424] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.264516] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52ff33db0.
[10219.264610] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.264702] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52ff33db0.
[10219.264892] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.264986] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d5300784a0.
[10219.265192] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.265283] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52f27a350.
[10219.265374] darkstar-xps gnome-shell[829808]: 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.
[10219.265470] darkstar-xps gnome-shell[829808]: The offending callback was set_container(), a vfunc.
[10219.265566] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.266155] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55d52d6bc290.
[10219.266251] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.266447] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55d52d6bc290.
[10219.266535] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.266730] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55d52d6bc290.
[10219.266799] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.266860] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d06f3b0.
[10219.266929] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.266997] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d06f3b0.
[10219.267058] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.267122] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d06f3b0.
[10219.267185] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.267346] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d06f3b0.
[10219.267412] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.267474] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52d0706b0.
[10219.267538] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.267607] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52d6bc290.
[10219.267708] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.267800] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d7bab20.
[10219.267890] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.268151] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d7bab20.
[10219.268247] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.268340] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d7bab20.
[10219.268465] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.268565] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52d7bab20.
[10219.268675] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.268785] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52f36b830.
[10219.268995] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.269103] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52d6bc290.
[10219.269208] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.269324] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52ce2ee30.
[10219.269551] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.269668] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52ce2ee30.
[10219.269772] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.269903] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52ce2ee30.
[10219.270003] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.270117] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52ce2ee30.
[10219.270227] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.270334] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d52f292630.
[10219.270436] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.270549] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52d6bc290.
[10219.270655] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.270860] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52ef05e70.
[10219.270975] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.275908] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52ef05e70.
[10219.276026] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.276211] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52ef05e70.
[10219.276409] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.276504] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x55d52ef05e70.
[10219.276691] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.276789] darkstar-xps gnome-shell[829808]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x55d53004a5c0.
[10219.276988] darkstar-xps gnome-shell[829808]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
[10219.277181] darkstar-xps gnome-shell[829808]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x55d52d6bc290.
[10219.277272] darkstar-xps gnome-shell[829808]: 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.
[10219.277502] darkstar-xps gnome-shell[829808]: The offending callback was set_container(), a vfunc.
[10229.068335] darkstar-xps gnome-shell[1167615]: Running GNOME Shell (using mutter 42.0) as a Wayland display server
[10229.118481] darkstar-xps gnome-shell[1167615]: Device '/dev/dri/card0' prefers shadow buffer
[10229.126163] darkstar-xps gnome-shell[1167615]: Added device '/dev/dri/card0' (i915) using atomic mode setting.
[10229.234057] darkstar-xps gnome-shell[1167615]: Created gbm renderer for '/dev/dri/card0'
[10229.234984] darkstar-xps gnome-shell[1167615]: Boot VGA GPU /dev/dri/card0 selected as primary
[10229.743063] darkstar-xps gnome-shell[1167615]: Using public X11 display :0, (using :1 for managed services)
[10229.743386] darkstar-xps gnome-shell[1167615]: Using Wayland display name 'wayland-0'
[10230.436119] darkstar-xps gnome-shell[1167615]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
[10230.436365] darkstar-xps gnome-shell[1167615]: Will monitor session 41
[10230.685762] darkstar-xps gnome-shell[1167615]: Telepathy is not available, chat integration will be disabled.
[10230.896776] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[10230.921514] darkstar-xps gnome-shell[1167615]: Extension user-theme@gnome-shell-extensions.gcampax.github.com already installed in /home/christoph/.local/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com. /usr/share/gnome-shell/extensions/user-theme@gnome-shell-extensions.gcampax.github.com will not be loaded
[10232.154734] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[10232.155274] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[10232.155398] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[10232.155870] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[10232.156031] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[10232.156356] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[10232.156586] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[10232.156586] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[10232.156705] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[10234.870168] darkstar-xps gnome-shell[1167615]: GNOME Shell started at Sat May 07 2022 12:16:58 GMT+0200 (CEST)
[10234.872238] darkstar-xps gnome-shell[1167615]: Registering session with GDM
[10235.260441] darkstar-xps gnome-shell[1167615]: ATK Bridge is disabled but a11y has already been enabled.
[10236.534477] darkstar-xps gnome-shell[1167615]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[10244.608585] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_iconGrid_BaseIcon>:0x5609d4a6e010] in animation of duration 100ms but not on stage.
[10250.883237] darkstar-xps gnome-shell[1167615]: Window manager warning: Window 0x120002e sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
[10450.692465] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (10450658) is greater than comparison timestamp (10450650).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[10450.692465] darkstar-xps gnome-shell[1167615]: Window manager warning: W1 appears to be one of the offending windows with a timestamp of 10450658.  Working around...
[10552.454535] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x120044a for 0x1200465 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x120004d.
[10553.146641] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x120044a for 0x120046c window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x120004d.
[10566.626581] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x12004e1 for 0x12004e8 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x120004d.
[10835.780237] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (10835736) is greater than comparison timestamp (10835724).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[10835.780237] darkstar-xps gnome-shell[1167615]: Window manager warning: 0x1600003 appears to be one of the offending windows with a timestamp of 10835736.  Working around...
[11180.697234] darkstar-xps gnome-shell[1167615]: libinput error: event6  - DLL075B:01 06CB:76AF Touchpad: kernel bug: Touch jump detected and discarded.
[11180.697234] darkstar-xps gnome-shell[1167615]: See https://wayland.freedesktop.org/libinput/doc/1.20.0/touchpad-jumping-cursors.html for details
[11564.071336] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x12008fe for 0x1200905 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x120004d.
[11568.648026] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1200905 for 0x1200910 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x120004d.
[11854.622828] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600b1d
[11855.709417] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600b1d
[11856.000970] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600b1d
[11856.410239] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600b1d
[11912.630407] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1602b36 for 0x1602c68 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x1600b1d.
[11915.312338] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1602b36 for 0x1602c68 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x1600b1d.
[11921.239467] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1602e0f for 0x1602e59 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x1600b1d.
[11921.526770] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1602e0f for 0x1602e6d window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x1600b1d.
[12019.444621] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600aa0
[12020.430713] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600aa0
[12020.722716] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600aa0
[12021.067217] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600aa0
[12021.406204] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600aa0
[12021.738081] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600aa0
[12022.079887] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600aa0
[12022.410590] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600aa0
[12022.754555] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600aa0
[12023.091121] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600aa0
[12023.430697] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600aa0
[12023.773010] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600aa0
[12024.120199] darkstar-xps gnome-shell[1167615]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1600aa0
[12551.448846] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1200e80 for 0x1200e87 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x120004d.
[12579.239008] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1200f1c for 0x1200f23 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x120004d.
[12580.347440] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1200f1c for 0x1200f2a window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x120004d.
[13266.635664] darkstar-xps gnome-shell[1167615]: libinput error: event6  - DLL075B:01 06CB:76AF Touchpad: kernel bug: Touch jump detected and discarded.
[13266.635664] darkstar-xps gnome-shell[1167615]: See https://wayland.freedesktop.org/libinput/doc/1.20.0/touchpad-jumping-cursors.html for details
[13739.604561] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[13739.633993] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[13739.643231] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[13739.643407] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[13739.665458] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[13739.665619] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[13739.672394] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[13739.672564] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[13739.697778] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[13739.697968] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[13740.141932] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[13740.142138] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[13882.281353] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[13882.286640] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[13882.288492] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[13882.307997] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[13882.308152] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[13882.321258] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[13882.321428] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[13882.355116] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[13882.355279] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[13882.409521] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[13882.409689] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[13882.590739] darkstar-xps gnome-shell[1167615]: Failed to load file:///home/christoph/.themes/Gela-transparency/gnome-shell/noise-texture.png: Error opening file /home/christoph/.themes/Gela-transparency/gnome-shell/noise-texture.png: No such file or directory
[13882.879595] darkstar-xps gnome-shell[1167615]: 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
[13883.015080] darkstar-xps gnome-shell[1167615]: Object St.BoxLayout (0x5609d32beb60), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.015268] darkstar-xps gnome-shell[1167615]: Object .Gjs_ui_unlockDialog_UnlockDialogClock (0x5609d32c7850), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.015353] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.015353] darkstar-xps gnome-shell[1167615]: #0   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:732 (8715fe3dd0 @ 26)
[13883.015353] darkstar-xps gnome-shell[1167615]: #1   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.015353] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.015353] darkstar-xps gnome-shell[1167615]: #0   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:733 (8715fe3dd0 @ 46)
[13883.015353] darkstar-xps gnome-shell[1167615]: #1   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.015353] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.015353] darkstar-xps gnome-shell[1167615]: #0   7ffc07514df0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (5870ecbc100 @ 25)
[13883.015353] darkstar-xps gnome-shell[1167615]: #1   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:735 (8715fe3dd0 @ 93)
[13883.015353] darkstar-xps gnome-shell[1167615]: #2   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.015353] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.015353] darkstar-xps gnome-shell[1167615]: #0   7ffc07514df0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (5870ecbc100 @ 25)
[13883.015353] darkstar-xps gnome-shell[1167615]: #1   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:735 (8715fe3dd0 @ 93)
[13883.015353] darkstar-xps gnome-shell[1167615]: #2   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.015353] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.016139] darkstar-xps gnome-shell[1167615]: Object St.Button (0x5609d6045110), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.016211] darkstar-xps gnome-shell[1167615]: #0   7ffc07514df0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (5870ecbc100 @ 25)
[13883.016211] darkstar-xps gnome-shell[1167615]: #1   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:742 (8715fe3dd0 @ 238)
[13883.016211] darkstar-xps gnome-shell[1167615]: #2   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.016211] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.016211] darkstar-xps gnome-shell[1167615]: #0   7ffc07514df0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (5870ecbc100 @ 25)
[13883.016211] darkstar-xps gnome-shell[1167615]: #1   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:742 (8715fe3dd0 @ 238)
[13883.016211] darkstar-xps gnome-shell[1167615]: #2   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.016211] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.016211] darkstar-xps gnome-shell[1167615]: #0   7ffc07514df0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (5870ecbc100 @ 25)
[13883.016211] darkstar-xps gnome-shell[1167615]: #1   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:742 (8715fe3dd0 @ 238)
[13883.016211] darkstar-xps gnome-shell[1167615]: #2   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.016211] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.016211] darkstar-xps gnome-shell[1167615]: #0   7ffc07514df0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (5870ecbc100 @ 25)
[13883.016211] darkstar-xps gnome-shell[1167615]: #1   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:742 (8715fe3dd0 @ 238)
[13883.016211] darkstar-xps gnome-shell[1167615]: #2   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.016211] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.016211] darkstar-xps gnome-shell[1167615]: #0   7ffc07514df0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (5870ecbc100 @ 25)
[13883.016211] darkstar-xps gnome-shell[1167615]: #1   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:749 (8715fe3dd0 @ 345)
[13883.016211] darkstar-xps gnome-shell[1167615]: #2   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.016211] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.016211] darkstar-xps gnome-shell[1167615]: #0   7ffc07514df0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (5870ecbc100 @ 25)
[13883.016211] darkstar-xps gnome-shell[1167615]: #1   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:749 (8715fe3dd0 @ 345)
[13883.016211] darkstar-xps gnome-shell[1167615]: #2   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.016211] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.017405] darkstar-xps gnome-shell[1167615]: Object St.Button (0x5609d6045110), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.017480] darkstar-xps gnome-shell[1167615]: #0   7ffc07514df0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (5870ecbc100 @ 25)
[13883.017480] darkstar-xps gnome-shell[1167615]: #1   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:749 (8715fe3dd0 @ 345)
[13883.017480] darkstar-xps gnome-shell[1167615]: #2   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.017480] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.017480] darkstar-xps gnome-shell[1167615]: #0   7ffc07514df0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (5870ecbc100 @ 25)
[13883.017480] darkstar-xps gnome-shell[1167615]: #1   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:749 (8715fe3dd0 @ 345)
[13883.017480] darkstar-xps gnome-shell[1167615]: #2   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.017480] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.017480] darkstar-xps gnome-shell[1167615]: #0   7ffc07514df0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (5870ecbc100 @ 25)
[13883.017480] darkstar-xps gnome-shell[1167615]: #1   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:756 (8715fe3dd0 @ 426)
[13883.017480] darkstar-xps gnome-shell[1167615]: #2   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.017480] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.017480] darkstar-xps gnome-shell[1167615]: #0   7ffc07514df0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (5870ecbc100 @ 25)
[13883.017480] darkstar-xps gnome-shell[1167615]: #1   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:756 (8715fe3dd0 @ 426)
[13883.017480] darkstar-xps gnome-shell[1167615]: #2   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.017480] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[13883.017480] darkstar-xps gnome-shell[1167615]: #0   7ffc07514df0 b   resource:///org/gnome/gjs/modules/core/overrides/GObject.js:685 (5870ecbc100 @ 25)
[13883.017480] darkstar-xps gnome-shell[1167615]: #1   5609d5eefc40 i   resource:///org/gnome/shell/ui/unlockDialog.js:756 (8715fe3dd0 @ 426)
[13883.017480] darkstar-xps gnome-shell[1167615]: #2   5609d5eefbb8 i   resource:///org/gnome/shell/ui/unlockDialog.js:493 (8715fe39c0 @ 27)
[13883.018392] darkstar-xps gnome-shell[1167615]: Object St.BoxLayout (0x5609d32beb60), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.018470] darkstar-xps gnome-shell[1167615]: Object St.BoxLayout (0x5609d32beb60), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.018533] darkstar-xps gnome-shell[1167615]: Object St.BoxLayout (0x5609d32beb60), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.018591] darkstar-xps gnome-shell[1167615]: Object St.BoxLayout (0x5609d32beb60), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.018652] darkstar-xps gnome-shell[1167615]: Object .Gjs_ui_unlockDialog_UnlockDialogClock (0x5609d32c7850), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.018714] darkstar-xps gnome-shell[1167615]: Object .Gjs_ui_unlockDialog_UnlockDialogClock (0x5609d32c7850), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.018774] darkstar-xps gnome-shell[1167615]: Object .Gjs_ui_unlockDialog_UnlockDialogClock (0x5609d32c7850), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.018836] darkstar-xps gnome-shell[1167615]: Object .Gjs_ui_unlockDialog_UnlockDialogClock (0x5609d32c7850), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.018900] darkstar-xps gnome-shell[1167615]: Object St.Button (0x5609d6045110), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.018962] darkstar-xps gnome-shell[1167615]: Object St.Button (0x5609d6045110), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.019023] darkstar-xps gnome-shell[1167615]: Object St.Button (0x5609d6045110), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[13883.025749] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[13883.026349] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[13883.026420] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[13883.026480] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[13883.026480] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[13883.026480] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[13883.026611] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[13883.026611] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[13883.026750] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[14175.865126] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_search_ListSearchResult>:0x5609d393bf50] in animation of duration 100ms but not on stage.
[14176.147479] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_search_ListSearchResult>:0x5609d2363890] in animation of duration 100ms but not on stage.
[14176.200321] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_search_ListSearchResult>:0x5609d4452e50] in animation of duration 100ms but not on stage.
[14176.900360] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_search_ListSearchResult>:0x5609d68d12b0] in animation of duration 100ms but not on stage.
[14177.998202] darkstar-xps gnome-shell[1167615]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
[14183.248541] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[14191.606623] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[14243.025292] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[14245.471780] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[14580.433701] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[14582.535694] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[14596.007578] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[14599.144296] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[14681.959149] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[14687.900301] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[14721.484564] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[14723.625260] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[14737.871661] darkstar-xps gnome-shell[1167615]: loading user theme: /usr/share/themes/Greybird/gnome-shell/gnome-shell.css
[14741.725474] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[14790.645683] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[14796.042573] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[14810.887673] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Glass-Gnome/gnome-shell/gnome-shell.css
[14813.970986] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[14830.649505] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[14832.955456] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[14946.115515] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[14948.615168] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[15113.395566] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[15115.635923] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[15253.389953] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[15255.764827] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[15278.018471] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[15281.602017] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[15346.296074] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[15348.604175] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[15422.629727] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[15424.677840] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[15465.893173] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[15467.792911] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[15532.822512] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[15535.209515] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[15743.337004] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[15745.269031] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[15795.940707] darkstar-xps gnome-shell[1167615]: libinput error: event6  - DLL075B:01 06CB:76AF Touchpad: kernel bug: Touch jump detected and discarded.
[15795.940707] darkstar-xps gnome-shell[1167615]: See https://wayland.freedesktop.org/libinput/doc/1.20.0/touchpad-jumping-cursors.html for details
[15887.309178] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[15889.230048] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[15923.286967] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[15925.017673] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[16373.597820] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[16375.632799] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[16399.276613] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[16401.318773] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[16526.960871] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[16530.272891] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[16765.293941] darkstar-xps gnome-shell[1167615]: An active wireless connection, in infrastructure mode, involves no access point?
[16766.059342] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[16766.059484] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[16766.059542] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[16766.059596] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[16766.059643] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[16766.059643] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[16766.059740] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[16766.059805] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[16766.059981] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[16766.088667] darkstar-xps gnome-shell[1167615]: Removing a network device that was not added
[17103.689553] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (17103656) is greater than comparison timestamp (17103597).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[17103.689553] darkstar-xps gnome-shell[1167615]: Window manager warning: W0 appears to be one of the offending windows with a timestamp of 17103656.  Working around...
[20563.641591] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (20563607) is greater than comparison timestamp (20563600).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[20563.641591] darkstar-xps gnome-shell[1167615]: Window manager warning: W1 appears to be one of the offending windows with a timestamp of 20563607.  Working around...
[20580.444543] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_search_ListSearchResult>:0x5609d6bf8860] in animation of duration 100ms but not on stage.
[20585.829780] darkstar-xps gnome-shell[1167615]: Window manager warning: Window 0x140002e sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
[22134.318054] darkstar-xps gnome-shell[1167615]: An active wireless connection, in infrastructure mode, involves no access point?
[22134.584132] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[22134.584603] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[22134.584697] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[22134.584777] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[22134.584777] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[22134.584777] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[22134.584932] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[22134.584932] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[22134.584932] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[22134.948331] darkstar-xps gnome-shell[1167615]: Removing a network device that was not added
[22288.106611] darkstar-xps gnome-shell[1167615]: libinput error: event6  - DLL075B:01 06CB:76AF Touchpad: kernel bug: Touch jump detected and discarded.
[22288.106611] darkstar-xps gnome-shell[1167615]: See https://wayland.freedesktop.org/libinput/doc/1.20.0/touchpad-jumping-cursors.html for details
[22434.159965] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (22434158) is greater than comparison timestamp (22434157).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[22434.159965] darkstar-xps gnome-shell[1167615]: Window manager warning: W275 appears to be one of the offending windows with a timestamp of 22434158.  Working around...
[22549.672232] darkstar-xps gnome-shell[1167615]: Window manager warning: Window 0x140002e sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense.
[22622.472449] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1400311 for 0x1400319 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x140004d.
[22720.896189] darkstar-xps gnome-shell[1167615]: libinput error: event6  - DLL075B:01 06CB:76AF Touchpad: kernel bug: Touch jump detected and discarded.
[22720.896189] darkstar-xps gnome-shell[1167615]: See https://wayland.freedesktop.org/libinput/doc/1.20.0/touchpad-jumping-cursors.html for details
[22720.896189] darkstar-xps gnome-shell[1167615]: libinput error: event6  - DLL075B:01 06CB:76AF Touchpad: WARNING: log rate limit exceeded (5 msgs per 24h). Discarding future messages.
[22747.358200] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1400596 for 0x14005a0 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x140004d.
[22748.926180] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1400596 for 0x14005a5 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x140004d.
[22750.179726] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1400596 for 0x14005aa window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x140004d.
[22763.119418] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x14005c1 for 0x14005c9 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x140004d.
[22783.497078] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1400619 for 0x1400620 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x140004d.
[22807.655678] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (22807601) is greater than comparison timestamp (22807585).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[22807.655678] darkstar-xps gnome-shell[1167615]: Window manager warning: W160 appears to be one of the offending windows with a timestamp of 22807601.  Working around...
[23565.361764] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1400bce for 0x1400c02 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x1400b05.
[23565.909507] darkstar-xps gnome-shell[1167615]: Window manager warning: WM_TRANSIENT_FOR window 0x1400bce for 0x1400c12 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x1400b05.
[24403.742264] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[24403.747164] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[24403.783956] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[24403.784142] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[24403.881912] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[24403.882885] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[24403.909033] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[24403.909199] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[24403.914630] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[24403.914788] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[24404.319042] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[24404.319242] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[24787.828175] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[24787.833560] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[24787.835359] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[24787.857011] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[24787.857176] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[24787.875508] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[24787.875692] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[24787.913420] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[24787.913588] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[24787.991958] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[24787.992136] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[24788.117566] darkstar-xps gnome-shell[1167615]: Failed to load file:///home/christoph/.themes/Gela-transparency/gnome-shell/noise-texture.png: Error opening file /home/christoph/.themes/Gela-transparency/gnome-shell/noise-texture.png: No such file or directory
[24788.422411] darkstar-xps gnome-shell[1167615]: 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
[24788.526109] darkstar-xps gnome-shell[1167615]: Object Gdm.UserVerifierProxy (0x5609d48f5d70), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
[24788.526328] darkstar-xps gnome-shell[1167615]: == Stack trace for context 0x5609d20bc4a0 ==
[24788.526328] darkstar-xps gnome-shell[1167615]: #0   7ffc07515a20 b   resource:///org/gnome/gjs/modules/core/overrides/Gio.js:425 (5870eccde70 @ 77)
[24788.710310] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[24788.711504] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[24788.711504] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[24788.711504] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[24788.711504] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[24788.711504] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[24788.711504] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[24788.711504] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[24788.711504] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[26414.541290] darkstar-xps gnome-shell[1167615]: loading user theme: /usr/share/themes/Yaru-olive/gnome-shell/gnome-shell.css
[26423.821057] darkstar-xps gnome-shell[1167615]: loading user theme: /usr/share/themes/Yaru-viridian-dark/gnome-shell/gnome-shell.css
[26434.666731] darkstar-xps gnome-shell[1167615]: loading user theme: /usr/share/themes/Adapta-Nokto/gnome-shell/gnome-shell.css
[26442.116092] darkstar-xps gnome-shell[1167615]: loading user theme: /usr/share/themes/Adapta/gnome-shell/gnome-shell.css
[26445.023743] darkstar-xps gnome-shell[1167615]: loading default theme (Adwaita)
[26452.526095] darkstar-xps gnome-shell[1167615]: loading user theme: /usr/share/themes/Adapta/gnome-shell/gnome-shell.css
[26465.095415] darkstar-xps gnome-shell[1167615]: loading user theme: /usr/share/themes/Adapta-Eta/gnome-shell/gnome-shell.css
[26471.733756] darkstar-xps gnome-shell[1167615]: loading user theme: /usr/share/themes/Adapta-Nokto/gnome-shell/gnome-shell.css
[26500.062087] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (26500061) is greater than comparison timestamp (26500060).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[26500.062087] darkstar-xps gnome-shell[1167615]: Window manager warning: W1 appears to be one of the offending windows with a timestamp of 26500061.  Working around...
[26674.303422] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (26674283) is greater than comparison timestamp (26674275).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[26674.303422] darkstar-xps gnome-shell[1167615]: Window manager warning: W1 appears to be one of the offending windows with a timestamp of 26674283.  Working around...
[26973.578777] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[27053.551546] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Glass-Gnome/gnome-shell/gnome-shell.css
[27055.642993] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[27076.238934] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (27076191) is greater than comparison timestamp (27076146).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[27076.238934] darkstar-xps gnome-shell[1167615]: Window manager warning: W1 appears to be one of the offending windows with a timestamp of 27076191.  Working around...
[27204.540361] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[27207.030403] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[27243.361304] darkstar-xps gnome-shell[1167615]: loading user theme: /usr/share/themes/Adapta-Nokto/gnome-shell/gnome-shell.css
[27252.109586] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Cloudy-Light-Blue-GnomeShell/gnome-shell/gnome-shell.css
[27252.135561] darkstar-xps gnome-shell[1167615]: Ignoring length property that isn't a number at line 711, col 24
[27363.043233] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[27373.166986] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Cloudy-Light-Blue-GnomeShell/gnome-shell/gnome-shell.css
[27373.192792] darkstar-xps gnome-shell[1167615]: Ignoring length property that isn't a number at line 711, col 24
[27560.458441] darkstar-xps gnome-shell[1167615]: Ignoring length property that isn't a number at line 711, col 24
[27560.464514] darkstar-xps gnome-shell[1167615]: Ignoring length property that isn't a number at line 711, col 24
[27563.666807] darkstar-xps gnome-shell[1167615]: Ignoring length property that isn't a number at line 711, col 24
[27972.868649] darkstar-xps gnome-shell[1167615]: Ignoring length property that isn't a number at line 711, col 24
[29223.646227] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[29239.396191] darkstar-xps gnome-shell[1167615]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0xe0000e specified for 0xe0001e.
[29318.960762] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela/gnome-shell/gnome-shell.css
[29322.814911] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[30619.240728] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (30619228) is greater than comparison timestamp (30619192).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[30619.240728] darkstar-xps gnome-shell[1167615]: Window manager warning: W1 appears to be one of the offending windows with a timestamp of 30619228.  Working around...
[31362.259950] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (31362259) is greater than comparison timestamp (31362258).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[31362.259950] darkstar-xps gnome-shell[1167615]: Window manager warning: W160 appears to be one of the offending windows with a timestamp of 31362259.  Working around...
[31550.790213] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_search_ListSearchResult>:0x5609d7c0c460] in animation of duration 100ms but not on stage.
[31720.852943] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (31720841) is greater than comparison timestamp (31720832).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[31720.852943] darkstar-xps gnome-shell[1167615]: Window manager warning: W1 appears to be one of the offending windows with a timestamp of 31720841.  Working around...
[31998.378823] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (31998378) is greater than comparison timestamp (31998376).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[31998.378823] darkstar-xps gnome-shell[1167615]: Window manager warning: W1 appears to be one of the offending windows with a timestamp of 31998378.  Working around...
[32089.101084] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (32089100) is greater than comparison timestamp (32089099).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[32089.101632] darkstar-xps gnome-shell[1167615]: Window manager warning: W1 appears to be one of the offending windows with a timestamp of 32089100.  Working around...
[32543.780394] darkstar-xps gnome-shell[1167615]: An active wireless connection, in infrastructure mode, involves no access point?
[32565.789821] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <dashtodockContainer>[<StBin>:0x5609d7b2fc10] in animation of duration 500ms but not on stage.
[32566.443424] darkstar-xps gnome-shell[1167615]: Removing a network device that was not added
[32566.449908] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[32566.450077] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[32566.450077] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[32566.450077] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[32566.450255] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[32566.450255] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[32566.450255] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[32566.450255] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[32566.450464] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[32794.402127] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_iconGrid_BaseIcon>:0x5609d4395750] in animation of duration 100ms but not on stage.
[33561.252288] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (33561228) is greater than comparison timestamp (33561224).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[33561.252288] darkstar-xps gnome-shell[1167615]: Window manager warning: W160 appears to be one of the offending windows with a timestamp of 33561228.  Working around...
[33847.309990] darkstar-xps gnome-shell[1167615]: Window manager warning: last_user_time (33847261) is greater than comparison timestamp (33847253).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
[33847.309990] darkstar-xps gnome-shell[1167615]: Window manager warning: W1 appears to be one of the offending windows with a timestamp of 33847261.  Working around...
[33850.940878] darkstar-xps gnome-shell[1167615]: An active wireless connection, in infrastructure mode, involves no access point?
[33851.202203] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[33851.202355] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[33851.202355] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[33851.202355] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[33851.202355] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[33851.202557] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[33851.202557] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[33851.202557] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[33851.202557] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[33851.547244] darkstar-xps gnome-shell[1167615]: Removing a network device that was not added
[34243.448309] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[34243.478660] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[34243.491119] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[34243.491347] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[34243.573031] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[34243.573194] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[34243.596659] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[34243.596823] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[34243.602401] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[34243.602567] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[34243.945128] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[34243.945307] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[34378.584595] darkstar-xps gnome-shell[1167615]: An active wireless connection, in infrastructure mode, involves no access point?
[34379.661182] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[34379.662312] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[34379.671517] darkstar-xps gnome-shell[1167615]: loading user theme: /home/christoph/.themes/Gela-transparency/gnome-shell/gnome-shell.css
[34379.692500] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[34379.692707] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[34379.710104] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[34379.710265] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[34379.745432] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[34379.745599] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[34379.834367] darkstar-xps gnome-shell[1167615]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
[34379.834539] darkstar-xps gnome-shell[1167615]: cr_declaration_parse_list_from_buf: assertion 'parser' failed
[34379.918585] darkstar-xps gnome-shell[1167615]: Failed to load file:///home/christoph/.themes/Gela-transparency/gnome-shell/noise-texture.png: Error opening file /home/christoph/.themes/Gela-transparency/gnome-shell/noise-texture.png: No such file or directory
[34380.206805] darkstar-xps gnome-shell[1167615]: Removing a network device that was not added
[34380.374645] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[34380.374921] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[34380.374921] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[34380.374921] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[34380.374921] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[34380.374921] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[34380.374921] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[34380.374921] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[34380.375571] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[34410.627054] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[34410.627374] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[34410.627374] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[34410.627374] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[34410.627374] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[34410.627374] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[34410.627374] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[34410.627374] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[34410.627661] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[34410.696892] darkstar-xps gnome-shell[1167615]: Removing a network device that was not added
[34510.986601] darkstar-xps gnome-shell[1167615]: Attempting to add actor of type 'Gjs_ui_search_ListSearchResult' to a container of type 'StBoxLayout', but the actor has already a parent of type 'StBoxLayout'.
[34511.041354] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_search_ListSearchResult>:0x5609d7a63950] in animation of duration 100ms but not on stage.
[34513.184728] darkstar-xps gnome-shell[1167615]: Attempting to add actor of type 'Gjs_ui_search_ListSearchResult' to a container of type 'StBoxLayout', but the actor has already a parent of type 'StBoxLayout'.
[34514.445159] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_search_ListSearchResult>:0x5609d81c66f0] in animation of duration 100ms but not on stage.
[35820.126889] darkstar-xps gnome-shell[1167615]: An active wireless connection, in infrastructure mode, involves no access point?
[35832.927204] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <dashtodockContainer>[<StBin>:0x5609d7417fd0] in animation of duration 500ms but not on stage.
[35833.476473] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
[35833.476616] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
[35833.476712] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
[35833.476792] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
[35833.476792] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
[35833.476992] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
[35833.476992] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
[35833.476992] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
[35833.476992] darkstar-xps gnome-shell[1167615]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
[35833.507881] darkstar-xps gnome-shell[1167615]: Removing a network device that was not added
[36154.435939] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_iconGrid_BaseIcon>:0x5609d44fe030] in animation of duration 100ms but not on stage.
[36154.616275] darkstar-xps gnome-shell[1167615]: Timelines with detached actors are not supported. <unnamed>[<Gjs_ui_search_ListSearchResult>:0x5609d8237d50] in animation of duration 100ms but not on stage.