Thanks for the tips. No extensions were present,
~$ cd ~/.local/share/gnome-shell/
~/.local/share/gnome-shell$ ls -alrt
total 12
-rw-rw-r-- 1 mcra mcra 0 Oct 13 2024 update-check-46
drwx------ 25 mcra mcra 4096 Jun 9 23:26 ..
-rw-rw-r-- 1 mcra mcra 1641 Jun 9 23:37 application_state
drwx------ 2 mcra mcra 4096 Jun 9 23:37 .
It looked like apport would upload a lot of text without me having a chance to
inspect or redact it so I did the following first:
I ran `apport-cli --save /tmp/br.txt gnome-shell` and saw it generates a lot of
log noise,
then I used this to cook the noise down to unique entries.
~$ perl -ne 'next unless s{^ \[\d+\.\d+\] buttle gnome-shell\[\d+\]: }{};
s{(Gjs-WARNING \*\*:| \*\* Message:) \d+:\d+:\d+\.\d+: }{$1 T:T:T.T: };
s{^DING: \(gjs:\d+\)}{DING: (gjs:NNNNN)}; if (m{Window manager warning: .*
appears to be one of the offending windows with a timestamp of .*\. Working})
{ s{ \d+\.}{ NNNN.}; s{ 0x[0-9a-f]+}{ 0xHHHHH} } if (m{Window manager warning:
last_\w+_time .* is greater than comparison timestamp}) { for ($_,$_) {
s{\(\d+\)}{(NNNNNN)} } } if (m{Object \.Gjs_ui_messageTray_Notification \(0x.*
has been already disposed}) { s{0x[0-9a-f]+}{0xHHHHHH} } print' /tmp/br.txt
|sort|uniq -c
1 clutter_actor_set_allocation_internal: assertion '!isnan (box->x1) &&
!isnan (box->x2) && !isnan (box->y1) && !isnan (box->y2)' failed
1 ../clutter/clutter/clutter-actor.c:8692: Actor 'unnamed [StBin]' tried
to allocate a size of -2147483648.00 x -2147483648.00
1 ../clutter/clutter/clutter-actor.c:8692: Actor 'unnamed
[StDrawingArea]' tried to allocate a size of -2147483648.00 x -2147483648.00
92 clutter_timeline_set_auto_reverse: assertion 'CLUTTER_IS_TIMELINE
(timeline)' failed
92 clutter_timeline_set_repeat_count: assertion 'CLUTTER_IS_TIMELINE
(timeline)' failed
2 Cursor update failed: drmModeAtomicCommit: Invalid argument
69 DING: 0 DesktopManager()
["/usr/share/gnome-shell/extensions/[email protected]/app/desktopManager.js":264:12]
69 DING: 1 anonymous()
["/usr/share/gnome-shell/extensions/[email protected]/app/ding.js":180:25]
69 DING: 2 anonymous()
["/usr/share/gnome-shell/extensions/[email protected]/app/ding.js":197:20]
69 DING: 3 <TOP LEVEL>
["/usr/share/gnome-shell/extensions/[email protected]/app/ding.js":206:12]
70 DING: DBus interface for File-roller (org.gnome.ArchiveManager1) is now
available.
69 DING: DBus interface for Gvfs daemon (org.gtk.vfs.Metadata) is now
available.
69 DING: DBus interface for Nautilus (org.freedesktop.FileManager1) is now
available.
69 DING: DBus interface for Nautilus (org.gnome.Nautilus.FileOperations2)
is now available.
69 DING: DBus interface for Switcheroo control
(net.hadess.SwitcherooControl) is now available.
69 DING: Detected async api for thumbnails
69 DING: (gjs:NNNNN): Gjs-WARNING **: T:T:T.T: GLib.unix_signal_add has
been moved to a separate platform-specific library. Please update your code to
use GLibUnix.signal_add instead.
69 DING: GNOME nautilus 46.2
69 DING: ** Message: T:T:T.T: Connecting to
org.freedesktop.Tracker3.Miner.Files
43 Error in size change accounting.
92 g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)'
failed
92 invalid (NULL) pointer instance
1 JS ERROR: TypeError: this.actor is null
69 Launching DING process
3 libinput error: event5 - PIXA3848:01 093A:3848 Touchpad: kernel bug:
Touch jump detected and discarded.
7 meta_window_set_stack_position_no_sync: assertion
'window->stack_position >= 0' failed
2 Object .Gjs_ui_messageTray_Notification (0xHHHHHH), has been already
disposed — impossible to access it. This might be caused by the object having
been destroyed from C code using something such as destroy(), dispose(), or
remove() vfuncs.
2 Object .Gjs_ui_messageTray_Notification (0xHHHHHH), has been already
disposed — impossible to emit any signal on it. This might be caused by the
object having been destroyed from C code using something such as destroy(),
dispose(), or remove() vfuncs.
69 Received notification for window. 0 notifications remaining.
3 See
https://wayland.freedesktop.org/libinput/doc/1.25.0/touchpad-jumping-cursors.html
for details
2 Window manager warning: 0xHHHHH appears to be one of the offending
windows with a timestamp of NNNN. Working around...
15 Window manager warning: Event has no timestamp! You may be using a
broken program such as xse. Please ask the authors of that program to fix it.
2 Window manager warning: last_focus_time (NNNNNN) is greater than
comparison timestamp (NNNNNN). This most likely represents a buggy client
sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying
to work around...
3 Window manager warning: last_user_time (NNNNNN) is greater than
comparison timestamp (NNNNNN). This most likely represents a buggy client
sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying
to work around...
167 Window manager warning: Overwriting existing binding of keysym 31 with
keysym 31 (keycode a).
167 Window manager warning: Overwriting existing binding of keysym 32 with
keysym 32 (keycode b).
167 Window manager warning: Overwriting existing binding of keysym 33 with
keysym 33 (keycode c).
167 Window manager warning: Overwriting existing binding of keysym 34 with
keysym 34 (keycode d).
167 Window manager warning: Overwriting existing binding of keysym 35 with
keysym 35 (keycode e).
168 Window manager warning: Overwriting existing binding of keysym 36 with
keysym 36 (keycode f).
168 Window manager warning: Overwriting existing binding of keysym 37 with
keysym 37 (keycode 10).
168 Window manager warning: Overwriting existing binding of keysym 38 with
keysym 38 (keycode 11).
168 Window manager warning: Overwriting existing binding of keysym 39 with
keysym 39 (keycode 12).
1 Window manager warning: W1 appears to be one of the offending windows
with a timestamp of NNNN. Working around...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2113786
Title:
Dark rectangle over gnome-terminal is a ghost of a "visual alert"
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
I started getting dark rectangles obscuring my main gnome-terminal
windows when I left the session locked for a while. Description of
chasing and removing these is at
https://linux.codidact.com/posts/293718 , and the screenshot below
shows some of those rectangles after I poked their size and opacity to
better illustrate what happens.
Now I found the cause and a recipe to reproduce the bug.
1. Open a gnome-terminal (3.52.0-1ubuntu2) or xterm (390-1ubuntu3) window;
but not foot (1.16.2-2ubuntu0.1) because it does not seem to be able to alert
on terminal bell. For better confirmation: make the window a distinctive size,
not full screen.
2. In gnome-control-center go to Accessibility > Hearing > Visual Alerts.
Enable for "entire window". Bug seems not to trigger for "entire screen", but I
didn't try hard because I don't want to dig myself out of that mess.
3. Run something that generates ASCII BEL for the remainder of the test such
as `while true; do echo -ne \\a; sleep 1; done` . In my case it was the
occasional bell of an email, a random factor which made it harder to figure out
the cause.
4. Lock the screen. Bug does not trigger when screen is active. By rectangle
counting, I suspect the bug also triggers during the password unlock dialog.
5. Expected: each visual alert to be finished and gone within a second of the
BEL.
6. What you find when you unlock: a pile of semi-transparent dark rectangles
stacked on your alerting window, approximately one per BEL emitted during the
lock time. One or two might leave the text legible but dim, but more often the
window is plain black.
7. Uf necessary, or you are curious about what they are: use the Wayland
looking glass to find and delete the rectangles.
https://linux.codidact.com/posts/293718
8. Switch Visual Alerts off and be grateful that you don't really need them. 🫣
Other notes that might be relevant:
Grok advises that gnome-shell is the package providing this a11y
function, so that's why I'm offering the report here.
Grok also advises to give `journalctl /usr/bin/gnome-shell` output,
but there is nothing recent ie. since last reboot.
The opacity of these rectangles seems to vary, as if the visual alert
were progressing as usual and then got an exception which prevented it
becoming transparent and being deleted?
It seems the visual alert was incomplete and not deleted. Mouse clicks
can pass through them but the window's image is blocked or greatly
darkened.
The size of the rectangle seems to match the area flashed. This is
more obvious after watching xterm flash repeatedly.
With gnome-terminal it is possible to drag tabs out of the obscured
window to "rescue" them... if you can see or guess where the tab is.
---
Using a fairly standard Ubuntu 24.04.2 LTS Noble desktop on x86_64,
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 24.04.2 LTS
Release: 24.04
$ apt-cache policy gnome-shell
gnome-shell:
Installed: 46.0-0ubuntu6~24.04.9
Candidate: 46.0-0ubuntu6~24.04.9
Version table:
*** 46.0-0ubuntu6~24.04.9 500
500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
100 /var/lib/dpkg/status
46.0-0ubuntu6~24.04.3 500
500 http://security.ubuntu.com/ubuntu noble-security/main amd64
Packages
46.0-0ubuntu5 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
$ apt-cache policy xwayland
xwayland:
Installed: 2:23.2.6-1ubuntu0.5
Candidate: 2:23.2.6-1ubuntu0.5
Version table:
*** 2:23.2.6-1ubuntu0.5 500
500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
100 /var/lib/dpkg/status
2:23.2.6-1ubuntu0.4 500
500 http://security.ubuntu.com/ubuntu noble-security/main amd64
Packages
2:23.2.6-1 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
---
So long and thanks for all the adjectival animals!
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.7
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-10-13 (240 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64
(20240827.1)
Package: gnome-shell 46.0-0ubuntu6~24.04.9
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcVersionSignature: Ubuntu 6.11.0-26.26~24.04.1-generic 6.11.11
RelatedPackageVersions: mutter-common 46.2-1ubuntu0.24.04.8
Tags: noble wayland-session
Uname: Linux 6.11.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2113786/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
