On 03/08/2009 Stuart Pook wrote:
hello Jonas
Jonas Meurer wrote:
please also provide the output of 'udevadm monitor' while running
'cryptsetup luksOpen ...'.
I guess that you don't need this anymore given that you have found the
bad rule in udev
hey,
maybe you could check whether the
this was reported upstream
http://code.google.com/p/cryptsetup/issues/detail?id=34
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
hey,
On 02/08/2009 Stuart Pook wrote:
On 31/07/09 01:58, Jonas Meurer wrote:
this sounds like a udev race condition. could you give cryptsetup
2:1.0.7-1 from debian/unstable a try?
2:1.0.7-1 does not work either
: root; cryptsetup luksOpen /dev/mapper/vg0-asterisk_ROOT_snapshot
hi Jonas
On 31/07/09 01:58, Jonas Meurer wrote:
this sounds like a udev race condition. could you give cryptsetup
2:1.0.7-1 from debian/unstable a try?
2:1.0.7-1 does not work either
: root; cryptsetup luksOpen /dev/mapper/vg0-asterisk_ROOT_snapshot
asterisk_ROOT_snapshot --key-file /tmp/xx
Hey Stuart,
thanks for your bugreport.
On 24/07/2009 Stuart Pook wrote:
Crytsetup 2:1.0.7~rc1-2 often fails to open my devices. Sometimes it works
but I'm not exactly sure under
what conditions. Downgrading to 2:1.0.6+20090405.svn49-1 from testing works.
: root; cryptsetup luksOpen
Package: cryptsetup
Version: 2:1.0.7~rc1-2
Severity: important
Crytsetup 2:1.0.7~rc1-2 often fails to open my devices. Sometimes it works but
I'm not exactly sure under
what conditions. Downgrading to 2:1.0.6+20090405.svn49-1 from testing works.
: root; cryptsetup luksOpen
6 matches
Mail list logo
