From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: X unlock bug revisited
Date: 06 May 2003 16:18:06 +0100 [thread overview]
Message-ID: <1052234284.1201.15.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0305061141300.1272-100000@oddball.prodigy.com>
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
next prev parent reply other threads:[~2003-05-06 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 15:50 Bill Davidsen
2003-05-06 15:18 ` Alan Cox [this message]
2003-05-06 15:56 ` Randy.Dunlap
2003-05-06 17:59 ` jjs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1052234284.1201.15.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®