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
On Mon, 2010-05-03 at 13:55 +, Vreixo Formoso wrote:
> I am having the /tmp issue with a Lucid fresh install. Is this really
> fixed?
>
I've not tried Lucid yet, but it's managed to "go away" for quite some
time now on Karmic (for me, at least). This is a nasty race condition
that seems to c
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
Public bug reported:
Binary package hint: cryptsetup
Hi,
I'm using Karmic Ubuntu 9.10 w/latest updates as of 2/5/2010. This includes:
cryptsetup: Installed: 2:1.0.6+20090405.svn49-1ubuntu7.2
watershed: Installed: 4
mountall: Installed: 1.0
I've been running with encrypted root/swap for a
Yes, that was my intial assessment; however:
1. They do match up.
2. It sometimes works
This is why I suspect a race condition.
Regards,
== k ==
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
https://bugs.launchpad.net/bug
I'd like to comment on this fix (e.g. cryptsetup -
2:1.0.6+20090405.svn49-1ubuntu7.2 w/watershed 4 and mountall 1.0):
I've been running with encrypted root/swap for a month, but then had
hardware problems forcing me to replace the system disk. All was well
for nearly a week 5+ days and 6+ reboots
