Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263893AbTEFPrK (ORCPT ); Tue, 6 May 2003 11:47:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263898AbTEFPrK (ORCPT ); Tue, 6 May 2003 11:47:10 -0400 Received: from air-2.osdl.org ([65.172.181.6]:52679 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S263893AbTEFPrI (ORCPT ); Tue, 6 May 2003 11:47:08 -0400 Date: Tue, 6 May 2003 08:56:23 -0700 From: "Randy.Dunlap" To: Bill Davidsen Cc: linux-kernel@vger.kernel.org Subject: Re: X unlock bug revisited Message-Id: <20030506085623.4fe97953.rddunlap@osdl.org> In-Reply-To: References: Organization: OSDL X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i586-pc-linux-gnu) X-Face: +5V?h'hZQPB9kW Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 860 Lines: 20 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. -- ~Randy - 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/