From: Hans-Christian Armingeon <linux.johnny@gmx.net>
To: Bill Davidsen <davidsen@tmr.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: KDE hang with 2.4.18-pre3-ac2
Date: Wed, 16 Jan 2002 18:00:31 +0100 [thread overview]
Message-ID: <16QsTK-0yvhtAC@fmrl10.sul.t-online.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1020116103205.28369E-100000@gatekeeper.tmr.com>
In-Reply-To: <Pine.LNX.3.96.1020116103205.28369E-100000@gatekeeper.tmr.com>
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.
Johnny
Am Mittwoch, 16. Januar 2002 16:37 schrieb Bill Davidsen:
> I got an interesting symptom on the first machine I tried using the new
> -ac2 kernel. The KDE bar wouldn't launch any applications. The rest of the
> system was running just fine, applications running, `sessions' starting
> connections to various machines, mail going along, but KDE just didn't
> start apps, with no errors.
>
> After reboot all was fine, restarting KDE didn't change anything.
>
> I mention this only as something people might shrug off otherwise, but
> this KDE hasn't done that, and it's an old one from Slack7.0. Can't
> replicate otherwise, this is not a bug report proper or not, just
> something to notice. If restarting KDE fixed it I'd say it was a KDE bug,
> but it didn't.
next prev parent reply other threads:[~2002-01-16 16:00 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 [this message]
2002-01-16 17:20 ` Bill Davidsen
2002-01-16 18:52 ` Rob Landley
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=16QsTK-0yvhtAC@fmrl10.sul.t-online.com \
--to=linux.johnny@gmx.net \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
/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®