acpi_fakekey is just broken, it's just unreasonable to send a key to a random keyboard device and expect that the kernel will let the event though the key isn't actually present on the keyboard.
If we decide to keep acpi_fakekey around, I think we should switch to uinput to get rid of these issues once and for all as proposed earlier in this bug report. See http://launchpadlibrarian.net/21350541/acpi- support_0.115_0.115%2Bthjaeger1.diff.gz for a suggested implementation. By the way, the issue has been "fixed" on my thinkpad; the ThinkVantage button now calls acpi_fakekey on a different keycode that the kernel doesn't drop, but this issue is still present for example for KEY_WWW. -- acpi_fakekey stopped working for certain keycodes https://bugs.launchpad.net/bugs/217504 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
