Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263848AbTEFPh4 (ORCPT ); Tue, 6 May 2003 11:37:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263855AbTEFPh4 (ORCPT ); Tue, 6 May 2003 11:37:56 -0400 Received: from prgy-npn1.prodigy.com ([207.115.54.37]:1028 "EHLO oddball.prodigy.com") by vger.kernel.org with ESMTP id S263848AbTEFPhz (ORCPT ); Tue, 6 May 2003 11:37:55 -0400 Date: Tue, 6 May 2003 11:50:22 -0400 (EDT) From: Bill Davidsen X-X-Sender: root@oddball.prodigy.com Reply-To: Bill Davidsen To: Linux Kernel Mailing List Subject: X unlock bug revisited Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 607 Lines: 12 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. - 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/