Bug 511117 - Mouse shows square dots as cursor theme x96 Suse Plasma Wayland Tumbleweed HP Computer may be too slow.
Summary: Mouse shows square dots as cursor theme x96 Suse Plasma Wayland Tumbleweed H...
Status: RESOLVED DUPLICATE of bug 510930
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_cursortheme (other bugs)
Version First Reported In: 6.5.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-25 19:26 UTC by Josh Zimmerman
Modified: 2025-10-25 19:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Zimmerman 2025-10-25 19:26:55 UTC
STEPS TO REPRODUCE
1. Boot up the system to the latest default 32 bit kernel 
2. Login to Plasma (Wayland)
3.  Choose cursor theme type such as get cursor windows 10.

OBSERVED RESULT
It shows me square array of dots which size varies with resolution and cursor size selected.

EXPECTED RESULT
I expected it to show me a windows 10 cursor them.

ADDITIONAL INFORMATION

I tried logging in and out; locking screen rebooting; choosing a different kernel; changijng mouse usb port, etc, but I noticed if I look at the kernel logs or I think if I recall right dmesg that it said, "Computer is too slow." even though this is an A.M.D. Athlon II x2 processor.  There is no option in the B.I.O.S. to assign more R.A.M. to the graphics adapter. 

When I take a screen-shot to submit; it records an okay normal cursor without the square dots like it never happened. I don't know if maybe it requires super user privileges to change the cursor..

I am not sure what version it was first reported in, because it still does it when I go back a kernel or 2.
Comment 1 Josh Zimmerman 2025-10-25 19:32:28 UTC
It's supposed to say x86. I have trouble seeing the screen.
Comment 2 Antonio Rojas 2025-10-25 19:39:16 UTC

*** This bug has been marked as a duplicate of bug 510930 ***