** Branch linked: lp:ubuntu/karmic/cryptsetup
--
cryptsetup: failed to setup lvm device
https://bugs.launchpad.net/bugs/151532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
This bug was fixed in the package cryptsetup - 2:1.0.6-6ubuntu1
---
cryptsetup (2:1.0.6-6ubuntu1) intrepid; urgency=low
* drop almost all ubuntu specific changes from the cryptsetup package,
because they have been merged in debian. Thanks a lot!
* merge from debian, remaining
Secure bit could you elaborate on your luks not being able to open the
partition problem? I'm using AES256-CBC-ESSIV with SHA-256 as the hash
algo, and I have had no such pain.
Its purely cosmetic for me, as mentioned already.
--
cryptsetup: failed to setup lvm device
https://bugs.launchpad.net
Agree with Chris, I use dm-crypt & LUKS with root on LVM inside the
encrypted partition, and I see this on Intrepid (latest patches) with
2.6.27-2. Doesn't seem to have any negative effect mind :)
--
cryptsetup: failed to setup lvm device
https://bugs.launchpad.net/bugs/151532
You received this
I never saw this in hardy, but I see it after an Intrepid upgrade, both
with and without usplash.
--
cryptsetup: failed to setup lvm device
https://bugs.launchpad.net/bugs/151532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
This is still happening in intrepid alpha 4 (IBM Thinkpad R61, 32 bit
intrepid)
--
cryptsetup: failed to setup lvm device
https://bugs.launchpad.net/bugs/151532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Still present in Intrepid alpha-2.
Tore
--
cryptsetup: failed to setup lvm device
https://bugs.launchpad.net/bugs/151532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
** Tags added: iso-testing
--
cryptsetup: failed to setup lvm device
https://bugs.launchpad.net/bugs/151532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
I can confirm this on an up-to-date hardy installation.
Kernel: 2.6.24-19-server
Architecture: amd64
Cryptsetup: 1.0.5
Indeed only cosmetical but irritating nonetheless.
** Tags added: cryptsetup initramfs lvm
** Tags removed: iso-testing
--
cryptsetup: failed to setup lvm device
https://bugs
luks never opened that partition, and I had to format the hard disk,
I've lost all my important data !
--
cryptsetup: failed to setup lvm device
https://bugs.launchpad.net/bugs/151532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
I have this problem in the ubuntu studio and once I see it the system
stop loading, what should I do to rescure my data ? thank you
--
cryptsetup: failed to setup lvm device
https://bugs.launchpad.net/bugs/151532
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is known and ugly, but only cosmetical. The cryptsetup initramfs
scripts should not really attempt to manually set up LVM. udev does it
all for us, in a much more robust and automatic fashion. The only thing
cryptsetup initramfs needs to do is to read the configuration file to
find out which p
** Tags added: iso-testing
--
cryptsetup: failed to setup lvm device
https://bugs.launchpad.net/bugs/151532
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
13 matches
Mail list logo
