@Seth: update for you. I just tested this on a Thinkpad Edge 11 that has a standard wireless hotkey (e.g. the key's primary function is wireless on/off, rather than using the Fn+F2 combo on the EeePCs I discovered this on) and this does not happen.
So in my experience so far, this issue only occurs on systems that use the Fn+F* combo to trigger wireless on and off.
lsinput on the Edge11 shows them as "ThinkPad Extra Buttons" rather than just HotKeys
/dev/input/event7
bustype : BUS_HOST
vendor : 0x17aa
product : 0x5054
version : 16641
name : "ThinkPad Extra Buttons"
phys : "thinkpad_acpi/input0"
bits ev : EV_SYN EV_KEY EV_MSC EV_SW
but when I try input-events on that event (and event3, the AT Keyboard), nothing is captured yet again.
@Seth: update for you. I just tested this on a Thinkpad Edge 11 that has a standard wireless hotkey (e.g. the key's primary function is wireless on/off, rather than using the Fn+F2 combo on the EeePCs I discovered this on) and this does not happen.
So in my experience so far, this issue only occurs on systems that use the Fn+F* combo to trigger wireless on and off.
lsinput on the Edge11 shows them as "ThinkPad Extra Buttons" rather than just HotKeys acpi/input0"
/dev/input/event7
bustype : BUS_HOST
vendor : 0x17aa
product : 0x5054
version : 16641
name : "ThinkPad Extra Buttons"
phys : "thinkpad_
bits ev : EV_SYN EV_KEY EV_MSC EV_SW
but when I try input-events on that event (and event3, the AT Keyboard), nothing is captured yet again.