You are not logged in.

#1 2007-12-15 16:01:48

kayrune
Member
Registered: 2007-12-15
Posts: 43

Evdev kills X with mouse buttons

Hi

I'm new to Arch so please have some patience.

I have a Logitech MX3100 mouse/kbd combo (MX1000 mouse), connected via usb

I just installed Arch yesterday and to get all my mouse buttons working I tried to use evdev, now the problem is if I use evdev, X crash instantly with any mouse button click other than button1. If I don't specify the event (as documented in the wiki) the mouse doesn't work at all.

Section "InputDevice"
         Identifier      "Evdev Mouse"
         Driver          "evdev"
        Option          "device" "/dev/input/event5"
#       Option          "Name" "Logitech USB Reciever"
        Option          "SendCoreEvents" #CorePointer"
        Option          "Buttons" "12"
EndSection

This is the backtrace from log

Backtrace:
0: X(xf86SigHandler+0x7e) [0x80d9e0e]
1: [0xb7fdc420]
2: /usr/lib/xorg/modules/input//evdev_drv.so [0xb722d8bd]
3: X [0x80d9f8a]
4: X [0x80b4fb6]
5: [0xb7fdc420]
6: X(Dispatch+0x82) [0x808c602]
7: X(main+0x48b) [0x8073d5b]
8: /lib/libc.so.6(__libc_start_main+0xe0) [0xb7db7390]
9: X(FontFileCompleteXLFD+0x201) [0x80730d1]

Other interesting parts of the log:

(**) Evdev Mouse: always reports core events
(II) Evdev Mouse: Found 4 relative axes.
(II) Evdev Mouse: Configuring as pointer.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Unable to parse 'null' as a map specifier string.
(EE) Evdev Mouse: Button(null)MapTo: Button 96 already claimed.
(EE) Evdev Mouse: Unable to parse 'Button 96' as a map specifier.
(II) Evdev Mouse: Found 96 mouse buttons
(II) Evdev Mouse: Configured 96 mouse buttons.
(**) Option "CorePointer"
(**) USB Mouse: always reports core events
(II) USB Mouse: Found 4 relative axes.
(II) USB Mouse: Configuring as pointer.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Unable to parse 'null' as a map specifier string.
(EE) USB Mouse: Button(null)MapTo: Button 96 already claimed.
(EE) USB Mouse: Unable to parse 'Button 96' as a map specifier.
(II) USB Mouse: Found 96 mouse buttons
(II) USB Mouse: Configured 96 mouse buttons.
(II) evaluating device (USB Mouse)
(II) XINPUT: Adding extended input device "USB Mouse" (type: KEYBOARD)
(II) evaluating device (Evdev Mouse)
(II) XINPUT: Adding extended input device "Evdev Mouse" (type: KEYBOARD)
(II) evaluating device (Keyboard0)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(**) USB Mouse: 2 valuators.
(**) USB Mouse: Configuring in Absolute mode.
(**) USB Mouse: Registering 96 buttons.
evdev: leds are 0x0 for device 2
(II) USB Mouse: Init
(**) Evdev Mouse: 2 valuators.
(**) Evdev Mouse: Configuring in Absolute mode.
(**) Evdev Mouse: Registering 96 buttons.
evdev: leds are 0x0 for device 3
(II) Evdev Mouse: Init
(II) USB Mouse: On
(II) Evdev Mouse: On
(EE) Evdev Mouse: Unable to grab device (Device or resource busy).

Offline

#2 2007-12-15 18:47:37

Eradest
Member
From: Germany
Registered: 2007-07-18
Posts: 56

Re: Evdev kills X with mouse buttons

Hi kayrune, welcome to Arch!

Have you tried not to specify the event but the name option that you commented? Like that:

Section "InputDevice"
         Identifier      "Evdev Mouse"
         Driver          "evdev"
        Option          "Name" "Logitech USB Reciever"
        Option          "SendCoreEvents" #CorePointer"
        Option          "Buttons" "12"
EndSection

That's what works for me at least (MX 1000 as well), but "SendCoreEvents" not in the Device section, but "ServerLayout" section.

Finding 96 buttons somehow more looks like a keyboard doesn't it?

Last edited by Eradest (2007-12-15 18:49:53)

Offline

#3 2007-12-15 19:10:55

kayrune
Member
Registered: 2007-12-15
Posts: 43

Re: Evdev kills X with mouse buttons

Hi Eradest,

I guess there is some confusion since it's a mouse/kbd combo, it creates 2 events, one for the keyboard og 1 for the mouse, and the tricky part is that the one for the mouse also features some extra keyboard keys.

I tried your suggestion, but still same result, if I don't specify event, then the mouse doesn't work.
If I comment out both mouse and keyboard X autodetect it and use evdev for both it seems, however then I have the problem that X crash when I click any other mouse button than button1
I've also tried using the default keyboard setting and let X autodetect it, but it makes no difference.

This is the part of my xorg.conf

