Althouuh it crashed several times before I opened the bug, I haven't been
able to reproduce it since. I don't have ECC, so perhaps this can be
attributed to kernel memory corruption? Anyways, feel free to close the
bug and I'll reopen it if I can ever reproduce it again.
Ivan
--
To
I've been running it with -sync, but it hasn't crashed yet. When it does,
it doesn't leave a core file. (It's not segfaulting, it just seems to
exit.)
As far as PAM, xscreensaver is just using the default pam_unix:
a...@totoro:~$ cat /etc/pam.d/xscreensaver
#
# /etc/pam.d/xscreensaver - PAM
Package: xscreensaver
Version: 5.11-1
Severity: grave
Tags: security
Justification: user security hole
xscreensaver ocasionally crashes leaving my desktop unlocked. I'm not
sure how to reproduce it other than just using xscreensaver normally
for like a week. I'm also not sure whether it happens
That's a new one... Yes, -sync will probably help, as will a core file stack
trace. I suspect we will discover that some sub-process launched by your PAM
stack is crashing and taking libpam with it. That line about an unknown process
dying means that we got a SIGCHLD for a pid that
4 matches
Mail list logo
