You can gate it behind just the LS receiever if you alternate between wired and wireless, since the wired mode doesn’t have this bug, but it should also not hurt it, so it’s pointless IMHO.
Again, I think this should be fixed, it’s very clearly a bug, I’m just not sure where to report this bug to the maintainers.
Nice find for a more specific fix, so far blacklisting the hid_logitech_hidpp has been a success for me since doing it but that’s obviously a band-aid workaround for a bug, and also reports my mouse as a generic logitech device to the system which could maybe? cause problems in the future. Hopefully we can get someone more knowledgeable to weigh on on best procedure to where this should be reported if you haven’t managed to already, good work.
Oh my god I thought my scroll wheel was wearing out, but when plugged in it was perfectly fine.
modprobe -r hid_logitech_hidpp and power cycling my mouse fixed it, but I had to re-disable mouse acceleration in KDE because it showed up as a new device (with a keyboard?)
Seeing as this issue is marked as resolved, yet the problem generally persists and is seemingly gotten slightly worse in Kernel 7.0, I opened a new thread:
Bump to the new thread, still not resolved, fixes are not permenant, and KDE XWayland crashes when scrolling too fast now, we need a patched 6.18 kernel until someone fixes this.
