keyboard-configuration's console-setup.service is a static unit which is
only being pulled in by systemd-vconsole-setup.service. This was
previously pulled in by plymouth-start.service, but this seems an odd
and unreliable way of doing that. systemd-vconsole-setup.service has
never existed in Debian, and the dependency to it got removed from
Debian's plymouth a long time ago; and now that we merged plymouth it's
gone in Ubuntu as well.
IMHO keyboard-configuration should just (statically) enable console-
setup.service by itself, as the provider of that functionality. In
Debian it gets started automatically via the init.d script. In Ubuntu we
have a systemd unit, but back then I was misled:
console-setup (1.108ubuntu4) vivid; urgency=medium
* Add systemd unit for console-setup. That avoids waiting for $remote_fs
during early boot. (Note: there is no need to enable it, it gets pulled
in through systemd-vconsole-setup.service) (LP: #1430280)
-- Martin Pitt <[email protected]> Wed, 11 Mar 2015 15:33:49
+0100
** Changed in: console-setup (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531442
Title:
reboot switches to us keyboard layout on console
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1531442/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
