|
| ▲ | 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. |
|
| ▲ | 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. |
|
| ▲ | 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). |
|
| ▲ | 5 hours ago | parent | prev [-] |
| [deleted] |
