[pkg-cryptsetup-devel] Bug#768314: Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping

[Jonas Meurer]

Hi Kjetil,

Am 15.12.2014 um 00:23 schrieb Kjetil Kjernsmo:
> On Monday 8. December 2014 23.21.05 Jonas wrote:
>> I guess that you discovered the bug due to a separate /usr partition. I
>> just prepared packages that should fix the bug for you. Could you give
>> them a try and report back? I'd like to get this fixed in time for
>> jessie.
> 
> So, it is rather more apparent that it stops at some point now, but
> there still isn't clear prompt as far as I can see.
> 
> Adding to the problem is that things happen so fast, so I haven't got
> the time to understand what is going on. But it appears that there is
> kinda a prompt, then it rolls half a screen of unrelated messages,
> before it halts, and some kind of counter starts.
> 
> I suppose this isn't really clear enough, please let me know if there is
> anything else I can do to help, but I'm terribly busy these days, so I
> can't promise anything.

Thanks for your feedback. Can you provide me with some further information?

Which init system do you use? Is this systemd, sysvinit or something
completely different?

Did I get you right, that unlocking the encrypted root fs (sda5_crypt)
works as expected (i.e. you see a prompt asking for passphrase) while at
unlocking the encrypte home fs (owl-home_crypt) no prompt is displayed?

The main difference is, that the root fs is unlocked in initramfs, while
the home fs is unlocked by a initscript.

In case that you use systemd: I know that systemd introduced some
internal magic to handle encrypted devices at startup and to my
knowledge this is tried before the initscript from my packages are
started. So could you try the following: press return a few times when
the system boot stops waiting for the passphrase of you encrypted home
partition (without prompt) and see, whether it continues afterwards -
optionally showing the expected prompt afterwards?

Sorry to bother you with extra debugging work, but unfortunately you
seem to be the only one suffering from this bug so far.

Cheers,
 jonas