[ 12.070930] asus-tuf gnome-shell[3910]: Running GNOME Shell (using mutter 42.beta) as a X11 window and compositing manager [ 12.118900] asus-tuf gnome-shell[3910]: Enabling experimental feature 'x11-randr-fractional-scaling' [ 12.365430] asus-tuf gnome-shell[3910]: ATK Bridge is disabled but a11y has already been enabled. [ 12.523221] asus-tuf gnome-shell[3910]: Skipping parental controls support as it’s disabled [ 12.618942] asus-tuf gnome-shell[3910]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 12.619029] asus-tuf gnome-shell[3910]: Will monitor session 1 [ 12.732254] asus-tuf gnome-shell[3910]: Telepathy is not available, chat integration will be disabled. [ 13.923988] asus-tuf gnome-shell[3910]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _loadFile@resource:///org/gnome/shell/ui/background.js:503:20 _load@resource:///org/gnome/shell/ui/background.js:533:14 _init@resource:///org/gnome/shell/ui/background.js:282:14 Background@resource:///org/gnome/shell/ui/background.js:237:4 getBackground@resource:///org/gnome/shell/ui/background.js:624:30 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14 _init@resource:///org/gnome/shell/ui/layout.js:303:14 LayoutManager@resource:///org/gnome/shell/ui/layout.js:194:4 _initializeUI@resource:///org/gnome/shell/ui/main.js:205:21 start@resource:///org/gnome/shell/ui/main.js:170:5 @resource:///org/gnome/shell/ui/init.js:6:17 [ 13.944271] asus-tuf gnome-shell[3910]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _loadFile@resource:///org/gnome/shell/ui/background.js:503:20 _load@resource:///org/gnome/shell/ui/background.js:533:14 _init@resource:///org/gnome/shell/ui/background.js:282:14 Background@resource:///org/gnome/shell/ui/background.js:237:4 getBackground@resource:///org/gnome/shell/ui/background.js:624:30 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14 [ 13.944849] asus-tuf gnome-shell[3910]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _loadFile@resource:///org/gnome/shell/ui/background.js:503:20 _load@resource:///org/gnome/shell/ui/background.js:533:14 _init@resource:///org/gnome/shell/ui/background.js:282:14 Background@resource:///org/gnome/shell/ui/background.js:237:4 getBackground@resource:///org/gnome/shell/ui/background.js:624:30 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14 [ 14.007158] asus-tuf gnome-shell[3910]: Update check failed: Unexpected response: Cannot resolve hostname [ 14.068270] asus-tuf gnome-shell[3910]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 14.586460] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 14.586460] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 14.586744] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 14.586744] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 14.586744] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 14.586744] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 14.586744] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 14.586744] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 14.586744] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 14.586744] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 14.586744] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 14.586744] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 14.586744] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 14.749937] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 4973: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 4973 does not exist. [ 15.206974] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 15.207160] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 15.207160] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 15.207160] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 15.207160] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 15.207160] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 15.207160] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 15.207160] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 15.207334] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 15.207334] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 15.207334] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 15.207334] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 15.207334] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 15.485397] asus-tuf gnome-shell[3910]: GNOME Shell started at Wed Mar 30 2022 22:31:57 GMT+0300 (MSK) [ 15.485947] asus-tuf gnome-shell[3910]: Registering session with GDM [ 15.649892] asus-tuf ubuntu-appindicators@ubuntu.com[3910]: Skype1, Impossible to lookup icon for 'Skype1_2-panel' in path /tmp/.org.chromium.Chromium.qMGI5O [ 15.650462] asus-tuf gnome-shell[3910]: DING: Detected async api for thumbnails [ 15.656808] asus-tuf ubuntu-appindicators@ubuntu.com[3910]: unable to update icon for Skype1 [ 15.683401] asus-tuf ubuntu-appindicators@ubuntu.com[3910]: Skype1, Impossible to lookup icon for 'Skype1_2-panel' in path /tmp/.org.chromium.Chromium.qMGI5O [ 15.689305] asus-tuf gnome-shell[3910]: DING: GNOME nautilus 42.rc [ 15.695681] asus-tuf ubuntu-appindicators@ubuntu.com[3910]: unable to update icon for Skype1 [ 15.735702] asus-tuf ubuntu-appindicators@ubuntu.com[3910]: Skype1, Impossible to lookup icon for 'Skype1_2-panel' in path /tmp/.org.chromium.Chromium.qMGI5O [ 15.745911] asus-tuf ubuntu-appindicators@ubuntu.com[3910]: Skype1, Impossible to lookup icon for 'Skype1_2-panel' in path /tmp/.org.chromium.Chromium.qMGI5O [ 15.746618] asus-tuf ubuntu-appindicators@ubuntu.com[3910]: unable to update icon for Skype1 [ 15.746817] asus-tuf ubuntu-appindicators@ubuntu.com[3910]: unable to update icon for Skype1 [ 16.110667] asus-tuf ubuntu-appindicators@ubuntu.com[3910]: Skype1, Impossible to lookup icon for 'Skype1_6-panel' in path /tmp/.org.chromium.Chromium.JJ4pmf [ 16.118657] asus-tuf ubuntu-appindicators@ubuntu.com[3910]: unable to update icon for Skype1 [ 40.653891] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 40.654151] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 40.654151] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 40.654151] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 40.654151] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 40.654151] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 40.654151] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 40.654151] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 40.654151] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 40.654151] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 40.654151] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 40.654151] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 40.654151] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 42.949701] asus-tuf gnome-shell[3910]: Object 0x562d28702a60 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 44.262278] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 13566: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 13566 does not exist. [ 44.282730] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d2856aac0 Gjs_ubuntu-dock_ubuntu_com_appIcons_DockAppIcon.app-well-app ("")] which is not in the stage. [ 44.282804] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d28419020 StWidget:insensitive ("")] which is not in the stage. [ 44.282855] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d29544460 StDrawingArea.progress-bar:insensitive] which is not in the stage. [ 52.953192] asus-tuf gnome-shell[3910]: Object 0x7ffbb8132ca0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 52.953766] asus-tuf gnome-shell[3910]: Object 0x562d286a1610 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 52.953858] asus-tuf gnome-shell[3910]: Object 0x562d286a1530 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 52.954005] asus-tuf gnome-shell[3910]: Object 0x562d286a15a0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 52.954173] asus-tuf gnome-shell[3910]: Object 0x7ffbb8132c30 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 52.954278] asus-tuf gnome-shell[3910]: Object 0x562d28d50a50 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 52.954410] asus-tuf gnome-shell[3910]: Object 0x562d28d50a50 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 52.954515] asus-tuf gnome-shell[3910]: Object 0x562d286a0f50 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 52.954593] asus-tuf gnome-shell[3910]: Object 0x562d286a0d90 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 75.013228] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 75.013487] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 75.013487] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 75.013487] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 75.013487] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 75.013487] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 75.013487] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 75.013487] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 75.013487] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 75.013487] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 75.013487] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 75.013487] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 75.013831] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 76.515619] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 76.515892] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 76.515892] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 76.515892] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 76.515892] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 76.515892] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 76.515892] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 76.515892] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 76.515892] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 76.515892] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 76.515892] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 76.515892] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 76.515892] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 76.589728] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 76.589798] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 76.589846] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 76.589846] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 76.589846] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 76.589846] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 76.589846] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 76.589962] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 76.589962] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 76.589962] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 76.589962] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 76.589962] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 76.589962] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 78.940682] asus-tuf ubuntu-appindicators@ubuntu.com[3910]: unable to update icon for software-update-available [ 88.500483] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d265d6e10 Gjs_ubuntu-dock_ubuntu_com_appIcons_DockAppIcon.app-well-app ("")] which is not in the stage. [ 88.500728] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d29b88430 StWidget:insensitive ("")] which is not in the stage. [ 88.500774] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d25fdbe60 StDrawingArea.progress-bar:insensitive] which is not in the stage. [ 131.544553] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d277f66d0 Gjs_ubuntu-dock_ubuntu_com_appIcons_DockAppIcon.app-well-app ("")] which is not in the stage. [ 131.544791] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d29a37570 StWidget:insensitive ("")] which is not in the stage. [ 131.544953] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d29806d50 StDrawingArea.progress-bar:insensitive] which is not in the stage. [ 186.520492] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d29617a70 Gjs_ubuntu-dock_ubuntu_com_appIcons_DockAppIcon.app-well-app ("")] which is not in the stage. [ 186.520734] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d29542ab0 StWidget:insensitive ("")] which is not in the stage. [ 186.520900] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d27fc2c30 StDrawingArea.progress-bar:insensitive] which is not in the stage. [ 205.725929] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 68601: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 68601 does not exist. [ 212.952026] asus-tuf gnome-shell[3910]: Object 0x562d2869c510 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 212.952523] asus-tuf gnome-shell[3910]: Object 0x562d2a3a2a50 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 212.952586] asus-tuf gnome-shell[3910]: Object 0x562d2c5848b0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 212.952626] asus-tuf gnome-shell[3910]: Object 0x7ffbb80aee70 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 212.952660] asus-tuf gnome-shell[3910]: Object 0x562d2a3a2a50 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 212.952749] asus-tuf gnome-shell[3910]: Object 0x7ffbb8278f30 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 212.952839] asus-tuf gnome-shell[3910]: Object 0x7ffbb80519f0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 212.952883] asus-tuf gnome-shell[3910]: Object 0x7ffbb8051b40 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 212.952915] asus-tuf gnome-shell[3910]: Object 0x562d298cf020 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 212.952946] asus-tuf gnome-shell[3910]: Object 0x562d298cef00 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 213.741229] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 69397: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 69397 does not exist. [ 214.591900] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 69752: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 69752 does not exist. [ 215.694587] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 70032: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 70032 does not exist. [ 219.239441] asus-tuf ubuntu-appindicators@ubuntu.com[3910]: unable to update icon for steam [ 219.240030] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 70416: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 70416 does not exist. [ 219.923154] asus-tuf gnome-shell[3910]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600071 [ 222.842386] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 70745: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 70745 does not exist. [ 222.863183] asus-tuf gnome-shell[3910]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5a0000b [ 222.863234] asus-tuf gnome-shell[3910]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5a0000b [ 222.889068] asus-tuf gnome-shell[3910]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x5a0000b [ 231.595772] asus-tuf gnome-shell[3910]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _loadFile@resource:///org/gnome/shell/ui/background.js:503:20 _load@resource:///org/gnome/shell/ui/background.js:533:14 _init@resource:///org/gnome/shell/ui/background.js:282:14 Background@resource:///org/gnome/shell/ui/background.js:237:4 getBackground@resource:///org/gnome/shell/ui/background.js:624:30 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14 [ 231.595978] asus-tuf gnome-shell[3910]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _loadFile@resource:///org/gnome/shell/ui/background.js:503:20 _load@resource:///org/gnome/shell/ui/background.js:533:14 _init@resource:///org/gnome/shell/ui/background.js:282:14 Background@resource:///org/gnome/shell/ui/background.js:237:4 getBackground@resource:///org/gnome/shell/ui/background.js:624:30 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14 [ 231.637713] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d2c606170 Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock.left shrink running-dots fixed extended:insensitive "dashtodockContainer"] which is not in the stage. [ 231.637829] asus-tuf gnome-shell[3910]: Spurious clutter_actor_allocate called for actor 0x562d2c606170/[:0x562d2c606170] which isn't a descendent of the stage! [ 231.638532] asus-tuf gnome-shell[3910]: Spurious clutter_actor_allocate called for actor 0x562d2c606170/[:0x562d2c606170] which isn't a descendent of the stage! [ 231.662758] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d26260320] is on because it needs an allocation. [ 231.662828] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28754b40] is on because it needs an allocation. [ 231.662868] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28756a20] is on because it needs an allocation. [ 231.662903] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28755320] is on because it needs an allocation. [ 231.662936] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28757120] is on because it needs an allocation. [ 231.662988] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28754750] is on because it needs an allocation. [ 231.663027] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d287566a0] is on because it needs an allocation. [ 231.681043] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 231.681127] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 231.681127] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 231.681127] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 231.681207] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 231.681207] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 231.681207] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 231.681207] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 231.681207] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 231.681207] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 231.681207] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 231.681207] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 231.681207] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 231.909363] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d26260320] is on because it needs an allocation. [ 231.909485] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28755320] is on because it needs an allocation. [ 231.909540] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28757120] is on because it needs an allocation. [ 231.909597] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28754750] is on because it needs an allocation. [ 231.909643] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d287566a0] is on because it needs an allocation. [ 276.678340] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 73698: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 73698 does not exist. [ 276.980104] asus-tuf gnome-shell[3910]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _loadFile@resource:///org/gnome/shell/ui/background.js:503:20 _load@resource:///org/gnome/shell/ui/background.js:533:14 _init@resource:///org/gnome/shell/ui/background.js:282:14 Background@resource:///org/gnome/shell/ui/background.js:237:4 getBackground@resource:///org/gnome/shell/ui/background.js:624:30 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14 [ 277.186773] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d26260320] is on because it needs an allocation. [ 277.186867] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28755320] is on because it needs an allocation. [ 277.186908] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28757120] is on because it needs an allocation. [ 277.186943] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28754750] is on because it needs an allocation. [ 277.186982] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d287566a0] is on because it needs an allocation. [ 277.239279] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 277.239391] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 277.239391] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 277.239391] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 277.239391] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 277.239391] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 277.239391] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 277.239391] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 277.239666] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 277.239666] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 277.239666] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 277.239666] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 277.239666] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 302.581589] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 75472: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 75472 does not exist. [ 302.581841] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 75475: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 75475 does not exist. [ 302.620901] asus-tuf gnome-shell[3910]: setup_framebuffers: assertion 'width > 0' failed [ 309.166245] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 75813: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 75813 does not exist. [ 456.108740] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 83988: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 83988 does not exist. [ 462.013094] asus-tuf gnome-shell[3910]: Could not create transient scope for PID 84295: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 84295 does not exist. [ 495.706886] asus-tuf gnome-shell[3910]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _loadFile@resource:///org/gnome/shell/ui/background.js:503:20 _load@resource:///org/gnome/shell/ui/background.js:533:14 _init@resource:///org/gnome/shell/ui/background.js:282:14 Background@resource:///org/gnome/shell/ui/background.js:237:4 getBackground@resource:///org/gnome/shell/ui/background.js:624:30 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14 [ 495.707129] asus-tuf gnome-shell[3910]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _loadFile@resource:///org/gnome/shell/ui/background.js:503:20 _load@resource:///org/gnome/shell/ui/background.js:533:14 _init@resource:///org/gnome/shell/ui/background.js:282:14 Background@resource:///org/gnome/shell/ui/background.js:237:4 getBackground@resource:///org/gnome/shell/ui/background.js:624:30 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14 [ 495.707183] asus-tuf gnome-shell[3910]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _loadFile@resource:///org/gnome/shell/ui/background.js:503:20 _load@resource:///org/gnome/shell/ui/background.js:533:14 _init@resource:///org/gnome/shell/ui/background.js:282:14 Background@resource:///org/gnome/shell/ui/background.js:237:4 getBackground@resource:///org/gnome/shell/ui/background.js:624:30 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14 [ 495.707234] asus-tuf gnome-shell[3910]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _loadFile@resource:///org/gnome/shell/ui/background.js:503:20 _load@resource:///org/gnome/shell/ui/background.js:533:14 _init@resource:///org/gnome/shell/ui/background.js:282:14 Background@resource:///org/gnome/shell/ui/background.js:237:4 getBackground@resource:///org/gnome/shell/ui/background.js:624:30 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14 [ 496.153245] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 496.153354] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 496.153354] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 496.153354] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 496.153354] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 496.153466] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 496.153466] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 496.153466] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 496.153466] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 496.153466] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 496.153466] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 496.153466] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 496.153466] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 500.386164] asus-tuf gnome-shell[3910]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed [ 512.372662] asus-tuf gnome-shell[3910]: st_widget_get_theme_node called on the widget [0x562d278b4cb0 Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock.left shrink running-dots fixed extended:insensitive "dashtodockContainer"] which is not in the stage. [ 512.372908] asus-tuf gnome-shell[3910]: Spurious clutter_actor_allocate called for actor 0x562d278b4cb0/[:0x562d278b4cb0] which isn't a descendent of the stage! [ 512.377881] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d26260320] is on because it needs an allocation. [ 512.377952] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28755b00] is on because it needs an allocation. [ 512.377992] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28756da0] is on because it needs an allocation. [ 512.378037] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28754750] is on because it needs an allocation. [ 512.378074] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d287566a0] is on because it needs an allocation. [ 512.441782] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d26260320] is on because it needs an allocation. [ 512.441890] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28755320] is on because it needs an allocation. [ 512.441929] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28757120] is on because it needs an allocation. [ 512.441962] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d2a7c8720] is on because it needs an allocation. [ 512.442008] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28757f20] is on because it needs an allocation. [ 512.442045] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d2a7c8330] is on because it needs an allocation. [ 512.442078] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28f68a40] is on because it needs an allocation. [ 512.517865] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d26260320] is on because it needs an allocation. [ 512.517942] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28754750] is on because it needs an allocation. [ 512.517977] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d287566a0] is on because it needs an allocation. [ 512.521736] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 512.521824] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 512.521852] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 512.521852] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 512.521852] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 512.521852] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 512.521932] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 512.521932] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 512.521932] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 512.521932] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 512.521932] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 512.521932] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 512.522055] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 512.623394] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d26260320] is on because it needs an allocation. [ 512.623480] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d2a7c8330] is on because it needs an allocation. [ 512.623519] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28f68a40] is on because it needs an allocation. [ 515.556261] asus-tuf gnome-shell[3910]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed [ 521.622524] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d26260320] is on because it needs an allocation. [ 521.622760] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28755b00] is on because it needs an allocation. [ 521.622804] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28756da0] is on because it needs an allocation. [ 522.250789] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d26260320] is on because it needs an allocation. [ 522.250915] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28754750] is on because it needs an allocation. [ 522.250956] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d287566a0] is on because it needs an allocation. [ 522.250985] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d2a7c8b10] is on because it needs an allocation. [ 522.251013] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28f68340] is on because it needs an allocation. [ 522.251039] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d2a7c8720] is on because it needs an allocation. [ 522.251065] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28757f20] is on because it needs an allocation. [ 522.251104] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28755320] is on because it needs an allocation. [ 522.251137] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28757120] is on because it needs an allocation. [ 522.251166] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d2a7c8330] is on because it needs an allocation. [ 522.251209] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28f68a40] is on because it needs an allocation. [ 522.658710] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d26260320] is on because it needs an allocation. [ 522.658908] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d2a7c8330] is on because it needs an allocation. [ 522.658940] asus-tuf gnome-shell[3910]: Can't update stage views actor [:0x562d28f68a40] is on because it needs an allocation. [ 523.240323] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 523.240494] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 523.240494] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 523.240494] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 523.240494] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 523.240494] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 523.240494] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 523.240494] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 523.240494] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 523.240494] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 523.240494] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 523.240494] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 523.240494] asus-tuf gnome-shell[3910]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 524.415521] asus-tuf gnome-shell[3910]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed [ 539.489054] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.489255] asus-tuf gnome-shell[3910]: The offending signal was notify on NMDeviceEthernet 0x562d26250500. [ 539.489321] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489321] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489321] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489321] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489321] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489321] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489462] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.489535] asus-tuf gnome-shell[3910]: The offending signal was notify on NMDeviceWifi 0x562d28c28250. [ 539.489575] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.489609] asus-tuf gnome-shell[3910]: The offending signal was notify on NMAccessPoint 0x562d2bc36dd0. [ 539.489641] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.489673] asus-tuf gnome-shell[3910]: The offending signal was notify on NMActiveConnection 0x562d2c3d2180. [ 539.489719] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.489756] asus-tuf gnome-shell[3910]: The offending signal was state-changed on NMDeviceEthernet 0x562d26250500. [ 539.489789] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489789] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489789] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489789] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489789] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489789] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489917] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.489952] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489952] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489952] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489952] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489952] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489952] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489952] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489952] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489952] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.489952] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490178] asus-tuf gnome-shell[3910]: The offending signal was state-changed on NMDeviceWifi 0x562d28c28250. [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490210] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490463] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490504] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490836] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.490876] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490876] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490876] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490876] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490876] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490876] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490876] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490876] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490876] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490876] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490876] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.490876] asus-tuf gnome-shell[3910]: == Stack trace for context 0x562d25d51180 == [ 539.491066] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491095] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.491127] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491156] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2c5cb060. [ 539.491192] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491222] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2c5cb060. [ 539.491248] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491273] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2c5cb060. [ 539.491296] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491321] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562d2c5a90e0. [ 539.491357] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491386] asus-tuf gnome-shell[3910]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.491412] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491437] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2c606740. [ 539.491463] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491488] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2c606740. [ 539.491523] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491553] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2c606740. [ 539.491578] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491602] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562d2c5d8510. [ 539.491628] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491652] asus-tuf gnome-shell[3910]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.491677] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491712] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d265a59d0. [ 539.491743] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491769] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d265a59d0. [ 539.491794] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491829] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d265a59d0. [ 539.491858] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491901] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562d297a6430. [ 539.491932] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.491957] asus-tuf gnome-shell[3910]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.491981] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492005] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d277e8a20. [ 539.492030] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492066] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d277e8a20. [ 539.492095] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492120] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d277e8a20. [ 539.492151] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492179] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562d29b7de60. [ 539.492206] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492231] asus-tuf gnome-shell[3910]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.492267] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492297] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2b06fcf0. [ 539.492323] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492348] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2b06fcf0. [ 539.492372] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492407] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2b06fcf0. [ 539.492436] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492470] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562d2b200900. [ 539.492509] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492538] asus-tuf gnome-shell[3910]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.492563] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492589] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d27461010. [ 539.492623] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492661] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d27461010. [ 539.492691] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492716] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d27461010. [ 539.492739] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492763] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562d2c0ae180. [ 539.492798] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492835] asus-tuf gnome-shell[3910]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.492879] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492910] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d26323170. [ 539.492936] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.492961] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d26323170. [ 539.492986] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493021] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d26323170. [ 539.493050] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493075] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562d2940f5f0. [ 539.493100] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493125] asus-tuf gnome-shell[3910]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.493159] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493189] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2c5b7680. [ 539.493215] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493239] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2c5b7680. [ 539.493263] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493298] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2c5b7680. [ 539.493327] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493352] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562d28c61540. [ 539.493385] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493414] asus-tuf gnome-shell[3910]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.493440] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493465] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2c5fe6d0. [ 539.493502] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493532] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2c5fe6d0. [ 539.493557] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493591] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d2c5fe6d0. [ 539.493619] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493644] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562d28c214e0. [ 539.493680] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493711] asus-tuf gnome-shell[3910]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.493734] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493759] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d27201a20. [ 539.493791] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493820] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d27201a20. [ 539.493854] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493891] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d27201a20. [ 539.493921] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.493946] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562d271f7b80. [ 539.493972] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.494005] asus-tuf gnome-shell[3910]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.494033] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.494069] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d271b3b40. [ 539.494100] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.494132] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d271b3b40. [ 539.494163] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.494190] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d271b3b40. [ 539.494216] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.494241] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562d271f0830. [ 539.494278] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.494307] asus-tuf gnome-shell[3910]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.494332] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.494368] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d271d5eb0. [ 539.494396] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.494420] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d271d5eb0. [ 539.494453] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.494484] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_appDisplay_AppIcon 0x562d271d5eb0. [ 539.494509] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.494534] asus-tuf gnome-shell[3910]: The offending signal was destroy on Gjs_ui_iconGrid_BaseIcon 0x562d271e9380. [ 539.494560] asus-tuf gnome-shell[3910]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. [ 539.494594] asus-tuf gnome-shell[3910]: The offending signal was actor-removed on Gjs_ui_appDisplay_FolderGrid 0x562d272b5840. [ 539.494620] asus-tuf gnome-shell[3910]: 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. [ 539.494657] asus-tuf gnome-shell[3910]: The offending callback was set_container(), a vfunc. [ 539.501589] asus-tuf gnome-shell[3910]: GNOME Shell crashed with signal 11 [ 539.501714] asus-tuf audit[3910]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=? pid=3910 comm="gnome-shell" exe="/usr/bin/gnome-shell" sig=11 res=1 [ 545.342032] asus-tuf gnome-shell[88929]: Running GNOME Shell (using mutter 42.beta) as a Wayland display server [ 545.353851] asus-tuf gnome-shell[88929]: Device '/dev/dri/card0' prefers shadow buffer [ 545.400589] asus-tuf gnome-shell[88929]: Added device '/dev/dri/card0' (nvidia-drm) using non-atomic mode setting. [ 545.422320] asus-tuf gnome-shell[88929]: Created gbm renderer for '/dev/dri/card0' [ 545.422385] asus-tuf gnome-shell[88929]: Boot VGA GPU /dev/dri/card0 selected as primary [ 545.977408] asus-tuf gnome-shell[88929]: Using public X11 display :1024, (using :1025 for managed services) [ 545.977481] asus-tuf gnome-shell[88929]: Using Wayland display name 'wayland-0' [ 546.063362] asus-tuf gnome-shell[88929]: Skipping parental controls support as it’s disabled [ 546.112905] asus-tuf gnome-shell[88929]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 546.113042] asus-tuf gnome-shell[88929]: Will monitor session c1 [ 546.200497] asus-tuf gnome-shell[88929]: Extension ding@rastersoft.com already installed in /usr/share/gnome-shell/extensions/ding@rastersoft.com. /usr/share/gnome-shell/extensions/ding@rastersoft.com will not be loaded [ 546.200572] asus-tuf gnome-shell[88929]: Extension ubuntu-appindicators@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com will not be loaded [ 546.200650] asus-tuf gnome-shell[88929]: Extension ubuntu-dock@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com will not be loaded [ 546.200724] asus-tuf gnome-shell[88929]: Extension system-monitor@paradoxxx.zero.gmail.com already installed in /usr/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com. /usr/share/gnome-shell/extensions/system-monitor@paradoxxx.zero.gmail.com will not be loaded [ 546.205991] asus-tuf org.gnome.Shell.desktop[88929]: Window manager warning: Failed to parse saved session file: Не удалось открыть файл «/var/lib/gdm3/.config/mutter/sessions/10886cb63c4e62d483164866924938306800000888910000.ms»: Нет такого файла или каталога [ 546.227725] asus-tuf gnome-shell[88929]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 546.297179] asus-tuf gnome-shell[88929]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed [ 546.297247] asus-tuf gnome-shell[88929]: cr_declaration_parse_list_from_buf: assertion 'parser' failed [ 546.371703] asus-tuf gnome-shell[88929]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed [ 546.371839] asus-tuf gnome-shell[88929]: cr_declaration_parse_list_from_buf: assertion 'parser' failed [ 546.466275] asus-tuf gnome-shell[88929]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed [ 546.466336] asus-tuf gnome-shell[88929]: cr_declaration_parse_list_from_buf: assertion 'parser' failed [ 546.471921] asus-tuf gnome-shell[88929]: ATK Bridge is disabled but a11y has already been enabled. [ 546.854395] asus-tuf gnome-shell[88929]: Registering session with GDM [ 553.635763] asus-tuf gnome-shell[89793]: Running GNOME Shell (using mutter 42.beta) as a X11 window and compositing manager [ 553.792517] asus-tuf gnome-shell[89793]: ATK Bridge is disabled but a11y has already been enabled. [ 553.912221] asus-tuf gnome-shell[89793]: Skipping parental controls support as it’s disabled [ 553.963123] asus-tuf gnome-shell[89793]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. [ 553.963224] asus-tuf gnome-shell[89793]: Will monitor session 4 [ 554.062111] asus-tuf gnome-shell[89793]: Telepathy is not available, chat integration will be disabled. [ 554.357171] asus-tuf gnome-shell[89793]: Unhandled promise rejection. To suppress this warning, add an error handler to your promise chain with .catch() or a try-catch block around your await expression. Stack trace of the failed promise: _loadFile@resource:///org/gnome/shell/ui/background.js:503:20 _load@resource:///org/gnome/shell/ui/background.js:533:14 _init@resource:///org/gnome/shell/ui/background.js:282:14 Background@resource:///org/gnome/shell/ui/background.js:237:4 getBackground@resource:///org/gnome/shell/ui/background.js:624:30 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:795:49 BackgroundManager@resource:///org/gnome/shell/ui/background.js:721:37 _createBackgroundManager@resource:///org/gnome/shell/ui/layout.js:451:25 _updateBackgrounds@resource:///org/gnome/shell/ui/layout.js:495:34 _monitorsChanged@resource:///org/gnome/shell/ui/layout.js:557:14 _init@resource:///org/gnome/shell/ui/layout.js:303:14 LayoutManager@resource:///org/gnome/shell/ui/layout.js:194:4 _initializeUI@resource:///org/gnome/shell/ui/main.js:205:21 start@resource:///org/gnome/shell/ui/main.js:170:5 @resource:///org/gnome/shell/ui/init.js:6:17 [ 554.508102] asus-tuf gnome-shell[89793]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation [ 555.073424] asus-tuf gnome-shell[89793]: Could not create transient scope for PID 90329: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 90329 does not exist. [ 555.091200] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 555.091313] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 555.091313] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 555.091313] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 555.091313] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 555.091313] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 555.091313] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 555.091313] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 555.091313] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 555.091550] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 555.091550] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 555.091550] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 555.091550] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 555.638409] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 555.638409] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 555.638409] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 555.638409] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 555.638409] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 555.638409] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 555.638409] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 555.638690] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 555.638690] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 555.638690] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 555.638690] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 555.638690] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 555.638690] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 555.979698] asus-tuf gnome-shell[89793]: GNOME Shell started at Wed Mar 30 2022 22:40:58 GMT+0300 (MSK) [ 555.980277] asus-tuf gnome-shell[89793]: Registering session with GDM [ 556.006019] asus-tuf ubuntu-appindicators@ubuntu.com[89793]: Skype1, Impossible to lookup icon for 'Skype1_2-panel' in path /tmp/.org.chromium.Chromium.7HMRlD [ 556.038897] asus-tuf ubuntu-appindicators@ubuntu.com[89793]: unable to update icon for Skype1 [ 556.144513] asus-tuf gnome-shell[89793]: DING: Detected async api for thumbnails [ 556.176080] asus-tuf gnome-shell[89793]: DING: GNOME nautilus 42.0 [ 556.254297] asus-tuf ubuntu-appindicators@ubuntu.com[89793]: Skype1, Impossible to lookup icon for 'Skype1_6-panel' in path /tmp/.org.chromium.Chromium.3ashYi [ 556.260621] asus-tuf ubuntu-appindicators@ubuntu.com[89793]: unable to update icon for Skype1 [ 563.993041] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 563.993318] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). [ 563.993318] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). [ 563.993318] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 72 with keysym 72 (keycode 1b). [ 563.993318] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 563.993318] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). [ 563.993318] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). [ 563.993318] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). [ 563.993318] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). [ 563.993318] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b). [ 563.993318] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). [ 563.993318] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). [ 563.993318] asus-tuf gnome-shell[89793]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). [ 616.388247] asus-tuf ubuntu-appindicators@ubuntu.com[89793]: unable to update icon for software-update-available [ 618.904233] asus-tuf gnome-shell[89793]: Could not create transient scope for PID 93013: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 93013 does not exist. [ 619.485593] asus-tuf gnome-shell[89793]: Could not create transient scope for PID 93043: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 93043 does not exist. [ 623.701687] asus-tuf gnome-shell[89793]: Could not create transient scope for PID 93103: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 93103 does not exist. [ 623.704944] asus-tuf gnome-shell[89793]: Could not create transient scope for PID 93109: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 93109 does not exist. [ 630.370035] asus-tuf gnome-shell[89793]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed [ 630.608698] asus-tuf gnome-shell[89793]: Could not create transient scope for PID 93998: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 93998 does not exist. [ 633.969409] asus-tuf gnome-shell[89793]: Object 0x55613596e530 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 633.969634] asus-tuf gnome-shell[89793]: Object 0x5561359a84a0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 633.969684] asus-tuf gnome-shell[89793]: Object 0x5561359a8660 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 633.969728] asus-tuf gnome-shell[89793]: Object 0x7f38cc001d70 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 633.969768] asus-tuf gnome-shell[89793]: Object 0x7f390c0688b0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 633.969814] asus-tuf gnome-shell[89793]: Object 0x7f390c0688b0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 633.969855] asus-tuf gnome-shell[89793]: Object 0x7f390c0688b0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 643.966529] asus-tuf gnome-shell[89793]: Object 0x5561359da450 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. [ 644.403752] asus-tuf gnome-shell[89793]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed