Comment # 25 on bug 890115 from Bj�rn Lie

For no better reason than bug returning at the same time as we went to systemd 
219.

Now systemd might very well be just the messenger, but I have this in my logs
now

embla:~ # journalctl -b | grep systemd-vconsole
Apr 14 14:41:19 embla systemd-vconsole-setup[141]: /usr/bin/loadkeys failed
with error code 1.
Apr 14 14:41:19 embla systemd-vconsole-setup[141]: cannot open file no-latin1
Apr 14 14:41:20 embla unknown[1]: <audit-1130> pid=1 uid=0 auid=4294967295
ses=4294967295 msg='unit=systemd-vconsole-setup comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 14 14:41:20 embla kernel: audit: type=1130 audit(1429015280.350:3): pid=1
uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-vconsole-setup
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Apr 14 14:41:25 embla systemd-vconsole-setup[415]: /usr/bin/loadkeys failed
with error code 1.


and the fun 

embla:~ # lsinitrd /boot/initrd | grep no-latin1
-rw-r--r--   1 root     root         1714 Apr 10 10:11
usr/share/kbd/keymaps/i386/qwerty/no-latin1.doc

Returned to my initrid.

I'm pretty positive that GNOME has got nothing to do with whats in the initrid