Patrice LaFlamme wrote: > But that still wouldn't excuse the existence of the problem... and it still > happens even if I launch from the command line.
That's to be expected. But does it also happen with WindowMaker like this. > Here's a sample backtrace (when kcontrol crashes) > > (no debugging symbols found)... 0xefbbad0 in wait4 () from /lib/libc.so.6 > #0 0xefbbad0 in wait4 () from /lib/libc.so.6 > #1 0xefbba84 in waitpid () from /lib/libc.so.6 > #2 0xfb16fbc in KCrash::defaultCrashHandler () from > /usr/lib/libkdecore.so.3 > #3 <signal handler called> Nothing below (and above)? This is only the part from the KDE signal handler, which doesn't give any information about the cause of the crash... Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and the DRI project
