@Victor: /etc/rc.local and /usr/share/hotkey-setup/ibm.hk are both only
executed at boot time. So you would have to reboot to see the effect of
changes there.
But you can also execute "sudo setkeycodes e017 148" in a terminal for
an immediate result.
It does not really matter if you use ibm.hk or rc.local, but I'd vote
for rc.local, because that is (as the name suggests) the startup file
for your local changes and, hence, does not interfer with files which
are administrated by packages. (ibm.hk should be overwritten when an
update to hotkey-setup comes out.)
@all: The setkeycodes fix is a *very* dirty hack. In fact, it does not matter
which scancode is used at the first position. I've got
setkeycodes e07f 148 # ThinkPad Button
setkeycodes e07e 192 # Zoom (Fn-Space)
in my rc.local and it also does work. These are only needed to convince the
kernel that the keycodes in the second positions are legal, because it
otherwise does not propagate them when they are issued by acpi_fakekey.
The way to go is Sergey's fix above, which would make this whole mess
unnecessary.
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
