On Tuesday 19 November 2002 02:54 pm, KMcLauchlan@chrysalis-its.com wrote:
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:
******************** (snip)
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
--------------------------------- Hi Kevin, Run kmail from the shell/console. This should give you more info about what you are running in too on the crashes. If kmail is running ok from the new user you have created, then my guess is your system is ok overall, but your user has got some things out of whack. Most likely a config file somewhere. Have you tried renaming your /home/<user>/.kde directory to something else and letting the whole thing be created new to see if that takes care of the problem? I guess it could be one of those MCOP or DCOP thingys too. As you can tell, thingys is very technical talk. ;o) Oh, do you ever write brief emails or does your technical writing or whatever writing you do get in the way most times? :o) Patrick --- KMail v1.4.3 --- SuSE Linux Pro v8.1 --- Registered Linux User #225206