[lkml]   [2003]   [May]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: X unlock bug revisited
Randy.Dunlap wrote:

>On Tue, 6 May 2003 11:50:22 -0400 (EDT) Bill Davidsen <> wrote:
>| Some months ago I noted that a new kernel introduced a failure to be able
>| to unlock X after locking. Still there in 2.5.69 for RH 7.2, 7.3, and 8.0.
>| Is there any plan to address whatever causes this problem with a kernel
>| fix, or is a 2.4 kernel still the way to go if you need to lock X. I
>| realize many developers work in environments where there's no need.
>This still bites me when I use xscreensaver, so I just use the KDE
>screen saver/locker instead. Eventually the pain level will be too
>much, though.

FWIW, I had this problem with late 2.5 kernels
on my 8.0 boxes - after upgrading to RH 9, the
xscreensaver unlocks properly when running
2.5 kernels -

Apparently the xscreensaver shipped with RH
9 contains the fixes - perhaps needed for their
kernel which contains backported 2.5 features?

Smarter folks than me may know more...


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

 \ /
  Last update: 2005-03-22 13:35    [W:0.103 / U:0.204 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site