On 2020-06-11 2:27 p.m., Alan Chandler wrote: > 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.
This has nothing to do with libwayland-cursor, it's between libmutter and the amdgpu kernel driver. Basically, due to unfortunate interaction between mutter and the amdgpu kernel driver, the former can stop using the HW cursor and start drawing the cursor in software instead. But in your case, the HW cursor remains visible, in front of everything else. I submitted https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1240 to prevent something like this from happening in mutter when transitioning from monitors disabled via DPMS to enabled. However, from your description I'm not sure this will help for you as well. The fact that the HW cursor stays on is most likely an amdgpu kernel driver issue and should be reported at https://gitlab.freedesktop.org/drm/amd/-/issues . -- Earthling Michel Dänzer | https://redhat.com Libre software enthusiast | Mesa and X developer
