Is /dev/null corrupted (see https://bugs.launchpad.net/ubuntu/+bug/387189) ?
This can trigger this bug.
** Also affects: pam (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=488147
Importance: Unknown
Status: Unknown
--
unix_chkpwd crashes on gnome-screensaver
https://bugs.l
I am having this issue on a lucid x64 install upgraded from a properly
working karmic. I have another lucid x64 clean install that does not
have the issue.
the only information I have is this in my auth.log. can I enable some extended
login somehow?
Apr 18 16:27:29 cw gnome-screensaver-dialog:
** Changed in: pam (Ubuntu)
Importance: Undecided => High
** Changed in: pam (Ubuntu)
Status: Invalid => Triaged
--
unix_chkpwd crashes on gnome-screensaver
https://bugs.launchpad.net/bugs/270781
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
This is in fact reproduceable. I had the same issue too, was difficult
to debug (due to setuid-ness of the binary in question), but finally it
turned out to be wrong permissions for /dev/full (local config error
really) - it was 0660 instead of 0666, so unix_chkpwd was unable to open
it when run
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
The contents of /etc/pam.d/* are immaterial, here; we know that it's the
unix_chkpwd process that's segfaulting, which means pam_unix must be
involved. And I have seen bugs more recently whereby pam_unix will fail
open if unix_chkpwd crashes unexpectedly; but the only case where I've
/seen/ unix_c
Can you post /var/log/syslog and /var/log/kern.log after the crash? What
are the contents of /etc/pam.d/common-* and /etc/pam.d/gnome-
screensaver. Does the username or password contain weird characters (if
posting them here, for your security, please change the password to
something else)?
--
un
In the meantime I've done a memory test over night and it passed without
errors.
Hardware is a Thinkpad T61 with following components:
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory
Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/G
I cannot reproduce this on an up to date hardy i386 virtual machine with
the same package versions. I even tried a small test program that just
runs unix_chkpwd with various input and it works fine. Can you run
'memtest' to make sure your memory is ok? Can you provide more details
on your setup?
