| Summary: | Random crashes in Kontact, hard to relaunch afterwards (backtrace included) | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | Thibaut Cousin <kde> |
| Component: | general | Assignee: | Thibaut Cousin <kde> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | backtrace of kontact crash | ||
|
Description
Thibaut Cousin
2006-01-24 20:57:13 UTC
I think I have narrowed down the problem. Akregator seems to be the cause. After a hard crash of my computer, Kontact would refuse to start again (crash at launch). I found that KMail could start standalone, but not Akregator. When I removed the ~/.kde/share/apps/akregator folder, Kontact would start again normally and never crash again. But when I started to use Akregator again, starting from a new clean configuration, Kontact started to crash again at random, every once in a while. Perhaps the crash is caused by an RSS feed that Akregator doesn't like. But as I have many RSS feeds, it will take time to find which one is the problem. In any case, Akregator shouldn't react to a bad RSS feed by crashing, obviously... and taking the whole Kontact with it. I forgot to mention that since comment #1, I upgraded to OpenSUSE 10.1 and KDE 3.5.2. Even starting everything from a clean configuration (I didn't reuse my old .kde folder), the problem was still there. Created attachment 16254 [details]
backtrace of kontact crash
|