Bug#962658: libwayland-cursor0: Cursor image left on screen after cursor moved on. Can only be removed by logging out.
Package: libwayland-cursor0
Version: 1.18.0-1
Severity: normal
Dear Maintainer,
I was editing some code in vscode, when, randomly, I though the cursor had
frozen. However I soon realised that it was elsewhere on the screen and what I
was seeing was a frozen image of it.
Despite closing vscode and switching to different workspaces on my (gnome)
desktop, the cursor remained in the same place on the screen. It seemed to
always be in the foreground - ie opening a new window over the top of where it
was would still show the cursor image, it was not displaced by the new pixels
from the overlaying window.
In the end the only way I was able to get it to disappear was to log out and
then log back in. The frozen image was removed from the screen on logout.
My computer is running a AMD graphics card (I think its a RX580) and I need to
load Linux Non Free Firmware to have a working system at all. I presume that
could be part of the issue.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.6.0-2-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libwayland-cursor0 depends on:
ii libc6 2.30-8
ii libwayland-client0 1.18.0-1
libwayland-cursor0 recommends no packages.
libwayland-cursor0 suggests no packages.
-- no debconf information
Reply to: