The Debian maintainer told me that this should be fix with later
versions of libpam-mount, which are now in our development release. See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484122 for details. If
this is in error or you are still able to reproduce this issue on an up
to date Ubuntu 10.
Appears to be rare, but confirming since multiple people have seen this.
Haven't seen a report of this on 9.10 or 10.04... if someone could
confirm it still occurring there, it would be helpful.
Duplicate bug has a very similar stack trace.
** Changed in: cron (Ubuntu)
Status: New => Confi
Here's the libpam-mount package. Hopefully this is helpful to somebody.
** Attachment added: "libpam-mount_1.32-1_amd64.deb"
http://launchpadlibrarian.net/33434570/libpam-mount_1.32-1_amd64.deb
--
cron crashed with SIGSEGV in pam_open_session()
https://bugs.launchpad.net/bugs/358983
You recei
I ran into this problem too. I built some packages for the amd64
architecture, and they seem to be working alright. I've attached the
libhx dep package, libpam-mount package to follow.
** Attachment added: "libhx_3.1-1_amd64.deb"
http://launchpadlibrarian.net/33434559/libhx_3.1-1_amd64.deb
--
Rotbart van Dainig wrote on 2009-04-19:
> cron fails when pam_mount has a volume that has no user specified.
No. Cron fails even when pam_mount got specified user. If i add this:
Cron will fail.
RK wrote on 2009-06-03:
> I uploaded my self-compiled libpam_mount (plus the required libhx from
>
I uploaded my self-compiled libpam_mount (plus the required libhx from
debian/sid) here:
deb http://www.climm.org/deb/ jaunty main
(And no, I do not have a volume without user specified, only users
without volume...)
--
cron crashed with SIGSEGV in pam_open_session()
https://bugs.launchpad.net/
Am Mittwoch, den 03.06.2009, 08:56 + schrieb Norbert Hartl:
> Is there a solution or at least a workaround?
Solution: Fix cron.
Workaround: Specifiy a user for pam_mount
--
cron crashed with SIGSEGV in pam_open_session()
https://bugs.launchpad.net/bugs/358983
You received this bug notificat
I have this problems, too. It seems to segfault everytime it is invoked.
I use pam_mount to mount my encrypted /home. Is there a solution or at
least a workaround?
--
cron crashed with SIGSEGV in pam_open_session()
https://bugs.launchpad.net/bugs/358983
You received this bug notification because
Found the case of the cron bug in Intrepid again:
cron fails when pam_mount has a volume that has no user specified.
--
cron crashed with SIGSEGV in pam_open_session()
https://bugs.launchpad.net/bugs/358983
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Am Montag, den 13.04.2009, 13:54 + schrieb RK:
> In intrepid, I certainly didn't get segfaults each time cron started the
> script to fetch email - I'd have noticed email not arriving for half a
> year.
Don't really remember nor do I really care - other people complained.
Am Montag, den 13.04
In intrepid, I certainly didn't get segfaults each time cron started the
script to fetch email - I'd have noticed email not arriving for half a
year.
And yes, the bug is in pam_mount and can easily be fixed by updating to
current pam_mount. Took me 5 minutes to re-compile, will take Ubongo
years..
This bug was around for a while and is tied to pam_mount - in Intrepid,
it failed just silently.
--
cron crashed with SIGSEGV in pam_open_session()
https://bugs.launchpad.net/bugs/358983
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/25204196/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/25204197/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/25204198/ProcMaps.txt
** Attachment ad
13 matches
Mail list logo
