On Mon, Nov 06, 2000 at 12:08:03AM +0000 or thereabouts, Hadess wrote: > Well then just launch the app from the command-line and check if the pb > is the same !
Thanks for making me feel dumb (hm, studying for those exams must have made my mind go away...) ;) But that still wouldn't excuse the existence of the problem... and it still happens even if I launch from the command line. 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> Thanks, Patrix. -- "No boom today. Boom tomorrow. There's always a boom tomorrow." -- Lt. Cmdr. Susan Ivanova, Babylon 5. "It's the Magic that counts." -- Larry Wall on Perl's apparent ugliness.
