xscreensaver and kernel 2.6.x

xscreensaver and kernel 2.6.x

[Charles Shannon Hendrix]

I'm trying to find the details on why xscreensaver has some troubles
with the 2.6 kernels.

On my system, something in pam is failing, causing a several seconds
delay when unlocking my screen.

In /var/log/messages, I get this:

Jan 18 17:59:07 daydream xscreensaver(pam_unix)[869]: authentication
failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=shannon
Jan 18 17:59:09 daydream xscreensaver(pam_unix)[869]: authentication
failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost=  user=root

This happens with all 2.6 kernels, and all earlier kernels work fine.

I found a lot of references to problems with pam and the 2.5 and 2.6
kernels, but can't seem to find the details I want.

Any help appreciated.

I don't get lockups, but the delay is annoying, and I hate broken
things.


-- 
UNIX/Perl/C/Pizza____________________s h a n n o n@wido !SPAM maker.com

Re: xscreensaver and kernel 2.6.x

[Randy.Dunlap]

On Sun, 18 Jan 2004 18:57:28 -0500 Charles Shannon Hendrix <shannon@widomaker.com> wrote:

| 
| 
| I'm trying to find the details on why xscreensaver has some troubles
| with the 2.6 kernels.
| 
| On my system, something in pam is failing, causing a several seconds
| delay when unlocking my screen.
| 
| In /var/log/messages, I get this:
| 
| Jan 18 17:59:07 daydream xscreensaver(pam_unix)[869]: authentication
| failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=shannon
| Jan 18 17:59:09 daydream xscreensaver(pam_unix)[869]: authentication
| failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost=  user=root
| 
| This happens with all 2.6 kernels, and all earlier kernels work fine.
| 
| I found a lot of references to problems with pam and the 2.5 and 2.6
| kernels, but can't seem to find the details I want.
| 
| Any help appreciated.
| 
| I don't get lockups, but the delay is annoying, and I hate broken
| things.

There are patches in Red Hat 9 (pam) for this, and someone else
pointed to the location of pam package fixes for it, but I don't
have that pointer around... sorry.

--
~Randy
Everything is relative.