> > @Steve for me this was broken in Hardy with a Thinkpad. Perhaps people who > > reported it working in Hardy could give more info. >What info is needed?
I mean, we know from bug https://bugs.launchpad.net/bugs/217504 that acpi_fakekey has been broken since 2.6.24 was introduced, i.e. Hardy. So I agree with you there is a contradiction. So if someone has keys working in Hardy it should be informative to check *why*, i.e. check whether acpi_fakekey was called and which codes if any were sent by acpi_fakekey and whether they got through. Note acpi_fakekey is not 100% broken: codes below KEY_MAX do get through. You can also look at the scripts in /etc/acpi and look at the codes defined in /usr/share/acpi-support/key-constants and run acpi_fakekey from the keyboard. So for me (in Hardy) for example sudo acpi_fakekey 10 sends a "9" into my terminal, but sudo acpi_fakekey 224 does not lower the brightness, and sudo acpi_fakekey 154 does not lock the screen -- Hotkeys no longer working in Intrepid on Thinkpads https://bugs.launchpad.net/bugs/267682 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
