Bug #1973583 “gnome-shell[200033]: Window manager warning: last_...” : Bugs : guake package : Ubuntu

Revision history for this message

Bartosz Woronicz (mastier1) wrote on 2022-05-16:

#1

Dependencies.txt Edit (23.1 KiB, text/plain; charset="utf-8")
GsettingsChanges.txt Edit (3.1 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (310 bytes, text/plain; charset="utf-8")
ShellJournal.txt Edit (2.5 MiB, text/plain; charset="utf-8")
monitors.xml.txt Edit (22.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2022-05-16:

#2

Looks like a difference of 11ms, so less than one frame.

This is most likely to be a buggy app (or toolkit) as the message suggests. Please try to identify what the offending app is. For example if the window ID is still 0xa0000e then:

xwininfo -id 0xa0000e

or

xprop -id 0xa0000e | grep _NET_WM_PID

affects:	gnome-shell (Ubuntu) → ubuntu
Changed in ubuntu:
status:	New → Incomplete

Revision history for this message

Bartosz Woronicz (mastier1) wrote on 2022-05-16:

#3

Thanks, Daniel!
Unfortunately, I needed to reboot the machine, but will check if that will reoccur.

I am not sure whether leaving the machine in suspend state over the course of weekend would have triggered that.

Revision history for this message

Bartosz Woronicz (mastier1) wrote on 2022-05-16:

#4

Download full text (4.5 KiB)

Ok, seems like Guake got some issues
it happens from time to time

$ guake --version
Guake Terminal: 3.8.5
VTE: 0.68.0
VTE runtime: 0.68.0
Gtk: 3.24.33

/var/log/syslog:May 16 23:35:15 graf gnome-shell[3646]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b
/var/log/syslog:May 16 23:37:13 graf gnome-shell[3646]: libinput error: event16 - Bartosz Woronicz’s Keyboard: client bug: event processing lagging behind by 33ms, your system is too slow
/var/log/syslog:May 16 23:37:32 graf gnome-shell[4011]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
/var/log/syslog:May 16 23:39:05 graf gnome-shell[3646]: 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:#012 _loadFile@resource:///org/gnome/shell/ui/background.js:488:20#012 _load@resource:///org/gnome/shell/ui/background.js:518:14#012 _init@resource:///org/gnome/shell/ui/background.js:278:14#012 Background@resource:///org/gnome/shell/ui/background.js:234:4#012 getBackground@resource:///org/gnome/shell/ui/background.js:622:30#012 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:793:49#012 _updateBackgroundActor@resource:///org/gnome/shell/ui/background.js:765:39#012 _createBackgroundActor/changeSignalId<@resource:///org/gnome/shell/ui/background.js:821:18#012 _emitChangedSignal/this._changedIdleId<@resource:///org/gnome/shell/ui/background.js:311:18
/var/log/syslog:May 16 23:45:07 graf gnome-shell[3646]: 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:#012 _loadFile@resource:///org/gnome/shell/ui/background.js:488:20#012 _load@resource:///org/gnome/shell/ui/background.js:518:14#012 _init@resource:///org/gnome/shell/ui/background.js:278:14#012 Background@resource:///org/gnome/shell/ui/background.js:234:4#012 getBackground@resource:///org/gnome/shell/ui/background.js:622:30#012 _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:793:49#012 _updateBackgroundActor@resource:///org/gnome/shell/ui/background.js:765:39#012 _createBackgroundActor/changeSignalId<@resource:///org/gnome/shell/ui/background.js:821:18#012 _emitChangedSignal/this._changedIdleId<@resource:///org/gnome/shell/ui/background.js:311:18
/var/log/syslog:May 16 23:48:25 graf gnome-shell[3646]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b
/var/log/syslog:May 16 23:50:02 graf gnome-shell[3646]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b
/var/log/syslog:May 16 23:54:34 graf gnome-shell[3646]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b
/var/log/syslog:May 17 00:00:56 graf gnome-shell[3646]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b
/var/log/syslog:May 17 00...

Ok, seems like Guake got some issues
it happens from time to time

$ guake --version
Guake Terminal: 3.8.5
VTE: 0.68.0
VTE runtime: 0.68.0
Gtk: 3.24.33

/var/log/syslog:May 16 23:35:15 graf gnome-shell[3646]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b
/var/log/syslog:May 16 23:37:13 graf gnome-shell[3646]: libinput error: event16 - Bartosz Woronicz’s Keyboard: client bug: event processing lagging behind by 33ms, your system is too slow
/var/log/syslog:May 16 23:37:32 graf gnome-shell[4011]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
/var/log/syslog:May 16 23:39:05 graf gnome-shell[3646]: 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:#012  _loadFile@resource:///org/gnome/shell/ui/background.js:488:20#012  _load@resource:///org/gnome/shell/ui/background.js:518:14#012  _init@resource:///org/gnome/shell/ui/background.js:278:14#012  Background@resource:///org/gnome/shell/ui/background.js:234:4#012  getBackground@resource:///org/gnome/shell/ui/background.js:622:30#012  _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:793:49#012  _updateBackgroundActor@resource:///org/gnome/shell/ui/background.js:765:39#012  _createBackgroundActor/changeSignalId<@resource:///org/gnome/shell/ui/background.js:821:18#012  _emitChangedSignal/this._changedIdleId<@resource:///org/gnome/shell/ui/background.js:311:18
/var/log/syslog:May 16 23:45:07 graf gnome-shell[3646]: 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:#012  _loadFile@resource:///org/gnome/shell/ui/background.js:488:20#012  _load@resource:///org/gnome/shell/ui/background.js:518:14#012  _init@resource:///org/gnome/shell/ui/background.js:278:14#012  Background@resource:///org/gnome/shell/ui/background.js:234:4#012  getBackground@resource:///org/gnome/shell/ui/background.js:622:30#012  _createBackgroundActor@resource:///org/gnome/shell/ui/background.js:793:49#012  _updateBackgroundActor@resource:///org/gnome/shell/ui/background.js:765:39#012  _createBackgroundActor/changeSignalId<@resource:///org/gnome/shell/ui/background.js:821:18#012  _emitChangedSignal/this._changedIdleId<@resource:///org/gnome/shell/ui/background.js:311:18
/var/log/syslog:May 16 23:48:25 graf gnome-shell[3646]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b
/var/log/syslog:May 16 23:50:02 graf gnome-shell[3646]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b
/var/log/syslog:May 16 23:54:34 graf gnome-shell[3646]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b
/var/log/syslog:May 17 00:00:56 graf gnome-shell[3646]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b
/var/log/syslog:May 17 00:01:37 graf gnome-shell[3646]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b
/var/log/syslog:May 17 00:02:07 graf gnome-shell[3646]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b
/var/log/syslog:May 17 00:03:15 graf gnome-shell[4011]: Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!
/var/log/syslog:May 17 00:06:38 graf gnome-shell[3646]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b
/var/log/syslog:May 17 00:08:49 graf gnome-shell[3646]: message repeated 2 times: [ Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0xa0000b]

$ xwininfo -id 0xa0000b

xwininfo: Window id: 0xa0000b "Guake!"

Absolute upper-left X:  0
  Absolute upper-left Y:  54
  Relative upper-left X:  0
  Relative upper-left Y:  54
  Width: 3840
  Height: 2106
  Depth: 32
  Visual: 0x350
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0xa00002 (not installed)
  Bit Gravity State: NorthWestGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: no
  Corners:  +0+54  -3840+54  -3840-0  +0-0
  -geometry 1920x1053+0-0

Daniel van Vugt (vanvugt) on 2022-05-17

affects:	ubuntu → guake (Ubuntu)
Changed in guake (Ubuntu):
status:	Incomplete → New

Revision history for this message

Launchpad Janitor (janitor) wrote on 2022-09-25:

#5

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in guake (Ubuntu):
status:	New → Confirmed

Revision history for this message

Sam Lalani (samlalani) wrote on 2022-12-10:

#6

(metacity:2108530): metacity-WARNING **: 02:36:37.470: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c0000d (Untitled Document 1 - gedit)

ubuntu@ip-172-31-23-58:~/.vnc$ date
Sat 10 Dec 2022 03:29:46 AM UTC

ubuntu@ip-172-31-23-58:~/.vnc$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Codename: focal

I had opened "gedit" and pasted a few thousand lines into it from the output of another program. Then I closed "gedit" without saving. A little while later I came back to my computer and noticed my VNC was blank so all the programs that were running were closed. I have two different Ubuntu EC2 servers from AWS and noticed the exact same problem on both.

Revision history for this message

Jorge PAB (jorge4llright) wrote on 2023-12-25:

#7

Download full text (6.8 KiB)

37@a37-tecnoilligent:~$ sudo systemctl disable bluemon.service
bluemon.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluemon
a37@a37-tecnoilligent:~$ sudo systemctl disable bluemon
bluemon.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluemon
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth\x2c.service
Failed to disable unit: Unit file bluetoothx2c.service does not exist.
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth\x2c
Failed to disable unit: Unit file bluetoothx2c.service does not exist.
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth
Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluetooth
Removed /etc/systemd/system/bluetooth.target.wants/bluetooth.service.
Removed /etc/systemd/system/dbus-org.bluez.service.
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth.service
Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluetooth
a37@a37-tecnoilligent:~$ systemctl is-enabled systemd-oomd
disabled
a37@a37-tecnoilligent:~$ systemctl mask systemd-oomd
Created symlink /etc/systemd/system/systemd-oomd.service → /dev/null.
a37@a37-tecnoilligent:~$ systemctl is-enabled systemd-oomd
masked
a37@a37-tecnoilligent:~$ journalctl -fo cat /usr/bin/gnome-shell
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Can't update stage views actor <dashtodockContainer>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock>:0x562a1a4f13d0] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashSlideContainer>:0x562a1b6e8890] is on because it needs an allocation.
Can't update stage views actor <dashtodockBox>[<StBoxLayout>:0x562a1ebc1fb0] is on because it needs an allocation.
Can't update stage views actor <dash>[<Gjs_ubuntu-dock_ubuntu_com_dash_DockDash>:0x562a1a9ee690] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashContainer>[<StBoxLayout>:0x562a1a11e770] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashScrollview>[<StScrollView>:0x562a1b3cdc10] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220085a
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200bd7
Can't update stage views actor <dashtodockContainer>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock>:0x562a1a4f13d0] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashSlideContainer>:0x562a1b6e8890] is on because it needs an allocation.
Can't update stage views actor <dashtodockBox>[<StBoxLayout>:0x562a1ebc1fb0] ...

37@a37-tecnoilligent:~$ sudo systemctl disable bluemon.service
bluemon.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluemon
a37@a37-tecnoilligent:~$ sudo systemctl disable bluemon
bluemon.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluemon
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth\x2c.service
Failed to disable unit: Unit file bluetoothx2c.service does not exist.
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth\x2c
Failed to disable unit: Unit file bluetoothx2c.service does not exist.
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth
Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluetooth
Removed /etc/systemd/system/bluetooth.target.wants/bluetooth.service.
Removed /etc/systemd/system/dbus-org.bluez.service.
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth.service
Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluetooth
a37@a37-tecnoilligent:~$ systemctl is-enabled systemd-oomd
disabled
a37@a37-tecnoilligent:~$ systemctl mask systemd-oomd
Created symlink /etc/systemd/system/systemd-oomd.service → /dev/null.
a37@a37-tecnoilligent:~$ systemctl is-enabled systemd-oomd
masked
a37@a37-tecnoilligent:~$ journalctl -fo cat /usr/bin/gnome-shell
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Can't update stage views actor <dashtodockContainer>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock>:0x562a1a4f13d0] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashSlideContainer>:0x562a1b6e8890] is on because it needs an allocation.
Can't update stage views actor <dashtodockBox>[<StBoxLayout>:0x562a1ebc1fb0] is on because it needs an allocation.
Can't update stage views actor <dash>[<Gjs_ubuntu-dock_ubuntu_com_dash_DockDash>:0x562a1a9ee690] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashContainer>[<StBoxLayout>:0x562a1a11e770] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashScrollview>[<StScrollView>:0x562a1b3cdc10] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220085a
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200bd7
Can't update stage views actor <dashtodockContainer>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock>:0x562a1a4f13d0] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashSlideContainer>:0x562a1b6e8890] is on because it needs an allocation.
Can't update stage views actor <dashtodockBox>[<StBoxLayout>:0x562a1ebc1fb0] is on because it needs an allocation.
Can't update stage views actor <dash>[<Gjs_ubuntu-dock_ubuntu_com_dash_DockDash>:0x562a1a9ee690] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashContainer>[<StBoxLayout>:0x562a1a11e770] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashScrollview>[<StScrollView>:0x562a1b3cdc10] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Can't update stage views actor <dashtodockContainer>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock>:0x562a1a4f13d0] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashSlideContainer>:0x562a1b6e8890] is on because it needs an allocation.
Can't update stage views actor <dashtodockBox>[<StBoxLayout>:0x562a1ebc1fb0] is on because it needs an allocation.
Can't update stage views actor <dash>[<Gjs_ubuntu-dock_ubuntu_com_dash_DockDash>:0x562a1a9ee690] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashContainer>[<StBoxLayout>:0x562a1a11e770] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashScrollview>[<StScrollView>:0x562a1b3cdc10] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Window manager warning: last_user_time (17053113) is greater than comparison timestamp (17053106).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Window manager warning: 0x1800052 appears to be one of the offending windows with a timestamp of 17053113.  Working around...

