Hello,
Thanks for your bug report.
I think you'll need to provide some basic information about how
you're using cryptmount before I can make any attempt to resolve
this bug report.
I have frequently tested 'cryptmount --prepare' on a wide range
of linux distros, including a broad cross-section of debian systems. Indeed,
I have run a pretty extensive testing suite on a debian-6.0.3 system
with exactly the same versions of libc6, libgcrypt11, libuuid1 that you
cite in your bug report. Those tests have not shown any sign of the problem
you mention, nor any sign that cryptmount is generally unusable.
Obviously, if you are running into problems with cryptmount,
I am keen to understand whether there are bugs that need fixing. However,
without more details of how to reproduce the symptoms you are seeing,
I cannot make any progress. If you need evidence of the tests that are
regularly preformed on cryptmount, you may like to refer to the 'mudslinger'
testing program within the cryptmount source distribution. If you can
suggest an additional test that should be included in there,
that would be especially helpful.
Kind regards,
RW Penney
+-- on Wed, Jan 18, 2012 at 11:55:27AM -0500, gds...@tx.rr.com wrote: ---+
> Subject: cryptmount --prepare fails
> Package: cryptmount
> Version: 4.1-2
> Justification: renders package unusable
> Severity: grave
> Tags: l10n
>
> *** Please type your report below this line ***
>
> Here are the error messages from syslog:
>
> Jan 16 20:33:04 far-star kernel: [ 690.357274] device-mapper: table: 254:0:
> crypt: Error allocating crypto tfm
> Jan 16 20:33:04 far-star kernel: [ 690.357284] device-mapper: ioctl: error
> adding target to table
>
> And here are the relevant messages from strace:
>
> munmap(0xb78b1000, 4096) = 0
> ioctl(3, DM_VERSION, 0x9a6d5c0) = 0
> ioctl(3, DM_DEV_CREATE, 0x9a6d5c0) = 0
> ioctl(3, DM_TABLE_LOAD, 0x9a6d5c0) = -1 EINVAL (Invalid argument)
> open("/usr/share/locale/en_US.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1
> ENOENT (No such file or directory)
> open("/usr/share/locale/en_US.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1
> ENOENT (No such file or directory)
> open("/usr/share/locale/en_US/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No
> such file or directory)
> open("/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT
> (No such file or directory)
> open("/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT
> (No such file or directory)
> open("/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No
> such file or directory)
> write(2, "device-mapper: reload ioctl fail"..., 52device-mapper: reload ioctl
> failed: Invalid argument) = 52
> write(2, "\n", 1
> )
>
> In a normal workstation/GUI US English installation libc.mo is not in the
> /usr/share/locale/en/LC_MESSAGES or /usr/share/locale/en_US/LC_MESSAGES
> directories in Squeeze or Lenny. It is in all (?) the other non-english
> directories.
>
> -- System Information:
> Debian Release: 6.0.3
> APT prefers stable
> APT policy: (500, 'stable')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages cryptmount depends on:
> ii libc6 2.11.2-10 Embedded GNU C Library: Shared
> lib
> ii libdevmapper1.02.1 [libdevma 2:1.02.48-5 The Linux Kernel Device Mapper
> use
> ii libgcrypt11 1.4.5-2 LGPL Crypto library - runtime
> libr
> ii libuuid1 2.17.2-9 Universally Unique ID library
>
> cryptmount recommends no packages.
>
> Versions of packages cryptmount suggests:
> ii dmsetup 2:1.02.48-5 The Linux Kernel Device Mapper
> use
> ii openssl 0.9.8o-4squeeze5 Secure Socket Layer (SSL) binary
> a
>
> -- Configuration Files:
> /etc/cryptmount/cmtab changed [not included]
>
> -- no debconf information
>
>
>
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
