Re: woes with 2.6.0-test1 and xscreensaver/xlock

From: Randy.Dunlap (
Date: Wed Jul 16 2003 - 14:16:27 EST

On Wed, 16 Jul 2003 14:58:43 -0400 (EDT) Zwane Mwaikambo <> wrote:

| On Wed, 16 Jul 2003, Nuno Monteiro wrote:
| > Is anyone else having trouble with xscreensaver/xlock under 2.6.0-test1?
| > Whenever I lock my session using either "lock screen" from the menu (it
| > launches 'xscreensaver lock', afaik) or "xlock", I cant seem to ever get
| > my session back -- I type in the correct password, but they both just
| > hang there. The exact same setup works flawlessly in 2.4.21, and just for
| > the sake of curiosity I also tested 2.5.75, 2.5.74, 2.5.73, 2.5.72,
| > 2.5.71 and 2.5.70, they all exhibit the same behaviour as 2.6.0-test1. I
| > dont really have time to go on testing kernels to find out exactly where
| > it broke, so I'm hoping anyone else is experiencing these woes.
| Someone reported this on bugzilla too, but i failed to reproduce it so it
| appears that perhaps something else died like the keyboard. I tried it
| last night on 2.6.0-test1 and i managed to login fine. It does appear that
| something else is dying. It'd be good if you could collect the last few messages
| from /var/log/XFree86.0.log and /var/log/messages and also perhaps
| /var/log/dmesg.

It happens to me all the time (so I stopped using xscreensaver).

Alan says that it's fixed in RH 9 IIRC, but no details about the
problem or the fix.... ? Sounds a little like a userspace (library
or syscall) issue. Someone mentioned PAM also.

| | |
For Linux-2.6:
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Wed Jul 23 2003 - 22:00:26 EST