xprop -id 0xa0000e | grep _NET_WM_PID

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  21 (X_ListProperties)
  Resource id in failed request:  0xa0000e
  Serial number of failed request:  12
  Current serial number in output stream:  12
a37@a37-tecnoilligent:~$ xprop -id 0xa0000e | grep _NET_WM_PID

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  21 (X_ListProperties)
  Resource id in failed request:  0xa0000e
  Serial number of failed request:  12
  Current serial number in output stream:  12
a37@a37-tecnoilligent:~$ xwininfo -id 0xa0000e

X Error: 9: Bad Drawable: 0xa0000e
  Request Major code: 14
  Request serial number: 3
xwininfo: error: No such window with id 0xa0000e.
a37@a37-tecnoilligent:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.3 LTS
Release:	22.04
Codename:	jammy
a37@a37-tecnoilligent:~$ xwininfo -id 0x220085a
X Error: 9: Bad Drawable: 0x220085a
  Request Major code: 14
  Request serial number: 3
xwininfo: error: No such window with id 0x220085a.
a37@a37-tecnoilligent:~$ xwininfo -id 0x220085a
X Error: 9: Bad Drawable: 0x220085a
  Request Major code: 14
  Request serial number: 3
xwininfo: error: No such window with id 0x220085a.
a37@a37-tecnoilligent:~$ xprop -id 0x220085a | grep _NET_WM_PID
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  21 (X_ListProperties)
  Resource id in failed request:  0x220085a
  Serial number of failed request:  12
  Current serial number in output stream:  12
