I figured out what the problem was myself: The manpage of udevadm is
incorrect. Or at least misleading. It says:
<----- snip ----->
udevadm hwdb [options]
Maintain the hardware database index in /lib/udev/hwdb.bin.
--update
Compile the hardware database information located in
/lib/udev/hwdb.d/, /etc/udev/hwdb.d/ and store it in
/lib/udev/hwdb.bin. This should be done after any update to the
source files; it will not be called automatically. The running udev
daemon will detect a new database on its own and does not need to
be notified about it.
<----- snap ----->
The last sentence seems to indicate that compiling the hwdb is the only
thing you have to do to make changes take effect. This, however, is NOT
true on my system.
Not only did I have to recompile the hwdb but you also reload it:
'udevadm control --reload'.
Then I had to re-connect the keyboard in question.
And *then* I could use the new keymapping.
I therefore suggest to change the sentence in the manpage above to say the
exact opposite, refer the user to the 'udevadm control --reload' command and
tell them to reconnect the hardware (or reboot, if hotplugging is not
supported).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1361338
Title:
Custom keymap in hwdb not working
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1361338/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
