Hide Forgot
Description of problem: After a boot to runlevel 3 (with fixes to bug #618315 already applied) there is no echo of typed characters. Login over a network and killing 'login' process "fixes" that to some extent, i.e. echoing returns, but now it turns out that keystrokes are accepted or not in an apparently random manner. Sometimes they have to be doubled before they "take", sometimes not and sometimes a line terminator shows up "by itself". Due to these interesting properties chances of getting at least some resemblance of a working console without a network connection are rather meagre. With an initial login keystrokes are accepted "in blind", i.e. without echo, but no way to predict what reached the system. After booting with "... 3 init=/sbin/upstart" both login and console behave as they should. Version-Release number of selected component (if applicable): systemd-4-4.fc14 Additional information: I did not notice instances when more that two repeats of a keystroke were required to send a given character; only that sometimes one hit is enough and sometimes not.
Does it happen on tty1 only or are other VTs affected too? (Try ALT+F<n>)
(In reply to comment #1) > Does it happen on tty1 only or are other VTs affected too? (Try ALT+F<n>) Good call! There is an echo on other VTs from the start and typed characters are lost very infrequently (it still happens sporadically). Killing mgetty on tty1 does restore echo there but does nothing to make a keyboard sane. Even switching to another console may require mulitiple keyboard hits and may stall for a while.
The problem is that in multi-user.target nothing tells plymouth to quit. In upstart it was done by /etc/init/quit-plymouth.conf which calls "/usr/bin/plymouth quit".
Fixed now upstream. Upload to F14 follows shortly.
%post scriptlet of systemd-units still says ----------------------------------------- 111 %post units 112 if [ $1 -eq 1 ] ; then ----------------------------------------- So do we again have to $ rpm -e --nodeps systemd-units and reinstall systemd-units, not by just update?