[Hardy][regression] input devices (in particular Logitech mice) that require evdev to work properly are now broken

Bug #201937 reported by sibidiba
8
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: xserver-xorg-input-all

There are several input devices, in particular Logitech MX and LX series mice, which require evdev to work properly.
Without evdev some buttons do not generate input events. Also evdev was required to change the button mapping to get horizontal scrolling working. ( https://help.ubuntu.com/community/MX1000Mouse , or see bug #27421 )

Running Hardy, using X.Org 7.3 with XInputHotplug, evdev is disabled by default. If a device is listed in xorg.conf with driver evdev, it will not work, as indicated by the log file:

(...)
(EE) Configured Mouse: cannot open input pEvdev
(II) UnloadModule: "evdev"
(EE) PreInit returned NULL for "Configured Mouse"
(...)

As suggested in bug #173833 , evdev can be enabled via hal, by
$ sudo cp /usr/share/doc/hal/examples/10-x11-input.fdi /etc/hal/fdi/policy/

This indeed enables evdev devices (there were reports, that this is not always the case), but now evdev overtakes the control for all input devices. I attach my log for this case. As a result Ctrl+Alt+Backspace did not work, the given keyboard layout specified in xorg.conf was ignored. Other problems were also reported there. (No support for multiple readers for the same device etc.)
As stated in bug #42678 the InputHotplug facility should be used instead of evdev. But as mentioned, lots of input devices do no work properly this way.

For me, only evdev was able to recognize all the 12 input buttons for my LX7 USB mouse. In fact, is has only nine, but then I could set the appropriate button mapping to got all the nine real buttons including the horizontal scrolling working:
$ xinput set-button-map "`xinput list|grep Logitech|tr -d \\"|cut -f1`" 1 2 3 4 5 11 12 8 9 10 6 7

I suggest either to fix evdev and enable it's usage by default again, or make the xinputhotplug recognize all input devices properly.

Revision history for this message
sibidiba (sibidiba) wrote :
Revision history for this message
Jason Ribeiro (jrib) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 173833, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Revision history for this message
Jason Ribeiro (jrib) wrote :

I marked this as a dupe of bug 173833 because it seems to be the same issue (I'm bitten by this bug too), but the other report has more activity

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.