a37@a37-tecnoilligent:~$ xprop -id 0x2200bd7 | grep _NET_WM_PID
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  21 (X_ListProperties)
  Resource id in failed request:  0x2200bd7
  Serial number of failed request:  12
  Current serial number in output stream:  12
a37@a37-tecnoilligent:~$

Revision history for this message

Jorge PAB (jorge4llright) wrote on 2023-12-25:

#8

Download full text (20.6 KiB)

sudo ls /usr/share/gnome-shell/extensions/
<email address hidden> <email address hidden> <email address hidden>
<email address hidden> <email address hidden> <email address hidden>
<email address hidden> <email address hidden> <email address hidden>
<email address hidden> <email address hidden>
<email address hidden> <email address hidden>
a37@a37-tecnoilligent:~$ sudo systemctl disable blueman-mechanism.service
[sudo] password for a37:
Removed /etc/systemd/system/multi-user.target.wants/blueman-mechanism.service.
^[[Aa37@a37-tecnoilligent:~$ sudo systemctl disable blueman-mechanism
a37@a37-tecnoilligent:~$ sudo systemctl disable bluemon.service
bluemon.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluemon
a37@a37-tecnoilligent:~$ sudo systemctl disable bluemon
bluemon.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluemon
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth\x2c.service
Failed to disable unit: Unit file bluetoothx2c.service does not exist.
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth\x2c
Failed to disable unit: Unit file bluetoothx2c.service does not exist.
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth
Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluetooth
Removed /etc/systemd/system/bluetooth.target.wants/bluetooth.service.
Removed /etc/systemd/system/dbus-org.bluez.service.
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth.service
Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluetooth
a37@a37-tecnoilligent:~$ systemctl is-enabled systemd-oomd
disabled
a37@a37-tecnoilligent:~$ systemctl mask systemd-oomd
Created symlink /etc/systemd/system/systemd-oomd.service → /dev/null.
a37@a37-tecnoilligent:~$ systemctl is-enabled systemd-oomd
masked
a37@a37-tecnoilligent:~$ journalctl -fo cat /usr/bin/gnome-shell
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Can't update stage views actor <dashtodockContainer>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock>:0x562a1a4f13d0] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashSlideContainer>:0x562a1b6e8890] is on because it needs an allocation.
Can't update stage views actor <dashtodockBox>[<StBoxLayout>:0x562a1ebc1fb0] is on because it needs an allocation.
Can't update stage views actor <dash>[<Gjs_ubuntu-dock_ubuntu_com_dash_Do...

sudo ls /usr/share/gnome-shell/extensions/
apps-menu@gnome-shell-extensions.gcampax.github.com		   places-menu@gnome-shell-extensions.gcampax.github.com	      window-list@gnome-shell-extensions.gcampax.github.com
auto-move-windows@gnome-shell-extensions.gcampax.github.com	   screenshot-window-sizer@gnome-shell-extensions.gcampax.github.com  windowsNavigator@gnome-shell-extensions.gcampax.github.com
drive-menu@gnome-shell-extensions.gcampax.github.com		   ubuntu-appindicators@ubuntu.com				      workspace-indicator@gnome-shell-extensions.gcampax.github.com
launch-new-instance@gnome-shell-extensions.gcampax.github.com	   ubuntu-dock@ubuntu.com
native-window-placement@gnome-shell-extensions.gcampax.github.com  user-theme@gnome-shell-extensions.gcampax.github.com
a37@a37-tecnoilligent:~$ sudo systemctl disable blueman-mechanism.service
[sudo] password for a37: 
Removed /etc/systemd/system/multi-user.target.wants/blueman-mechanism.service.
^[[Aa37@a37-tecnoilligent:~$ sudo systemctl disable blueman-mechanism
a37@a37-tecnoilligent:~$ sudo systemctl disable bluemon.service
bluemon.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluemon
a37@a37-tecnoilligent:~$ sudo systemctl disable bluemon
bluemon.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluemon
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth\x2c.service
Failed to disable unit: Unit file bluetoothx2c.service does not exist.
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth\x2c
Failed to disable unit: Unit file bluetoothx2c.service does not exist.
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth
Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluetooth
Removed /etc/systemd/system/bluetooth.target.wants/bluetooth.service.
Removed /etc/systemd/system/dbus-org.bluez.service.
a37@a37-tecnoilligent:~$ sudo systemctl disable bluetooth.service
Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable bluetooth
a37@a37-tecnoilligent:~$ systemctl is-enabled systemd-oomd
disabled
a37@a37-tecnoilligent:~$ systemctl mask systemd-oomd
Created symlink /etc/systemd/system/systemd-oomd.service → /dev/null.
a37@a37-tecnoilligent:~$ systemctl is-enabled systemd-oomd
masked
a37@a37-tecnoilligent:~$ journalctl -fo cat /usr/bin/gnome-shell
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Can't update stage views actor <dashtodockContainer>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock>:0x562a1a4f13d0] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashSlideContainer>:0x562a1b6e8890] is on because it needs an allocation.
Can't update stage views actor <dashtodockBox>[<StBoxLayout>:0x562a1ebc1fb0] is on because it needs an allocation.
Can't update stage views actor <dash>[<Gjs_ubuntu-dock_ubuntu_com_dash_DockDash>:0x562a1a9ee690] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashContainer>[<StBoxLayout>:0x562a1a11e770] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashScrollview>[<StScrollView>:0x562a1b3cdc10] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220085a
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200bd7
Can't update stage views actor <dashtodockContainer>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock>:0x562a1a4f13d0] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashSlideContainer>:0x562a1b6e8890] is on because it needs an allocation.
Can't update stage views actor <dashtodockBox>[<StBoxLayout>:0x562a1ebc1fb0] is on because it needs an allocation.
Can't update stage views actor <dash>[<Gjs_ubuntu-dock_ubuntu_com_dash_DockDash>:0x562a1a9ee690] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashContainer>[<StBoxLayout>:0x562a1a11e770] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashScrollview>[<StScrollView>:0x562a1b3cdc10] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Can't update stage views actor <dashtodockContainer>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock>:0x562a1a4f13d0] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashSlideContainer>:0x562a1b6e8890] is on because it needs an allocation.
Can't update stage views actor <dashtodockBox>[<StBoxLayout>:0x562a1ebc1fb0] is on because it needs an allocation.
Can't update stage views actor <dash>[<Gjs_ubuntu-dock_ubuntu_com_dash_DockDash>:0x562a1a9ee690] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashContainer>[<StBoxLayout>:0x562a1a11e770] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashScrollview>[<StScrollView>:0x562a1b3cdc10] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Window manager warning: last_user_time (17053113) is greater than comparison timestamp (17053106).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Window manager warning: 0x1800052 appears to be one of the offending windows with a timestamp of 17053113.  Working around...
Window manager warning: Ping serial 18162683 was reused for window 0x1800052, previous use was for window W21.
Window manager warning: Ping serial 18898857 was reused for window W126, previous use was for window 0x1800052.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220762b

999999999999999999999999999999999999999999999999999999999999999999999999999999999

gnome-extensions list --enabled
ding@rastersoft.com
ubuntu-appindicators@ubuntu.com
ubuntu-dock@ubuntu.com
a37@a37-tecnoilligent:~$ ps auxw | grep gnome
a37         6471  0.0  0.0 238416  7088 ?        Sl   10:06   0:00 /usr/bin/gnome-keyring-daemon --daemonize --login
a37         6521  0.0  0.0 159748  5632 tty2     Ssl+ 10:06   0:00 /usr/libexec/gdm-wayland-session env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --session=ubuntu
a37         6529  0.0  0.0 220400 11392 tty2     Sl+  10:06   0:00 /usr/libexec/gnome-session-binary --session=ubuntu
a37         6661  0.0  0.0  89268  5632 ?        Ssl  10:06   0:00 /usr/libexec/gnome-session-ctl --monitor
a37         6672  0.0  0.0 591168 13184 ?        Ssl  10:06   0:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu
a37         6735  4.8  2.2 6769836 367488 ?      RLsl 10:06  11:58 /usr/bin/gnome-shell
a37         7159  0.0  0.0 583344 14208 ?        Sl   10:07   0:00 /usr/libexec/gnome-shell-calendar-server
a37         7253  0.0  0.1 2871360 20188 ?       Sl   10:07   0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Notifications
a37         7255  0.0  0.0 162680  6912 ?        Sl   10:07   0:00 /usr/libexec/at-spi2-registryd --use-gnome-session
a37         7751  0.0  0.7 1521440 114976 ?      Ssl  10:07   0:01 /usr/libexec/xdg-desktop-portal-gnome
a37         7864  0.0  0.1 2871324 18716 ?       Sl   10:07   0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.ScreenSaver
a37       126572  0.0  0.2 890968 36144 ?        Sl   10:51   0:00 /usr/bin/gnome-calendar --gapplication-service
a37       126605  0.0  0.1  35244 17628 ?        Ss   10:51   0:00 python3 /usr/lib/gnome-pass-search-provider/gnome-pass-search-provider.py
a37       482328  0.4  0.3 829972 55176 ?        Ssl  13:13   0:16 /usr/libexec/gnome-terminal-server
root      497165  0.0  0.4 1030452 74820 ?       Sl   13:19   0:01 /usr/libexec/xdg-desktop-portal-gnome
root      497305  0.0  0.0 238220  8704 ?        Sl   13:19   0:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
a37       623014  0.0  0.0   2888  1536 ?        Ss   14:04   0:00 sh -c /usr/bin/gnome-software --gapplication-service
a37       623017  0.5  0.6 659152 103928 ?       Sl   14:04   0:02 /usr/bin/gnome-software --gapplication-service
a37       649640  0.0  0.0   6556  2432 pts/0    S+   14:11   0:00 grep --color=auto gnome
a37@a37-tecnoilligent:~$ ps auxw | grep gjs
a37         7253  0.0  0.1 2871360 20188 ?       Sl   10:07   0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Shell.Notifications
a37         7864  0.0  0.1 2871324 18716 ?       Sl   10:07   0:00 /usr/bin/gjs /usr/share/gnome-shell/org.gnome.ScreenSaver
a37       651683  0.0  0.0   6556  2432 pts/0    S+   14:11   0:00 grep --color=auto gjs
a37@a37-tecnoilligent:~$ ps auxw | grep gdm
root        2772  0.0  0.0 238672  8064 ?        Ssl  10:06   0:00 /usr/sbin/gdm3
root        6213  0.0  0.0 322204 11692 ?        Sl   10:06   0:00 gdm-session-worker [pam/gdm-password]
a37         6521  0.0  0.0 159748  5632 tty2     Ssl+ 10:06   0:00 /usr/libexec/gdm-wayland-session env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --session=ubuntu
a37       652022  0.0  0.0   6556  2432 pts/0    S+   14:12   0:00 grep --color=auto gdm
a37@a37-tecnoilligent:~$ Monitors
Monitors: command not found
a37@a37-tecnoilligent:~$ Monitor
Command 'Monitor' not found, did you mean:
  command 'monitor' from deb dmucs (0.6.1-3build1)
Try: sudo apt install <deb name>
a37@a37-tecnoilligent:~$ systemctl disable --now systemd-oomd
Removed /etc/systemd/system/multi-user.target.wants/systemd-oomd.service.
Removed /etc/systemd/system/dbus-org.freedesktop.oom1.service.
a37@a37-tecnoilligent:~$ systemctl disable --now systemd-oomd
a37@a37-tecnoilligent:~$ systemctl is-enabled systemd-oomd
disabled
a37@a37-tecnoilligent:~$ sudo systemctl is-enabled systemd-oomd
disabled
a37@a37-tecnoilligent:~$ sudo systemctl list
Unknown command verb list.
a37@a37-tecnoilligent:~$ sudo systemctl show
Version=249.11-0ubuntu3.11
Features=+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCOD>
Architecture=x86-64
FirmwareTimestamp=n/a
FirmwareTimestampMonotonic=0
LoaderTimestamp=n/a
LoaderTimestampMonotonic=0
KernelTimestamp=Mon 2023-12-25 10:06:14 EST
KernelTimestampMonotonic=0
InitRDTimestamp=n/a
InitRDTimestampMonotonic=0
UserspaceTimestamp=Mon 2023-12-25 10:06:18 EST
UserspaceTimestampMonotonic=4642126
FinishTimestamp=Mon 2023-12-25 10:06:51 EST
FinishTimestampMonotonic=36854529
SecurityStartTimestamp=Mon 2023-12-25 10:06:18 EST
SecurityStartTimestampMonotonic=4666357
SecurityFinishTimestamp=Mon 2023-12-25 10:06:18 EST
SecurityFinishTimestampMonotonic=4673006
GeneratorsStartTimestamp=Mon 2023-12-25 10:06:19 EST
GeneratorsStartTimestampMonotonic=4981035
GeneratorsFinishTimestamp=Mon 2023-12-25 10:06:21 EST
GeneratorsFinishTimestampMonotonic=7633925
UnitsLoadStartTimestamp=Mon 2023-12-25 10:06:21 EST
UnitsLoadStartTimestampMonotonic=7633928
UnitsLoadFinishTimestamp=Mon 2023-12-25 10:06:22 EST
UnitsLoadFinishTimestampMonotonic=7944579
InitRDSecurityStartTimestamp=n/a
InitRDSecurityStartTimestampMonotonic=0
InitRDSecurityFinishTimestamp=n/a
InitRDSecurityFinishTimestampMonotonic=0
InitRDGeneratorsStartTimestamp=n/a
InitRDGeneratorsStartTimestampMonotonic=0
InitRDGeneratorsFinishTimestamp=n/a
InitRDGeneratorsFinishTimestampMonotonic=0
InitRDUnitsLoadStartTimestamp=n/a
InitRDUnitsLoadStartTimestampMonotonic=0
InitRDUnitsLoadFinishTimestamp=n/a
InitRDUnitsLoadFinishTimestampMonotonic=0
LogLevel=info
LogTarget=journal-or-kmsg
NNames=736
NFailedUnits=9
NJobs=1
NInstalledJobs=2469
NFailedJobs=775
Progress=1
Environment=LANG=en_US.UTF-8 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin XDG_DATA_DIRS=/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/
ConfirmSpawn=no
ShowStatus=no
UnitPath=/etc/systemd/system.control /run/systemd/system.control /run/systemd/transient /run/systemd/generator.early /etc/systemd/system /etc/systemd/system.attached /run/systemd/system /run/systemd/syst>
DefaultStandardOutput=journal
Version=249.11-0ubuntu3.11
Features=+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCOD>
Architecture=x86-64
FirmwareTimestamp=n/a
FirmwareTimestampMonotonic=0
LoaderTimestamp=n/a
LoaderTimestampMonotonic=0
KernelTimestamp=Mon 2023-12-25 10:06:14 EST
KernelTimestampMonotonic=0
InitRDTimestamp=n/a
InitRDTimestampMonotonic=0
UserspaceTimestamp=Mon 2023-12-25 10:06:18 EST
UserspaceTimestampMonotonic=4642126
FinishTimestamp=Mon 2023-12-25 10:06:51 EST
FinishTimestampMonotonic=36854529
SecurityStartTimestamp=Mon 2023-12-25 10:06:18 EST
SecurityStartTimestampMonotonic=4666357
SecurityFinishTimestamp=Mon 2023-12-25 10:06:18 EST
SecurityFinishTimestampMonotonic=4673006
GeneratorsStartTimestamp=Mon 2023-12-25 10:06:19 EST
GeneratorsStartTimestampMonotonic=4981035
GeneratorsFinishTimestamp=Mon 2023-12-25 10:06:21 EST
GeneratorsFinishTimestampMonotonic=7633925
UnitsLoadStartTimestamp=Mon 2023-12-25 10:06:21 EST
UnitsLoadStartTimestampMonotonic=7633928
UnitsLoadFinishTimestamp=Mon 2023-12-25 10:06:22 EST
UnitsLoadFinishTimestampMonotonic=7944579
InitRDSecurityStartTimestamp=n/a
InitRDSecurityStartTimestampMonotonic=0
InitRDSecurityFinishTimestamp=n/a
InitRDSecurityFinishTimestampMonotonic=0
InitRDGeneratorsStartTimestamp=n/a
InitRDGeneratorsStartTimestampMonotonic=0
InitRDGeneratorsFinishTimestamp=n/a
InitRDGeneratorsFinishTimestampMonotonic=0
InitRDUnitsLoadStartTimestamp=n/a
InitRDUnitsLoadStartTimestampMonotonic=0
InitRDUnitsLoadFinishTimestamp=n/a
InitRDUnitsLoadFinishTimestampMonotonic=0
LogLevel=info
LogTarget=journal-or-kmsg
NNames=736
NFailedUnits=9
NJobs=1
NInstalledJobs=2469
NFailedJobs=775
Progress=1
Environment=LANG=en_US.UTF-8 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin XDG_DATA_DIRS=/var/lib/flatpak/exports/share:/usr/local/share/:/usr/share/
ConfirmSpawn=no
ShowStatus=no
UnitPath=/etc/systemd/system.control /run/systemd/system.control /run/systemd/transient /run/systemd/generator.early /etc/systemd/system /etc/systemd/system.attached /run/systemd/system /run/systemd/syst>
DefaultStandardOutput=journal
DefaultStandardError=inherit
Features=+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCOD>
Architecture=x86-64
FirmwareTimestamp=n/a

888888888888888888888888888888888888888888888888888888888888888888888888888

xprop -id 0xa0000e | grep _NET_WM_PID

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  21 (X_ListProperties)
  Resource id in failed request:  0xa0000e
  Serial number of failed request:  12
  Current serial number in output stream:  12
a37@a37-tecnoilligent:~$ xprop -id 0xa0000e | grep _NET_WM_PID

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  21 (X_ListProperties)
  Resource id in failed request:  0xa0000e
  Serial number of failed request:  12
  Current serial number in output stream:  12
a37@a37-tecnoilligent:~$ xwininfo -id 0xa0000e

X Error: 9: Bad Drawable: 0xa0000e
  Request Major code: 14
  Request serial number: 3
xwininfo: error: No such window with id 0xa0000e.
a37@a37-tecnoilligent:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.3 LTS
Release:	22.04
Codename:	jammy
a37@a37-tecnoilligent:~$ xwininfo -id 0x220085a
X Error: 9: Bad Drawable: 0x220085a
  Request Major code: 14
  Request serial number: 3
xwininfo: error: No such window with id 0x220085a.
a37@a37-tecnoilligent:~$ xwininfo -id 0x220085a
X Error: 9: Bad Drawable: 0x220085a
  Request Major code: 14
  Request serial number: 3
xwininfo: error: No such window with id 0x220085a.
a37@a37-tecnoilligent:~$ xprop -id 0x220085a | grep _NET_WM_PID
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  21 (X_ListProperties)
  Resource id in failed request:  0x220085a
  Serial number of failed request:  12
  Current serial number in output stream:  12
a37@a37-tecnoilligent:~$ xprop -id 0x2200bd7 | grep _NET_WM_PID
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  21 (X_ListProperties)
  Resource id in failed request:  0x2200bd7
  Serial number of failed request:  12
  Current serial number in output stream:  12

888888888888888888888888888888888888888888888888888888888888888

journalctl -fo cat /usr/bin/gnome-shell
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Can't update stage views actor <dashtodockContainer>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock>:0x562a1a4f13d0] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashSlideContainer>:0x562a1b6e8890] is on because it needs an allocation.
Can't update stage views actor <dashtodockBox>[<StBoxLayout>:0x562a1ebc1fb0] is on because it needs an allocation.
Can't update stage views actor <dash>[<Gjs_ubuntu-dock_ubuntu_com_dash_DockDash>:0x562a1a9ee690] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashContainer>[<StBoxLayout>:0x562a1a11e770] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashScrollview>[<StScrollView>:0x562a1b3cdc10] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220085a
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200bd7
Can't update stage views actor <dashtodockContainer>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock>:0x562a1a4f13d0] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashSlideContainer>:0x562a1b6e8890] is on because it needs an allocation.
Can't update stage views actor <dashtodockBox>[<StBoxLayout>:0x562a1ebc1fb0] is on because it needs an allocation.
Can't update stage views actor <dash>[<Gjs_ubuntu-dock_ubuntu_com_dash_DockDash>:0x562a1a9ee690] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashContainer>[<StBoxLayout>:0x562a1a11e770] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashScrollview>[<StScrollView>:0x562a1b3cdc10] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Can't update stage views actor <dashtodockContainer>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashToDock>:0x562a1a4f13d0] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<Gjs_ubuntu-dock_ubuntu_com_docking_DashSlideContainer>:0x562a1b6e8890] is on because it needs an allocation.
Can't update stage views actor <dashtodockBox>[<StBoxLayout>:0x562a1ebc1fb0] is on because it needs an allocation.
Can't update stage views actor <dash>[<Gjs_ubuntu-dock_ubuntu_com_dash_DockDash>:0x562a1a9ee690] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashContainer>[<StBoxLayout>:0x562a1a11e770] is on because it needs an allocation.
Can't update stage views actor <dashtodockDashScrollview>[<StScrollView>:0x562a1b3cdc10] is on because it needs an allocation.
Can't update stage views actor <unnamed>[<StBoxLayout>:0x562a187e2c20] is on because it needs an allocation.
Window manager warning: last_user_time (17053113) is greater than comparison timestamp (17053106).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...
Window manager warning: 0x1800052 appears to be one of the offending windows with a timestamp of 17053113.  Working around...
Window manager warning: Ping serial 18162683 was reused for window 0x1800052, previous use was for window W21.
Window manager warning: Ping serial 18898857 was reused for window W126, previous use was for window 0x1800052.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x220762b

Ubuntu
guake package

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntuguake package

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
guake package