matejcik [2009-08-26 17:43 -0000]:
> no, the keys aren't hardwired, there are still situations where they
> don't work.
Hm, interesting. So just to confirm, without the udev rule (after a
clean boot, so that the keymap is really reset), and acpid stopped you
still get the correct keys in xev? That's really a kind of magic. I
checked your lsinput and udev db dump, and there's no other magic
input device where they could come from.
> so, is it normal that the key sends the event twice?
No, that's a bug. I suppose enabling them in acpi-support or udev
makes them work the proper way, and then there's the "magic way" from
above which we didn't understand yet.
> and if it is a kernel bug, where to report it and how to debug it?
Reporting can be done here (I opened a linux task), but right now I'm
afraid I don't know how to debug it either. :-(
matejcik [2009-08-26 17:43 -0000]:
> no, the keys aren't hardwired, there are still situations where they
> don't work.
Hm, interesting. So just to confirm, without the udev rule (after a
clean boot, so that the keymap is really reset), and acpid stopped you
still get the correct keys in xev? That's really a kind of magic. I
checked your lsinput and udev db dump, and there's no other magic
input device where they could come from.
> so, is it normal that the key sends the event twice?
No, that's a bug. I suppose enabling them in acpi-support or udev
makes them work the proper way, and then there's the "magic way" from
above which we didn't understand yet.
> and if it is a kernel bug, where to report it and how to debug it?
Reporting can be done here (I opened a linux task), but right now I'm
afraid I don't know how to debug it either. :-(