From: Rob Landley <landley@trommello.org>
To: Bill Davidsen <davidsen@tmr.com>,
Hans-Christian Armingeon <linux.johnny@gmx.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: KDE hang with 2.4.18-pre3-ac2
Date: Wed, 16 Jan 2002 13:52:29 -0500 [thread overview]
Message-ID: <20020117025432.INGX20810.femail29.sdc1.sfba.home.com@there> (raw)
In-Reply-To: <Pine.LNX.3.96.1020116121752.28369J-100000@gatekeeper.tmr.com>
In-Reply-To: <Pine.LNX.3.96.1020116121752.28369J-100000@gatekeeper.tmr.com>
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...)
Rob
next prev parent reply other threads:[~2002-01-17 2:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 15:37 Bill Davidsen
2002-01-16 17:00 ` Hans-Christian Armingeon
2002-01-16 17:20 ` Bill Davidsen
2002-01-16 18:52 ` Rob Landley [this message]
2002-01-17 14:42 ` Hans-Christian Armingeon
2002-01-17 17:01 ` bill davidsen
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=20020117025432.INGX20810.femail29.sdc1.sfba.home.com@there \
--to=landley@trommello.org \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.johnny@gmx.net \
/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®