Nice catch. There is a keyboard-setup.init script; but that's not being installed either because for upstart, all these were replaced by a single upstart job to deal with the keyboards.
The net result appears to be that keymap is not correctly set in a VT -- I'll look to find other reports of this issue, there is bound to be others. There is another fix I need to land for console-setup related to the move from upstart to systemd; we can land all this together. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1579267 Title: plymouth-start.service: After: reference to non-existent keyboard- setup.service Status in console-setup package in Ubuntu: New Bug description: 16.04 amd64. plymouth-start.service refers to a non-existent keyboard- setup.service: $ grep keyboard -r /lib/systemd/system/* /lib/systemd/system/plymouth-start.service:After=systemd-udev-trigger.service systemd-udevd.service keyboard-setup.service tj@T300CHI:~$ apt-file search keyboard-setup.service tj@T300CHI:~$ The file only exists in 16.10 in console-setup-linux This caught me out whilst I was debugging some console-setup issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1579267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp