Created attachment 92601 [details]
Screenshot depicting distorted systemd-ask-password prompt
This is not really a bug that affects any crucial functionality but more of a visual thing.
I'm running Arch Linux with systemd 208 in the initrd with my root device encrypted using dm-crypt, without plymouth. At some point systemd asks for the password to unlock the root device on the console. After 1 or 2 seconds this prompt gets "newlined" and interrupted by several other systemd messages. Typing in the password and pressing Return to confirm it works as expected, however.
I attached a screenshot (sorry for the quality) to illustrate the problem.
Ooops, that seems to be a result of the recent changes to show more status.
@Zbigniew: just to be clear, the reporter is running 208, so it must be happening for him because he is booting without "quiet" (afaik this has always behaved like that).
Either way, the problem with the recent changes to activate output after X seconds of waiting (210?) now causes this for people running _with_ "quiet" as well. systemd.show_status=0 is a workaround, but I guess in the long term there should be some kind of exception if a job is "hanging" because of password input.
Yes, the problem persists with systemd-211, quiet doesn't help (which is by the way not what I want, I want to see boot time messages)
[Something else strikes me as odd, but I'm not sure if this is a completely new bug or this one. I was trying to use systemd-gpt-auto-generator within my initrd (i.e. no fstab, no crypttab, no root=) and I'm seeing a similar thing: I'm being asked for my password, the prompt is reprinted every 5 (or so) seconds. This time the bug effectively prevents me from booting my system. See this post: https://bbs.archlinux.org/viewtopic.php?pid=1394879 ]
On my tests even a boot with systemd.show_status=0 overwrites the password prompt with unit startup messages.
Attaching a patch proposal to solve this.
Created attachment 98491 [details] [review]
dont overwrite crypt password prompt with status messages
Any updates on this? It's still happening with systemd-216.
This was only partially fixed in 217. There is no more output while the password is being queried. But when booting with quiet, the "show status after x seconds of waiting" is still triggered right after entering the password and pressing enter.
(In reply to mus.svz from comment #7)
> This was only partially fixed in 217. There is no more output while the
> password is being queried. But when booting with quiet, the "show status
> after x seconds of waiting" is still triggered right after entering the
> password and pressing enter.
That's basically a race condition, where systemd does not treat the removal of an ask-password entry as a event which bumps the timestamp of the last action. This can be added. However, an alternative implementation is being discussed on the mailing list (http://lists.freedesktop.org/archives/systemd-devel/2014-October/024717.html) so things are likely to change.
This is also tracked here:
Closing this here.