FS#5257 - xf86-input-evdev 1.1.2-1 fails on symlinked mouse

Attached to Project: Arch Linux
Opened by Marcel (ferkulat) - Saturday, 19 August 2006, 23:20 GMT
Last edited by Alexander Baldeck (kth5) - Wednesday, 05 September 2007, 09:34 GMT
Task Type Feature Request
Category Packages: Current
Status Closed
Assigned To Alexander Baldeck (kth5)
Architecture All
Severity Medium
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Identifier "Mouse1"
Driver "evdev"
Option "Device" "/dev/input/by-id/usb-Logitech_USB_Gaming_Mouse-event-mouse"

The lines above worked in my xorg.conf before update.

After updateting the package, I have to check on which event my mouse is bound,


Option "Device" "/dev/input/event2"

otherwise startx will exit with an error.

Since the mouse is an usb-type, the event for the mouse changes by plugging devices in different order.
This task depends upon

Closed by  Alexander Baldeck (kth5)
Wednesday, 05 September 2007, 09:34 GMT
Reason for closing:  Not a bug
Comment by Jan de Groot (JGC) - Saturday, 19 August 2006, 23:34 GMT
I'm using evdev without specifying a device at all, as stated in the example configuration in the manpage. Do you need to specify the evdev device on your system to get things working?
Comment by Marcel (ferkulat) - Saturday, 19 August 2006, 23:55 GMT
Yes, if i comment out the Device option, startx exits with:

[...]
(II) evdev brain: Rescanning devices (1).
(**) Option "CorePointer"
(**) Mouse1-isa0060/serio0/input0: Core Pointer
(**) Option "CorePointer"
(**) Mouse1-isa0060/serio3/input0: Core Pointer
(II) Mouse1-isa0060/serio3/input0: Found 4 absolute axes.
(II) Mouse1-isa0060/serio3/input0: Configuring as pointer.
(**) Mouse1-isa0060/serio3/input0: Configuring in Absolute mode.
(**) Mouse1-isa0060/serio3/input0: AbsoluteScreen: 0.
(II) Mouse1-isa0060/serio3/input0: Found 0 relative axes.
(II) Mouse1-isa0060/serio3/input0: Configuring as pointer.
(**) Mouse1-isa0060/serio3/input0: Configuring 2 relative axes.
(II) Mouse1-isa0060/serio3/input0: Found 79 mouse buttons
(II) Mouse1-isa0060/serio3/input0: Configured 79 mouse buttons
(**) Option "CorePointer"
(**) Mouse1-usb-0000:00:10.0-1/input0: Core Pointer
(II) Mouse1-usb-0000:00:10.0-1/input0: Found 4 relative axes.
(II) Mouse1-usb-0000:00:10.0-1/input0: Configuring as pointer.
(**) Mouse1-usb-0000:00:10.0-1/input0: HWHEELRelativeAxisButtons: 6 7.
(**) Mouse1-usb-0000:00:10.0-1/input0: WHEELRelativeAxisButtons: 4 5.
(II) Mouse1-usb-0000:00:10.0-1/input0: Found 16 mouse buttons
(II) Mouse1-usb-0000:00:10.0-1/input0: Configured 20 mouse buttons
(**) Option "CorePointer"
(**) Mouse1-usb-0000:00:10.0-2/input0: Core Pointer
(**) Option "CorePointer"
(**) Mouse1-usb-0000:00:10.0-2/input1: Core Pointer
(II) Mouse1-usb-0000:00:10.0-2/input1: Found 76 mouse buttons
(II) Mouse1-usb-0000:00:10.0-2/input1: Configured 76 mouse buttons
(**) Option "CorePointer"
(**) Mouse1-isa0061/input0: Core Pointer
(EE) Mouse1-isa0061/input0: Don't know how to use device.
(II) UnloadModule: "evdev"
(EE) PreInit failed for input device "Mouse1"


Comment by Paul Seropian (paranoos) - Tuesday, 05 September 2006, 19:42 GMT
freedesktop.org doesn't want you to specify devices. the device option will only accept /dev/input/event#, so you could make a symlink called event9, but there's no point. the evdev man page states that you can provide the device name (from /proc/bus/input/devices) as Option "Name" "<string>". this works quite well!

(i found out the hard way you can't do this with wacom devices, as it uses the wacom driver, not the evdev driver, even though it's accessing the event devices. wacom will let you use symlinks, though.)
Comment by Woody Gilk (Shadowhand) - Tuesday, 10 October 2006, 04:30 GMT
An update will be made to the package with a notice about this change. This isn't a bug, it's the way xorg designed it.
Comment by Johannes Jordan (FoPref) - Thursday, 08 March 2007, 16:15 GMT
There is a problem with the Xorg method, as "Name" doesn't work in every case. The Logitech MX Revolution registers two devices with the same name, one keyboard, one mouse, Xorg fails to find the right one.

Shitty design decision in my opinion.
Comment by Jan de Groot (JGC) - Thursday, 08 March 2007, 17:01 GMT
Microsoft includes Unicode characters in their product names ((R) or TM in their brand name), this makes configuration for evdev also very hard. The only way I can think of is specifying a /dev/input/event* devicenode and pin that one in udev. When the evdev scans for mouse devices and finds your keyboard also, X will bail out because it's invalid to have two corepointer devices since X.Org 7.2.
Comment by Paul Seropian (paranoos) - Thursday, 08 March 2007, 20:10 GMT
Have a look at man evdev.

You don't HAVE to use the Name, it's just the simplest for most cases I think. You can also go by vendor and product IDs, or by Phys (which matches a USB port I believe).
Comment by Johannes Jordan (FoPref) - Saturday, 12 May 2007, 13:02 GMT
Thanks for your suggestion.

Phys is the _only_ one that works for me :(
Comment by Alexander Baldeck (kth5) - Friday, 18 May 2007, 00:31 GMT
is this still an issue?
Comment by Johannes Jordan (FoPref) - Friday, 18 May 2007, 01:06 GMT
For me it is. I can use my mouse only on a fixed USB port, which is considerably _not_ how it is intended. But I guess, if this is a misconception in the design of evdev, there's not much you could do about it. The workaround (specifying the port) is a sufficient, yet annoying, workaround.

Loading...