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

[Kjetil Kjernsmo]

On Monday 15. December 2014 17.13.05 Jonas Meurer wrote:
> Hi Kjetil,
> 
> after discussing this issue with other fellow debian developers,
> i might have a better understanding of what's going on. to be
> honest, i don't have much experience with systemd myself yet.

OK! It seemed a little bit rushed to me to get as much as possible into systemd for jessie, but I suppose I 
shouldn't get involved as a non-DD :-)

> Am 2014-12-15 12:07, schrieb Kjetil Kjernsmo:
> > On Monday 15. December 2014 07.34.07 Jonas Meurer wrote:
> >> Which init system do you use? Is this systemd, sysvinit or something
> >> completely different?
> > 
> > I think it is systemd (no conscious decision from my side):
> > kjetil at owl:~$ ls -l /sbin/init
> > lrwxrwxrwx 1 root root 20 Nov 28 06:55 /sbin/init ->
> > /lib/systemd/systemd
> 
> as written earlier, systemd has it's own cryptsetup agent and
> uses that one to unlock encrypted devices instead of the the
> cryptdisks initscripts used by sysvinit.
> 
> the problem is, that systemd doesn't wait for optional user
> input after running cryptsetup. the boot logger plymouth is
> responsible for this task.

Aha, OK!

> could you try to install plymouth on your system and see whether
> that fixes your issues? you can configure plymouth to use a
> text-mode theme if you don't like the graphical boot splash
> screen that hides all the boot log messages.

Ah, yeah, that did work! In fact, I only had to write the passphrase once, which is kinda weird, what if I 
didn't use the same passphrase for both partitions? (Oh, I shouldn't say that I do ;-))


> if missing plymouth is the reason for the issues you discovered,
> then i fear that there's no easy solution to fix this bug. it seems
> like systemd simply requires something like plymouth to properly
> display user prompts at boot time :-/

Mmmm, yeah... And I can't use a different init at this point?
 

> that's a separate issue. seems like systemd indeed doesn't support
> separate /usr partitions.

Hmpf, yeah... :-( And plymouth didn't fix it... :-(

Oh well, I suppose you could say wontfix on this bug, then!

Cheers,

Kjetil


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20141215/4256a3c9/attachment.html>