Public bug reported:

Binary package hint: upstart

Hi!

First of all, I'm not sure if this belongs to upstart or cryptsetup. I'm filing 
it under upstart just because
it's a regression from Jaunty (i.e. it worked on jaunty, just upgraded to 
Karmic, now it doesn't) and the
cryptsetup behaviour looks the same. It may also be a bug in cryptsetup that 
was masked by
Jaunty's behaviour.

I have two partitions on /etc/crypttab. One of them is swap and another
is a regular disk.

In Jaunty, as a part of the boot process, I got asked the passwords for these 
early (swap on
initramfs, the regular one at the normal init process), way before starting X.

After upgrading to Karmic, apparently X starts in parallel to the cryptsetup 
init script, so I have to
switch to the text console to enter the second password (the initramfs 
obviously works just fine).
It should be noted that after I enter them, the boot process continues by 
running other scripts.

I'd expect the cryptsetup runs early on, before X is started, to prevent
things like this.

While I can work around this on this computer, I thought it would be better to 
report it in case there
are more complex scenarios that can cause more trouble.

If anyone needs more information, please let me know.

Thanks a lot,
        Alberto

ProblemType: Bug
Architecture: amd64
Date: Wed Oct  7 19:50:38 2009
DistroRelease: Ubuntu 9.10
Package: upstart 0.6.3-7
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: upstart
Uname: Linux 2.6.31.1 x86_64

** Affects: upstart (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug

-- 
Can't enter password for encrypted devices at boot time
https://bugs.launchpad.net/bugs/445888
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to