Section "ServerLayout"
        Identifier     "Xorg Configured"
        Screen      0  "Screen0" 0 0
#       InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "Mouse" "CorePointer"
#       InputDevice    "Evdev Mouse" "SendCoreEvents" #"CorePointer"
# Serial Mouse not detected
# USB Mouse not detected
EndSection
Section "InputDevice"
         Identifier      "Evdev Mouse"
         Driver          "evdev"
#       Option          "device" "/dev/input/event6"
        Option          "Name" "Logitech USB Reciever"
#       Option          "SendCoreEvents" 
        Option          "CorePointer"
        Option          "Buttons" "12"
EndSection

Last edited by kayrune (2007-12-15 19:11:41)

Offline

#4 2007-12-16 11:24:53

Eradest
Member
From: Germany
Registered: 2007-07-18
Posts: 56

Re: Evdev kills X with mouse buttons

hm... so I suppose that's one of those working with bluetooth? I got the "stand-alone" MX 1000 with some cheap noname keyboard, here's my complete xorg.conf if it helps:
http://pastebin.archlinux.org/21228 (kinda messed up, but it works wink )

Have you tried to somehow completely shut off the keyboard and only use the mouse? Or use the standard "mouse" driver in xorg?

Offline

#5 2007-12-16 13:56:04

kayrune
Member
Registered: 2007-12-15
Posts: 43

Re: Evdev kills X with mouse buttons

Eradest,

it's not a bluetooth set, just normal wireless. Your xorg.conf is fairly basic, like the wiki says, with this setup the mouse doesn't respond at all. But I have to ask you is your system up-to-date ? Because reading more about mouse and evdev problems there seems to be a problem with new versions of evdev/xserver.

as pointed out in this thread: http://bbs.archlinux.org/viewtopic.php?id=39981&p=1

unfortunatly since I have a fresh install I have noe way of installing the old evdev version, since I don't have it on my system, and the link to the pkg gives a 404

Offline

#6 2007-12-17 12:50:32

Eradest
Member
From: Germany
Registered: 2007-07-18
Posts: 56

Re: Evdev kills X with mouse buttons

I do have an up-to-date system, I also had those problems with evdev when it was updated, but, as discussed later in the thread you quoted, it was solved by an update to udev.
Have you tried using the standard "mouse" driver?

Offline

#7 2007-12-17 14:14:41

kayrune
Member
Registered: 2007-12-15
Posts: 43

Re: Evdev kills X with mouse buttons

how do you update udev?

I'm currently using the standard "mouse" driver, but then I'm missing a few buttons.

Offline

#8 2007-12-17 14:31:02

Eradest
Member
From: Germany
Registered: 2007-07-18
Posts: 56

Re: Evdev kills X with mouse buttons

udev is a normal package that should get updated as usual by doing a pacman -Syu

Offline

#9 2007-12-17 14:34:23

kayrune
Member
Registered: 2007-12-15
Posts: 43

Re: Evdev kills X with mouse buttons

but pacman says my udev is up-to-date. :S

Last edited by kayrune (2007-12-17 14:34:38)

Offline

#10 2007-12-17 15:19:07

jacko
Member
Registered: 2007-11-23
Posts: 840

Re: Evdev kills X with mouse buttons

post your whole xorg.conf here.

This is confusing to me...

Section "ServerLayout"
        Identifier     "Xorg Configured"
        Screen      0  "Screen0" 0 0
#       InputDevice    "Keyboard0" "CoreKeyboard"
        InputDevice    "Mouse" "CorePointer"
#       InputDevice    "Evdev Mouse" "SendCoreEvents" #"CorePointer"
# Serial Mouse not detected
# USB Mouse not detected
EndSection

u have the evdev commented out in the server layout section? explain what u are doing and what are trying to tell us u need help with.

Offline

#11 2007-12-17 15:23:32

jacko
Member
Registered: 2007-11-23
Posts: 840

Re: Evdev kills X with mouse buttons

I have a wireless logitech keyboard/mouse combo as well and it connects to the usb port and the ps/2 mouse port? Is yours like this or is it strictly USB?

My mouse is the mx700

Offline

#12 2007-12-17 16:30:30

kayrune
Member
Registered: 2007-12-15
Posts: 43

Re: Evdev kills X with mouse buttons

jacko,

I have ps/2 and usb, but ps/2 is not an option as it has even more limitations.

As for the xorg.conf, the reason that evdev is commented out is because I have to use default mouse driver to run X and use it. When I "test" evdev, I just comment out the default mouse, and uncomment the evdev line.

Last edited by kayrune (2007-12-17 16:31:17)

Offline

#13 2007-12-17 22:20:12

kayrune
Member
Registered: 2007-12-15
Posts: 43

Re: Evdev kills X with mouse buttons

-I just updated to xorg-server 1.4.0.90-1, still same problem with evdev sad  most mouse buttons will cause and instant kill of X

Offline

Board footer

Powered by FluxBB