On my toshiba Satellite A10 S100 the lock button (Fn+F2) doesn't works (It worked on gutsy, not anymore in hardy)
I can see in the logs that "/etc/acpi/lockbtn.sh" has ran, so all the toshiba_acpi stuff is working. In gnome-keybinding-properties when I try to change the default CRTL- Alt-L to the lockbtn, it does nothing. If I run "acpi_fakekey 128" (remotelly don't touching the local keyboard) I get an "0xe8" choice in gnome-keybinding-properties. With acpi_fakeykey 156 I get an "0xe6" choice in the gnome-keybinding-properties window. I really don't understand the correlation between the fakekey code and que gnome-keybinding-properties hex code. Anyway... When I type "acpi_fakekey 152" (the $KEY_COFFEE) in the remote shell: gnome-keybinding-properties does nothing. Also if I cat /dev/input/by-path/platform-i8042-serio-0-event-kbd I can see "things" anytime I press any key and when I do remotelly acpi_fakekey 128 (or 1, 2, 3.., 60, etc). Trying with many other fakekey numbers also works but with 152 does nothing. The Quick and dirty solution will be change the acpi script to send CTRL-Alt-L when lockbtn is pressed instead the 152 in acpi_fakekey. But I don't know what to send in acpi_fakekey to get CTRL-Alt-L. -- "screen lock" button no longer locks screen https://bugs.launchpad.net/bugs/22048 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
