[Bug 1198530] New: Mouse Pointer flicker and artifacts
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1198530 Bug ID: 1198530 Summary: Mouse Pointer flicker and artifacts Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Minor Priority: P5 - None Component: GNOME Assignee: gnome-bugs@suse.de Reporter: sjr.apd@shaw.ca QA Contact: qa-bugs@suse.de Found By: Customer Blocker: --- Using Leap 15.4 Beta: During initial boot to login screen the mouse pointer flickers and moving it over parts of interface leaves graphic artifacts behind. Once logged into X11 Gnome the same mouse pointer flicker/artifact issue persists. Also moving some windows around has square border artifacts--I assume where the translucent shadows would normally be. The work around is log back out and back in and the issue goes away. Another method is immediately setting machine to suspend, then waking it up. The lock screen login also fixes the mouse pointer. What would be the best way to resolve this for intial boot to avoid the secondary logout and login. p.s. (I added the Wayland pattern for Gnome to try via wayland instead of x11, but don't get the choice at the login screen for X11 or Wayland GNOME. It only shows GNOME and GNOME classic) Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
![](https://seccdn.libravatar.org/avatar/a895f78a81a109471893519443e4d933.jpg?s=120&d=mm&r=g)
http://bugzilla.opensuse.org/show_bug.cgi?id=1198530 http://bugzilla.opensuse.org/show_bug.cgi?id=1198530#c1 Stephen Rose <sjr.apd@shaw.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Stephen Rose <sjr.apd@shaw.ca> --- With recent package updates Jan12 2023, this cursor buffer artifact area appears resolved. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com