+- Xonotic Forums (https://forums.xonotic.org)
+-- Forum: Support (https://forums.xonotic.org/forumdisplay.php?fid=3)
+--- Forum: Xonotic - Help & Troubleshooting (https://forums.xonotic.org/forumdisplay.php?fid=4)
+--- Thread: [SOLVED] Random failures to register mouse input (/showthread.php?tid=7460)
Random failures to register mouse input - Halogene - 06-15-2017
I'm encountering random failures to register mouse input recently. It started about this week, I first thought, it would be network issues, but then I tried it locally and it happens there too.
What is happening: mouse clicks don't get registered randomly. Some times the release event doesn't register as well. At one point I even had the mouse going from continuous primary fire (left click) to secondary fire (right click) WITHOUT me even touching the mouse - I was chatting about the weird behavior! This happens a lot, especially but not exclusively in fights. Some times several clicks fail to register in a row, I think 4 or 5 clicks in a row is personal best score. Basically I don't survive an opponent encounter because I am unable to fire a single shot.
I am running Arch Linux on an intel i5 /GTX660 TI. I even did a clean install of Arch linux today and made a fresh clone of Xonotic git. The issue persists.
I tried also with a different mouse.
Now I believe this may not at all be caused by Xonotic, but is someone else maybe experiencing similar issues (even on local games)?
RE: Random failures to register mouse input - SpiKe - 06-15-2017
Hi Halogene,
I encountered the same issue on ArchLinux after Plasma 5.10 update.
If you use KDE/Plasma: disable the left touchscreen action (System Configuration -> Workspace behavior -> Touchscreen -> uncheck the left action).
Restart kwin afterwards, or simply reboot your PC.
I didn't find this solution alone, EACFreddy did.
Thanks Freddy!
Relevant KDE bug report: https://bugs.kde.org/show_bug.cgi?id=380476
RE: Random failures to register mouse input - Halogene - 06-15-2017
AWESOME.
You guys really rock. Thanks for sharing this, you made my day!
Will mark as solved when I can verify it's fixed