Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#17901 - [xf86-input-evdev] 2.3.2-1 loss of mouse buttons after 1-2 hours

Attached to Project: Arch Linux
Opened by Zalaad (zalaad) - Tuesday, 19 January 2010, 11:28 GMT
Last edited by Jan de Groot (JGC) - Thursday, 10 March 2011, 19:58 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: since the upgrade to xf86-input-evdev 2.3.2-1, after 1 or 2 hours, I loss my mouse buttons (all of them), but not the cursor, I can still move it, but without clicking. I can't see anything in the logs. I had to downgrade to xf86-input-evdev 2.3.1-1. I'm using KDE 4.3.4-1, with twin screens. radeon driver, on AMD64.


Additional info:
* package version(s) xf86-input-evdev 2.3.2-1
* config and/or log files etc.

xorg.conf :

Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "EvdevMouse" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "EvdevMouse"
Driver "evdev"
Option "Name" "Logitech USB RECEIVER"
Option "evBits" "+1-2"
Option "keyBits" "~272-287"
Option "relBits" "~0-2 ~6 ~8"
Option "Pass" "3"
Option "CorePointer"
EndSection




Steps to reproduce:
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 10 March 2011, 19:58 GMT
Reason for closing:  No response
Comment by Paul Mattal (paul) - Thursday, 25 February 2010, 13:04 GMT
I've got a similar issue, also with a Logitech wireless USB mouse; just downgraded to xf86-input-evdev 2.3.1-1 to see if it stabilizes. So far, so good.
Comment by Paul Mattal (paul) - Tuesday, 02 March 2010, 12:32 GMT
This definitely did it; it was xf86-input-evdev 2.3.2 causing the trouble. Stable now since this post.
Comment by Paul Mattal (paul) - Friday, 05 March 2010, 13:19 GMT
In case someone gets time to follow this before I do, here's the 2.3 branch of the driver in git. It looks like just 4 possible commits that could have broken it:

http://cgit.freedesktop.org/xorg/driver/xf86-input-evdev/log/?h=evdev-2.3-branch
Comment by Paul Mattal (paul) - Sunday, 07 March 2010, 20:57 GMT
This might be more complicated. I just upgraded xorg-server (1.7.5-1 -> 1.7.5.901-1) and this seems to break the behavior similarly to when I use xf86-input-evdev 2.3.2.

My suspicion is that these are both triggering a symptom of something more fundamental that's wrong.
Comment by Jan de Groot (JGC) - Sunday, 07 March 2010, 22:12 GMT
Please do some git bisection to find the commit that causes this bug. I can't reproduce the problem and won't take any action unless people start helping out.
Comment by Paul Mattal (paul) - Monday, 15 March 2010, 02:40 GMT
I don't think I can reproduce this, either. Also, it would appear my bug is related to xorg-server, and not to this.

Zalaad, is this still a problem for you with 2.3.2-1?

Also, what graphics card/chipset are you using?
Comment by Thomas Dziedzic (tomd123) - Monday, 28 June 2010, 20:52 GMT
status?

Loading...