[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Multimedia keys give double presses on HP ProBook laptop



Hi.

Using: Debian Wheezy with latest updates, hardware platform: HP ProBook
4515s.

I apreciate any sugestion you might give me.

I noticed that in my window manager, Openbox, the XF86AudioRaiseVolume,
XF86AudioLowerVolume keys generate two calls to the script that I
configured. So I started to investigate by running xev.

With xev I noticed that when pressing the multimedia keys in Openbox,
there are two KeyRelease events generated:

-----
KeymapNotify event, serial 45, synthetic NO, window 0x0,
    keys:  68  0   0   0   0   0   0   0   0   0   0   0   0   0   0   8
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

KeyRelease event, serial 45, synthetic NO, window 0x1a00001,
    root 0xa7, subw 0x0, time 5748545, (-486,454), root:(674,476),
    state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume),
same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

FocusOut event, serial 45, synthetic NO, window 0x1a00001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 45, synthetic NO, window 0x1a00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 45, synthetic NO, window 0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   8
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

KeyRelease event, serial 45, synthetic NO, window 0x1a00001,
    root 0xa7, subw 0x0, time 5748589, (-486,454), root:(674,476),
    state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume),
same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False
-----

I also started X only with an xterm window just to make sure it's not
Openbox's fault (notice the time, I couldn't have pressed the key so fast):

-----
KeyPress event, serial 18, synthetic NO, window 0xa7,
    root 0xa7, subw 0x40000c, time 3739894, (808,463), root:(808,463),
    state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume),
same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 21, synthetic NO, window 0xa7,
    root 0xa7, subw 0x40000c, time 3739901, (808,463), root:(808,463),
    state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume),
same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 21, synthetic NO, window 0xa7,
    root 0xa7, subw 0x40000c, time 3739907, (808,463), root:(808,463),
    state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume),
same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 21, synthetic NO, window 0xa7,
    root 0xa7, subw 0x40000c, time 3739965, (808,463), root:(808,463),
    state 0x0, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume),
same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False
-----

At this point I'm inclining to think that it's a bug in
xserver-xorg-input-evdev, but I'm not sure that this isn't some kind of
weird issue with my laptop (generated by ACPI perhaps of just the
hardware keyboard generating spurious presses).

Here is also some interesting extract from Xorg.0.log:
-----
[  3968.127] (II) config/udev: Adding input device ACPI Virtual Keyboard
Device (/dev/input/event12)
[  3968.127] (**) ACPI Virtual Keyboard Device: Applying InputClass
"evdev keyboard catchall"
[  3968.127] (**) ACPI Virtual Keyboard Device: Applying InputClass
"keyboard-layout"
[  3968.127] (II) Using input driver 'evdev' for 'ACPI Virtual Keyboard
Device'
[  3968.127] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[  3968.127] (**) ACPI Virtual Keyboard Device: always reports core events
[  3968.127] (**) evdev: ACPI Virtual Keyboard Device: Device:
"/dev/input/event12"
[  3968.127] (--) evdev: ACPI Virtual Keyboard Device: Vendor 0 Product 0
[  3968.127] (--) evdev: ACPI Virtual Keyboard Device: Found keys
[  3968.127] (II) evdev: ACPI Virtual Keyboard Device: Configuring as
keyboard
[  3968.127] (**) Option "config_info"
"udev:/sys/devices/virtual/input/input12/event12"
[  3968.127] (II) XINPUT: Adding extended input device "ACPI Virtual
Keyboard Device" (type: KEYBOARD, id 13)
[  3968.127] (**) Option "xkb_rules" "evdev"
[  3968.127] (**) Option "xkb_model" "pc105"
[  3968.127] (**) Option "xkb_layout" "us, ro"
[  3968.127] (**) Option "xkb_variant" ",std_cedilla"
[  3968.127] (**) Option "xkb_options"
"grp:switch,grp:alt_shift_toggle,grp_led:scroll"
[  3968.128] (II) config/udev: Adding input device HP WMI hotkeys
(/dev/input/event9)
[  3968.128] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard
catchall"
[  3968.128] (**) HP WMI hotkeys: Applying InputClass "keyboard-layout"
[  3968.128] (II) Using input driver 'evdev' for 'HP WMI hotkeys'
[  3968.128] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[  3968.128] (**) HP WMI hotkeys: always reports core events
[  3968.128] (**) evdev: HP WMI hotkeys: Device: "/dev/input/event9"
[  3968.128] (--) evdev: HP WMI hotkeys: Vendor 0 Product 0
[  3968.128] (--) evdev: HP WMI hotkeys: Found keys
[  3968.128] (II) evdev: HP WMI hotkeys: Configuring as keyboard
[  3968.128] (**) Option "config_info"
"udev:/sys/devices/virtual/input/input9/event9"
[  3968.128] (II) XINPUT: Adding extended input device "HP WMI hotkeys"
(type: KEYBOARD, id 14)
[  3968.128] (**) Option "xkb_rules" "evdev"
[  3968.128] (**) Option "xkb_model" "pc105"
[  3968.128] (**) Option "xkb_layout" "us, ro"
[  3968.128] (**) Option "xkb_variant" ",std_cedilla"
[  3968.128] (**) Option "xkb_options"
"grp:switch,grp:alt_shift_toggle,grp_led:scroll"
-----

Thanks.
-- 
Adrian Fita


Reply to: