Re: X unlock bug revisited

Re: X unlock bug revisited

[Alan Cox]

On Maw, 2003-05-06 at 16:50, 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.

Its a pam bug triggered by the subtle scheduling timing changes and
fixed in Red Hat 9

X unlock bug revisited

[Bill Davidsen]

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.

Re: X unlock bug revisited

[Randy.Dunlap]

On Tue, 6 May 2003 11:50:22 -0400 (EDT) Bill Davidsen <davidsen@tmr.com> 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.

--
~Randy

Re: X unlock bug revisited

[jjs]

Randy.Dunlap wrote:

>On Tue, 6 May 2003 11:50:22 -0400 (EDT) Bill Davidsen <davidsen@tmr.com> 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...

Joe