Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263884AbTEFQFQ (ORCPT ); Tue, 6 May 2003 12:05:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263886AbTEFQFQ (ORCPT ); Tue, 6 May 2003 12:05:16 -0400 Received: from pc2-cwma1-4-cust86.swan.cable.ntl.com ([213.105.254.86]:24960 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S263884AbTEFQFJ (ORCPT ); Tue, 6 May 2003 12:05:09 -0400 Subject: Re: X unlock bug revisited From: Alan Cox To: Bill Davidsen Cc: Linux Kernel Mailing List In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1052234284.1201.15.camel@dhcp22.swansea.linux.org.uk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 06 May 2003 16:18:06 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 537 Lines: 12 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/