I’m not sure what the bug is, but this is a terrible fix. What this is doing is forcing the WindowServer to composite the cursor rather than treat it as a hardware overlay. I suppose the issue must be pretty bad for OP if this helps, but … ugh.

▲

pbmonster an hour ago | parent | next [-]

Reminds me of a fix I wrote a decade ago. My Laptop would sometimes start emitting a high frequency whine when on battery. I figured out it only happened when the CPU went into performance states lower than P2 for power saving.

So I wrote a bash script that auto-started on battery mode and then calculated a hash every few seconds. Boom, whine solved. Terrible fix, but I never measured how much battery it cost me, so it was... fine.

▲

nusl 5 hours ago | parent | prev [-]

Terrible fix but it's a fix that's minimally-invasive and addresses a bug that causes a disproportionate annoyance to the fix. I can imagine your cursor lagging is something that is extremely annoying over time.

▲

nok22kon 5 hours ago | parent [-]

linux was plagued for a long time by lagging mouse cursor

▲

koiueo 5 hours ago | parent | next [-]

I've been using Linux every day for the last 17 years, and that's the first time I'm hearing this.

I'm genuinely surprised.

The way you word it, it looks like a famous ubiquitous problem. Mind sharing any details?

	▲	jaapz 5 hours ago \| parent \| next [-]
		I've also had computers with nvidia, amd (even back when it was still ATI) and intel gpu's, at least since 2006, and can't remember ever having an issue like this. Not saying it's not an issue, but there is such an incredible amount of hardware configurations that linux supports, so it's a bit weird to say that "linux" in general has suffered a bug like this.
	▲	kiicia an hour ago \| parent \| prev \| next [-]
		not necessarily ubiquitous, but you can encounter some issues with "lagging cursor" even today, if you use standard raspbian for example > usbhid.mousepoll=0 > to /boot/cmdline.txt > This option was implemented to enforce a mouse polling rate of 62.5Hz which dramatically reduced the XWindow event system update rate in certain circumstances (oddball or "performance" mice can have update rates of 1000Hz, which is silly).
	▲	JamesMcMinn 3 hours ago \| parent \| prev \| next [-]
		There was a time when it was quite bad, especially if using Wayland and under heavy CPU or I/O loads. I think this has mostly been solved now, but I do recall getting frustrated with the switch to Wayland because of it.
	▲	5 hours ago \| parent \| prev [-]
		[deleted]

▲

functionmouse 8 minutes ago | parent | prev [-]

still does for me

whenever the CPU works hard my cursor starts to lag