Bug#36881: marked as done (Program unuseable/unrecoverable after changing the user-interface) by Falk Brettschneider <gigafalk at yahoo.com>

Stephan Kulow owner at bugs.kde.org
Sat Jan 12 13:49:02 UTC 2002

Your message with subj: such unprecice description is useless for us developers, everything can't be reproduced

Michael Uplawski wrote:

>The situation has not improved. But after uninstalling KDE and a
>complete reinstallation (with SuSE-RPMs), the window-layout is back
>to normal. 
>Only now, _everything_ needs too much time. Clicking a menu-item,
>clicking an icon in the task-bar, navigation btw. files... halts
>KDevelop for an unbearable long time.
>This won't work for me.

Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 6 Jan 2002 11:58:40 +0000
Received: (qmail 21209 invoked by uid 33); 6 Jan 2002 11:58:40 -0000
Date: 6 Jan 2002 11:58:40 -0000
Message-ID: <20020106115840.21208.qmail at master.kde.org>
To: submit at bugs.kde.org
Subject: Program unuseable/unrecoverable after changing the user-interface
From: uplawski at quercus.franken.de

Package:           kdevelop
Version:           2.0.2 (using KDE 2.2.2 )
Severity:          normal
Installed from:    Unspecified Linux
Compiler:          gcc-2.95.3
OS:                Linux
OS/Compiler notes: SuSE-RPM or Compiled from source , same effect

I wanted to test a different window-layout 
with KDevelop 2.0.2. This was the first time,
I tried the midi-window layout.

As it was not very useful to me, I tried to
set it back to tabbed view. This did not work
as expected. I am still left with two separate
windows (not midi but toplevel-windows, 

1. Those windows cannot be combined into one,
neither by repeatedly using the configuration
dialog, nor by drag&drop.

2. Loading source-code files takes too much
time, now and sometimes KDevelop crashes.

3. Loading another project crashes the 
application. I just do it... load one project.
Load another one. Okay, here is my first
crash-report for today:
0x4136b5a9 in __wait4 () from /lib/libc.so.6
#0  0x4136b5a9 in __wait4 () from /lib/libc.so.6
#1  0x413d3ad8 in __DTOR_END__ () from /lib/libc.so.6
#2  0x411d5495 in KCrash::defaultCrashHandler ()
   from /opt/kde2/lib/libkdecore.so.3
#3  <signal handler called>

4. Upon quitting, the Application crashes.
To deliver the (will-be) attached crash-report
I go _now_ to the application, and simply
quit it... just so.
Et voilà, crash-report #2:
0x4136b5a9 in __wait4 () from /lib/libc.so.6
#0  0x4136b5a9 in __wait4 () from /lib/libc.so.6
#1  0x413d3ad8 in __DTOR_END__ () from /lib/libc.so.6
#2  0x411d5495 in KCrash::defaultCrashHandler ()
   from /opt/kde2/lib/libkdecore.so.3
#3  <signal handler called>

Do I have to say, that these are 
reproduceable? And they are, after I have
_uninstalled_ kdevelop and reinstalled it
again!! Irrespective of the 

And now I have no working IDE. 

PSE gimme a tipp, I am lost.

(Submitted via bugs.kde.org)

More information about the KDevelop-devel mailing list