Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 17 Jan 2002 08:42:48 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 17 Jan 2002 08:42:39 -0500 Received: from mailout09.sul.t-online.com ([194.25.134.84]:20190 "EHLO mailout09.sul.t-online.com") by vger.kernel.org with ESMTP id ; Thu, 17 Jan 2002 08:42:29 -0500 Content-Type: text/plain; charset=US-ASCII From: Hans-Christian Armingeon To: Rob Landley , Bill Davidsen Subject: Re: KDE hang with 2.4.18-pre3-ac2 Date: Thu, 17 Jan 2002 15:42:46 +0100 X-Mailer: KMail [version 1.3.2] Cc: Linux Kernel Mailing List In-Reply-To: <20020117025432.INGX20810.femail29.sdc1.sfba.home.com@there> In-Reply-To: <20020117025432.INGX20810.femail29.sdc1.sfba.home.com@there> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-ID: <16RCnC-1cbySmC@fmrl11.sul.t-online.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Am Mittwoch, 16. Januar 2002 19:52 schrieb Rob Landley: > On Wednesday 16 January 2002 12:20 pm, Bill Davidsen wrote: > > On Wed, 16 Jan 2002, Hans-Christian Armingeon wrote: > > > I've got the same problems with SuSE7.3 and kde2.2.2. > > > With kernel 2.4.17, the X locks up, when I push the power button, the > > > box tries to shut doen [I can hear a beep], but nothing else happens. > > > After two or three sysrq keys specally sigterm to all processes, the > > > system locks hard [reset cycle needed]. I am trying 2.4.18-pre4 now. > > > > Totally other problem. When my KDE won't launch tasks from the bar, it > > will still work just fine otherwise, shutdown cleanly, etc. System is not > > in any way hung, just that clicking the browser or terminal button > > doesn't start a process, and if I bring up a menu from the bar, and try > > to start something like moon phase, it also doesn't start. > > Question: did you change your computer's hostname just before this > happened? (That can trigger this behavior. When you change your box's > hostname, you have to exit and restart X. If you ask me, it's a design > flaw in X, which thinks it's doing stuff through the network even when it > isn't. KDE isn't helping by cacheing stuff, but it's going for > performance...) No, I didn't. Johnny > > Rob - 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/