mount.crypt segfaults when switching to battery
Bug #353935 reported by
Per Ångström
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libpam-mount (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: libpam-mount
Linux 2.6.28-11-generic #39-Ubuntu SMP Thu Apr 2 04:39:54 UTC 2009 x86_64 GNU/Linux
Having a tail on my /var/log/messages I see that whenever I pull the mains and the computer switches to battery, something like the following will be output:
Apr 2 18:23:17 barbaren kernel: [ 3661.921490] mount.crypt[6570]: segfault at fffffffffffffffc ip 00007fc12e315cfd sp 00007fff36737ab0 error 4 in libHX.so.
Today this happened while I was resuming from hibernation, and I got a crash report which was posted to bug #353726 (duplicate of #346824, which I'm not allowed to see).
Changed in libpam-mount (Ubuntu): | |
status: | Confirmed → Fix Released |
To post a comment you must log in.
I'm also having crashes of mount.crypt. I guess it's the same cause, so I'm attaching it here, rather then creating a new entry.
I have set up an encrypted loop file to be pam-mounted as a users home (the user is called "test" in my case). In most cases when loggin in as that user mount.crypt crashes. Sometimes it works, though. But it's not usable this way.
The loop file has been encrypted with:
cryptsetup -y --cipher aes-xts-plain --key-size 512 luksFormat /dev/loop0 test.img) .
(with /dev/loop0 connected to /data/tmp/
I added:
<volume user="test" fstype="crypt" path="/ data/tmp/ test.img" mountpoint="~" cipher= "aes-xts- plain" noroot="1" options=""/>
to /etc/security/ pam_mount. conf.xml. Using noroot="1" lets mount.crypt always crash (at least I haven't had a successful mount). Leaving it out, i.e. mounting as root, lets it work sometimes, but mostly it fails, too.