This issue has been patched in cryptmount-2.1 with a precautionary "modprobe"
in the /etc/init.d scripts.
An updated debian package (2.1-1) has just been uploaded to unstable.
--
cannot initialize device-mapper
https://bugs.launchpad.net/bugs/93568
You received this bug notification because you
Can this bug be marked as resolved?
Package bash-3.2-0ubuntu11, as used in xubuntu7.10, appears to correctly
reference /usr/lib/command-not-found in /etc/bash.bashrc.
--
[gutsy] command-not-found not found
https://bugs.launchpad.net/bugs/135794
You received this bug notification because you are
*** This bug is a duplicate of bug 135794 ***
https://bugs.launchpad.net/bugs/135794
** This bug has been marked a duplicate of bug 135794
[gutsy] command-not-found not found
--
command-not-found executable missing
https://bugs.launchpad.net/bugs/140868
You received this bug notification
python-flac was removed from the Ubuntu archives in November 2006
(bugs.launchpad.net/ubuntu/+source/pyflac/0.0.4-1) python-mutagen might
be an appropriate replacement.
Should this bug be marked as completed?
--
TypeError thrown from vorbiscomment_set_vendor_string
https://bugs.launchpad.net/bug
*** This bug is a duplicate of bug 106696 ***
https://bugs.launchpad.net/bugs/106696
** This bug has been marked a duplicate of bug 106696
Failure to auto-load dm-mod kernel module
--
libdevmapper incompatible with cryptsetup kernel driver
https://bugs.launchpad.net/bugs/64625
You receive
I've attached a *tentative* patch, which should make encrypted-passwords the
default option, by adding a new debconf parameter
("grub-installer/hash-password") which controls whether the manually-entered
password is passed through grub's md5crypt function before entry in the
menu.lst.
If approp
I think this is really a problem with the libdevmapper package (1.02.08)
in the ubuntu-7.04-beta release which I have tried this on. The problem
seems to be entirely due to the failure to load the main device-mapper
kernel-module either on system boot-up or when libdevmapper is first
used. The debi
Public bug reported:
The libdevmapper package (1.02.08 in ubuntu-7.04-beta) does not auto-
load the kernel dm-mod module either at system bootup, or when first
used by a client application (e.g. cryptsetup, cryptmount). This means
that those client applications will typically fail unless the user
This bug report really does not sound like it refers to the "cryptmount"
package.
Specifically, "cryptmount" does not use the /etc/crypttab file for any
purpose, nor does it include any utility called "cryptswap" (even though
if offers similar generic functionality).
More generally, it would appe
As a reminder - your bug report does NOT relate to the "cryptmount"
package given details in your original post.
The problem with running "swapon" with an encrypted partition is simply
that both the /etc/crypttab mechanisms, and those of other encryption
tools, perfectly reasonably regenerate the
Thanks for finding this bug, and for the helpful stack traces.
I believe this problem is due to differences in the error-checking applied in
the LUKS key-manager from other cryptmount key-managers.
I've attached a patch which I hope will sort out the problem.
This patch will be incorporated in fut
Can we declare this bug to have been fixed?
The upstream Debian bug has been fixed since June 2010; cryptmount-4.1
has been part of Ubuntu releases "Maverick" (10.10) and "Natty" (11.04);
and cryptmount-4.2 has just been been flagged for inclusion in "Oneiric"
(11.10).
--
You received this bug n
I suspect this issue could be the result in changes in the behaviour of
cryptsetup since the upgrade.
Instead of trying to read the key-material from stdin, you could try
"crypsetup --key-file /mnt/usb/keys/fs". The failure to mount could
simply be a sign that the filesystem hadn't been decrypted
d to run. This feature
is currently part of the beta release of cryptmount-4.2. I'm hoping this
will significantly reduce the risk of accidental dataloss in a way similar
to the /etc/crypttab issue, even if it can't eliminate it entirely.
Kind regards,
RW Penney
--
You received this
The upstream release of cryptmount-4.1
(http://www.sourceforge.net/projects/cryptmount) includes this patch.
cryptmount-4.1-2 is now available in debian-testing, and is scheduled for
inclusion in the Maverick Meerkat release of Ubuntu.
cryptmount-4.0.2 has been available in Lucid Lynx for a while
This is more of a feature request than a bug in cryptmount.
As already noted, the original source of the problem seems to be the behaviour
of the LVM system.
--
LVM unusable after uncleanly unplugging USB disk
https://bugs.launchpad.net/bugs/223583
You received this bug notification because you
16 matches
Mail list logo
