Bug 380957 - FPS "Sticky Mouse"
Summary: FPS "Sticky Mouse"
Status: RESOLVED DUPLICATE of bug 380476
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.10.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-08 03:29 UTC by Wyatt Childers
Modified: 2017-06-17 16:12 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
mgraesslin: Wayland-
mgraesslin: X11+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wyatt Childers 2017-06-08 03:29:39 UTC
I originally opened https://bugs.kde.org/show_bug.cgi?id=380846, and hadn't done enough investigation. I orignally blamed screen corners, as I thought disabling them had fixed it.

I retested, and found a consistent way to reproduce the issue, and tested this both on the X implementation, and the Wayland implementation. I could reproduce this on the X implementation, not the Wayland implementation -- so that's a plus, at least for the future.

To reproduce the issue:
- Download xonotic: http://xonotic.org/
- Join a server and find a hit scan weapon (tested with the Machine Gun & Hagar)
- Hold down left click to start shooting and turn continously left
- Release the left mouse button

Expected behavior:
- The gun stops firing

Actual behavior:
- The gun continues to fire like you never let go of the left click button

Additional notes:
There's a similar issue with the right click button -- where it acts like it's continuing to be held down -- however, I suspect whatever is causing this for left click, is causing it for right click.

I can confirm that this has only happened for me since the update to 5.10, this did not happene before tumbleweed updated to 5.10 from 5.9.

Additional wayland note:
While Xonotic gameplay worked, after leaving Xonotic I was unable to move the mouse.
Comment 1 Wyatt Childers 2017-06-08 23:47:57 UTC
Interestingly enough, with the addition of another monitor to my computer, this seems to have resolved itself. Seems it's a single monitor only issue?
Comment 2 Wyatt Childers 2017-06-17 16:12:46 UTC
I tried disabling the touch screen support mentioned in Bug 380476, and that resolved this issue entirely. Thus, I'm going to resolve this as a duplicate. Thanks.

*** This bug has been marked as a duplicate of bug 380476 ***