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.
--
bill davidsen <[email protected]>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
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.
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.
I think the kernel told KDE something it didn't want to hear, so to speak.
--
bill davidsen <[email protected]>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
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
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
In article <20020117025432.INGX20810.femail29.sdc1.sfba.home.com@there> you write:
| On Wednesday 16 January 2002 12:20 pm, Bill Davidsen wrote:
| > 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...)
Haven't changed the name this millenium. This is my personal box I use
to monitor systems at a site, and while it's not critical it's
production (which is why I can play). Didn't know that was a problem,
but I'd be unlikely to rename from X if I had to.
If restarting KDE would have fixed it I would ignore the issue (once),
but no new KDE start did any good until a reboot.
--
bill davidsen <[email protected]>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.