Does anybody have a suggestion, please? I've been using SuSE 8.0 and KDE3 and KMail for a year at my office. I shut down (in orderly fashion) on a Friday evening and then booted on the Monday after the weekend. I got into KDE 3.0.4 with no problems, and then tried to start KMail. After some effort, the system responds with the you've-got-a problem dialog, saying that KMail has failed with signal 11 SIGSEGV. I clicked the "Backtrace" tab, and got the following: ******************** (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1024 (LWP 1762)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x413b5099 in wait4 () from /lib/libc.so.6 #0 0x413b5099 in wait4 () from /lib/libc.so.6 #1 0x4142fbd8 in __DTOR_END__ () from /lib/libc.so.6 #2 0x4128d072 in waitpid () from /lib/libpthread.so.0 #3 0x40a350de in KCrash::defaultCrashHandler () from /opt/kde3/lib/libkdecore.so.4 #4 0x4128aa74 in pthread_sighandler () from /lib/libpthread.so.0 #5 <signal handler called> #6 0x0811a539 in KDialog::marginHint () #7 0x084ed820 in ?? () #8 0x08128cb0 in KDialog::marginHint () #9 0x08128d10 in KDialog::marginHint () #10 0x08128d10 in KDialog::marginHint () #11 0x08128d10 in KDialog::marginHint () #12 0x08128d10 in KDialog::marginHint () #13 0x08119abb in KDialog::marginHint () #14 0x081a05a4 in KDialog::marginHint () #15 0x081a4334 in KDialog::marginHint () #16 0x4132a9ed in __libc_start_main () from /lib/libc.so.6 ******************** I have not tried every other application on my system, but those that I have been using don't seem to be broken... Anybody interpret what's wrong, here? Or, is there a HowTo or a website that can tell me how to interpret the above output? Meanwhile, I have done the following: - ran YOU, which reported that the most recent previous update had been 17 days ago - tried KMail again -- same symptoms. - re-installed kdenetworks and related pkgs, and then ran YOU again -- same symptoms (similarly after restarting X again). - created another user on my system -- KMail starts for that user, but of course does nothing because the user doesn't have a mail account on our company server... still, the program starts with no reported error - moved my own /home/kmclauchlan/Mail directory and it's subdirectories to a temp directory - tried starting KMail again -- no change - copied the virgin, empty /Mail directory structure from the "Otherguy" user into my home directory started KMail and it failed as usual with SIGSEGV before opening I'm baffled as to where to look. Why would the ONE program be segfaulting? How do you trace to see what it wants, that it's not getting? I didn't see any log files in /var/log that seemed to be KDE-related. (But, I'm getting crosseyed by now.) Does anybody know a good HowTo on "debugging Kommercial apps for Dummies" ?? Is anybody using directories with KMail, rather than MBOX? I was told, last year that this was preferable due to the server I'm connected to. I don't recall the reasoning. To re-iterate, everything has been working for months with no problem, right up until that Friday at 17h30. The next Monday morning... suddenly a problem. I have never run apt-get on this system. Only YOU. Hints? Suggestions? Some suggested reading? Thank you. /kevin