You are not logged in.
Hello everyone, I'm new here, didn't really need the forums before this.
I'm having an issue where when i click on the mouse it acts as if the click is held indefinitely until there is movement from the mouse. Makes the whole system extremely sluggish and often drags items when i meant to just click. Quite frustrating.
Nothing in my configuration has changed, Nothing about my mouse or other input devices have changed, i update the whole system regularly.
Running latest KDE plasma on wayland, AMD 6000 series GPU (underclocked but reverting to default doesnt fix it.)
A quick preliminary peek in journalctl shows thousands of endlessly spammed lines of
floorp[1545]: console.warn: "This Event is registered in System: [object KeyboardEvent]"but this seems to be unrelated since turning off floorp (my browser) doesnt help.
Tried looking online but i couldn't find anything or anyone with a similar issue.
Last edited by Abstract445 (2025-07-12 19:56:41)
Offline
First: check whether the release is delayed in "sudo libinput debug-events"
If yes, also check "sudo evtest".
If yes, it's a likely hardware problem.
If not, test whether the same happens in KDE/X11
If so:
xev -event mouse click, move, post the output.
If not, check whether https://man.archlinux.org/man/wev.1 registers anything in wayland - and what (the meaning of this is limited because of the messy wayland situation where nothing is really compatible with anything else…)
Offline
If yes, also check "sudo evtest".
If yes, it's a likely hardware problem.
Yes to both; however strangely enough, instead of delayed events as i initially thought, all events appear to be shifted forward by one, meaning that the click down even registers as a whatever event was meant to come before it, and the release registers after there is are more events after. Its like events are being held up in a buffer of some sort.
Thanks for the help.
Unless there are any other ideas ill chalk this up to incredibly sloppy mouse firmware (even tho i haven't updated it ever and this started happening only a week ago, it's still possible considering the mouse isn't a from a established brand. ¯\_(ツ)_/¯) and mark thread as answered.
Offline
What kind of rodent is this? Programmable? Does it use some obscsure mouse driver module or is this just usbhid?
(This could still be a kernel related bug, try the LTS kernel or a kernel downgrade to eg. the last 6.14 kernel)
Offline
Tired LTS kernel, no dice.
Its the rodent is a LA-1, failed project from lethal.gg, Chinese factory cloned their desgin so they canned the project and dumped the stock for really cheap.
It's got some windows exclusive proprietary garbage configuration software or whatever but all the configuration i want can be done with buttons so i never even bothered, plugged in the wireless dongle and it just works fine under what i assume to be regular usbhid.
I guess ill try spinning up a windows machine and updating the firmware.
Offline