[Konsole-devel] Bug#42362: running "kdeinit konsole" crashes

[Ladislav.Strojil at seznam.cz]

Package: konsole
Version: 1.1.1 (using KDE 3.0.1 (CVS >= 20020327))
Severity: normal
Installed from:    compiled sources
Compiler:          gcc version 2.95.3 20010315 (release)
OS:                Linux (i686) release 2.4.8-26mdk
OS/Compiler notes: 

Hi,

I just noticed that I cannot run konsole from kicker anymore (KDE3.0.1 from CVS). It is still possible to run konsole from the Alt-F2 windows. 
Looking into this further, I found out that the reason is kdeinit. When I run "kdeinit konsole" from command line I get following output:
[lada at smrz ~]$ kdeinit konsole                                                                                  [~ 10:21 0]
kdeinit: Shutting down running client.
kdeinit: Launched DCOPServer, pid = 2455 result = 0
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /home/lada/.DCOPserver_smrz.kolej.mff.cuni.cz__0
and start dcopserver again.
---------------------------------

kdeinit: Launched KLauncher, pid = 2456 result = 0
kdeinit: Launched KDED, pid = 2458 result = 0
KDE Daemon (kded) already running.
kio (KLauncher): KLauncher: Got kdeinit_exec_wait('kbuildsycoca', ...)
kdeinit: Got EXEC_NEW 'kbuildsycoca' from launcher.
kio (KLauncher): kbuildsycoca (pid 2460) up and running.
kbuildsycoca: Recreating ksycoca file
kbuildsycoca: Database is up to date
kdeinit: PID 2460 terminated.
kdeinit: PID 2458 terminated.
kdeinit: opened connection to :0.0
kdeinit: Launched 'konsole', pid = 2461 result = 0
KCrash: crashing.... crashRecursionCounter = 2                                                   
KCrash: Application Name = konsole path = <unknown> pid = 2461
kdeinit: PID 2461 terminated.

But no crash window is displayed. Furthermore, "kdeinit konsole" is still running. It is not eating excesive CPU cycles, it just sits there. :-)

This is perfectly reproducible, happens every time.

Other applications start OK with kdeinit that is why I report this as a bug in konsole, not kdeinit.

Cheers,
Lada

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)