with stock udev (without the rule to load micro-star keymap) and acpid
stopped, i still have two key events from xev, as said above

in that situation:
matej...@limetka:~$ sudo /lib/udev/keymap input/event5 | grep 'f[78]'
0x041 f7
0x042 f8
0x0f7 reserved
0x0f8 reserved
0x1f7 reserved
0x1f8 reserved

for the following, i'm always pressing fn+f4 (brightness down) once and
after that fn+f5 (brightness up) once.

"/lib/udev/keymap -i input/event5" gives nothing
(in non-X console, it also emits the "unknown keycode" kernel messages and a 
single "^@" - which leads me to believe that the ^@ is eaten by bash and that's 
why i don't see it after login; the kernel mesages are displayed whenever i 
press the key, not just with this command)

input/event6 gives:
scan code: 0x00   key code: brightnessdown
scan code: 0x00   key code: brightnessup
(which is true ;e) )

input-events 5 gives:
22:01:30.610733: EV_MSC code=4 value=247
22:01:30.610769: EV_SYN code=0 value=0
22:01:30.611648: EV_MSC code=4 value=247
22:01:30.611675: EV_SYN code=0 value=0
22:01:32.687762: EV_MSC code=4 value=248
22:01:32.687794: EV_SYN code=0 value=0
22:01:32.688687: EV_MSC code=4 value=248
22:01:32.688713: EV_SYN code=0 value=0
(that's twice the same output for each keypress)

input-events 6 gives:
22:02:03.536339: EV_KEY KEY_BRIGHTNESSDOWN (0xe0) pressed
22:02:03.536356: EV_SYN code=0 value=0
22:02:03.536361: EV_KEY KEY_BRIGHTNESSDOWN (0xe0) released
22:02:03.536365: EV_SYN code=0 value=0
22:02:04.837748: EV_KEY KEY_BRIGHTNESSUP (0xe1) pressed
22:02:04.837762: EV_SYN code=0 value=0
22:02:04.837766: EV_KEY KEY_BRIGHTNESSUP (0xe1) released
22:02:04.837769: EV_SYN code=0 value=0
(both "pressed" and "released" come up simultaneously, regardless of actual 
keydown/keyup)

-- 
hotkey-setup support for MSI PR200
https://bugs.launchpad.net/bugs/178860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to