Bug 975238 - systemd-vconsole-setup.service fails to set keymap at live boot (but works if restarted post-boot)
Summary: systemd-vconsole-setup.service fails to set keymap at live boot (but works if...
Keywords:
Status: CLOSED DUPLICATE of bug 1001411
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 19
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-17 21:10 UTC by Adam Williamson
Modified: 2013-09-29 18:08 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-09-29 18:08:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2013-06-17 21:10:55 UTC
After bcl fixed https://bugzilla.redhat.com/show_bug.cgi?id=974784 , if you specify 'keyboard fr' in a kickstart for a live image , the file /etc/vconsole.conf is written in the live image with this content:

KEYMAP="fr"
FONT="latarcyrheb-sun16"

However, on boot of the system, the 'us' keymap is still in use (though 'localectl' reports "VC Keymap: fr". If you run 'systemctl restart systemd-vconsole-setup.service' , the correct keymap is loaded.

Not sure if this is a bug in systemd or if it correctly loads fr and then something else jumps in and loads us, I'm currently trying to track it down.

Comment 1 Kay Sievers 2013-06-17 21:21:48 UTC
Might be this:
  https://bugzilla.redhat.com/show_bug.cgi?id=970030

Comment 2 Adam Williamson 2013-06-17 22:56:08 UTC
I'm not totally sure I see the connection; I've been vaguely following that whole ball of wax but I don't quite see what you mean by them being the same thing. What exactly is the problem in 970030? What needs to happen to fix it? Why might that fix this too?

Comment 3 Adam Williamson 2013-06-17 22:57:30 UTC
Oh, in case it helps in debugging at all, I've noticed that consoles (VTs) in my VMs often somewhat inexplicably have a sort of ugly, vomit-yellow color background, including in this case. As well as making the keyboard map take effect, 'systemctl restart systemd-vconsole-setup.service' causes that background to go away. No idea what that means, but maybe it means something.

Comment 4 Adam Williamson 2013-06-17 23:00:27 UTC
oh, and indeed, the console on the live images does show the unicode apostrophe in "Schrödinger’s Cat" as a square blob.

Comment 5 Mark Harig 2013-07-11 21:05:22 UTC
This problem occurs with an installed system, also. (It's not specific to "live" boots from CD/DVD.)  Neither the keymap nor the font specified in /etc/vconsole.conf are recognized:

From /var/log/messages:
systemd[1]: Starting Setup Virtual Console...
localhost.localdomain systemd-vconsole-setup[120]: cannot open file [key-map file]
localhost.localdomain systemd-vconsole-setup[120]: /usr/bin/loadkeys failed with error code 1.
localhost.localdomain systemd-vconsole-setup[120]: Cannot open font file [font name]
localhost.localdomain systemd-vconsole-setup[120]: /usr/bin/setfont failed with error code 66.
localhost.localdomain systemd[1]: Started Setup Virtual Console.

Once the system has started, 'sudo systemctl restart systemd-vconsole-setup.service' completes without error, the font is changed and the new keymap is in effect.

Changing the kernel command-line options 'vconsole.keymap' and 'vconsole.font' does not fix the problem, either. The default keymap and font are in effect when the system has finished start-up.

$ rpm -q kernel systemd
kernel-3.9.9-301.fc19.x86_64
systemd-204-9.fc19.x86_64

Comment 6 Adam Williamson 2013-07-11 21:14:13 UTC
Mark: I don't think that's necessarily the same thing. Setting keymap in /etc/vconsole.conf on an installed system works fine for me.

Comment 7 Mark Harig 2013-07-11 21:34:51 UTC
(In reply to Adam Williamson from comment #6)

OK. I will submit a new report.

Comment 9 Lennart Poettering 2013-09-29 18:08:37 UTC

*** This bug has been marked as a duplicate of bug 1001411 ***


Note You need to log in before you can comment on or make changes to this bug.