Thanks, considering this fixed then.
** Changed in: cryptsetup (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/520160
Title:
cryptsetup race conditi
Hi,
I have not reproduced this bug in Lucid, and it therefore is no longer an issue
for me.
Regards,
== k+ ==
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/520160
Title:
cryptsetup race c
Ken, please provide feedback to the question asked by Steve.
Just leave a ping, if this is not an issue for you anymore, or cannot be
reproduced.
** Changed in: cryptsetup (Ubuntu)
Status: New => Incomplete
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided => Medium
--
You rec
Is this problem reproducible for you in lucid? Chances are good that
either these problems are solved, or you will now see a completely
different problem instead.
--
cryptsetup race condition on boot
https://bugs.launchpad.net/bugs/520160
You received this bug notification because you are a memb
FWIW, I don't see any way that the use of USB would account for this,
since obviously the USB disk has already been detected by the kernel in
the initramfs (or else the root filesystem couldn't be mounted).
--
cryptsetup race condition on boot
https://bugs.launchpad.net/bugs/520160
You received t
Ahh, an important detail I inadvertently left out. My system disk is a
USB connected drive (e.g. HP SimpleSave 320g), which could have bearing
on the race condition.
Regards,
== k ==
--
cryptsetup race condition on boot
https://bugs.launchpad.net/bugs/520160
You received this bug not
