plymouth-start.service: After: reference to non-existent keyboard-setup.service
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
console-setup (Ubuntu) |
Fix Released
|
Medium
|
Mathieu Trudel-Lapierre | ||
Xenial |
Fix Released
|
Medium
|
Mathieu Trudel-Lapierre |
Bug Description
[Impact]
Keymaps are not correctly set on virtual console (in gettys)
[Test case]
Set keymap, using us, intl variant. Test that dead keys behave correctly (ie. hitting an apostrophe and then e yields "é" rather than "'e".
[Regression potential]
System that carry a keyboard configuration but the system administrators rely on the fact that the local console keymap remains in US will find that it no longer behaves as expected.
---
16.04 amd64.
plymouth-
$ grep keyboard -r /lib/systemd/
/lib/systemd/
tj@T300CHI:~$ apt-file search keyboard-
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.
Changed in console-setup (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Medium |
Changed in console-setup (Ubuntu Xenial): | |
status: | New → In Progress |
importance: | Undecided → Medium |
Changed in console-setup (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in console-setup (Ubuntu Xenial): | |
assignee: | nobody → Mathieu Trudel-Lapierre (cyphermox) |
description: | updated |
It's not a bug for a systemd unit to reference a non-existent unit in 'Before' or 'After'; this declares sequencing relative to other units *if* they exist. If the named unit does not exist, the relationship is ignored - this is not a 'Requires' dependency.
If anything, the bug here appears to be that the keyboard- setup.service is *absent* in 16.04. Reassigning to console-setup for investigation.