https://bugs.kde.org/show_bug.cgi?id=483944
--- Comment #4 from Samuel García <k...@samueldgv.com> --- (In reply to Jonathan from comment #3) > Using Solaar, I cannot trigger this by locking the screen, but by restarting > the mouse or letting it go into standby mode. The issue seems to be not > exactly with the scroll speed configuration (which determines how far a > scroll event moves) but the disabled hires scrolling mode, which causes > scroll events to be emitted only about twice per revolution, True! I just tested this, and the fact that it went to standby around the same time my screen was set to lock was a coincidence. I just let the mouse idle while using the computer and indeed I was able to replicate it this way. There is nothing relevant in journalctl around the time it went on standby, although when I moved the mouse again I could only see the following in journalctl (the mouse is connected via bluetooth): Mar 19 11:40:12 mostriyo bluetoothd[1788]: Device is already marked as connected Also: In my case, I don't use Solaar/logiops at all -- You are receiving this mail because: You are watching all bug changes.