Summary: | Crash when manipulating an Akonadi KOrganizer event [qDeleteAll<KIO::SchedulerPrivate::ProtocolInfoDict>, ~SchedulerPrivate, destroy] | ||
---|---|---|---|
Product: | [Applications] kontact | Reporter: | Marcus Harrison <marcus> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra |
Priority: | NOR | ||
Version: | 4.4 pre | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Marcus Harrison
2009-12-28 17:25:43 UTC
The backtrace's functions seems related to bug 199375 (which seems to be a KMail bug). Did you used KMail during the same session? Unfortunatelly the backtrace was corrupted by a bug in the crash reporting tool (which was quickly fixed). It would be useful if we could generate a new backtrace if you could repeat the crash/hang situation. Regards Actually, it appears that KOrganizer doesn't freeze or crash when called as an independent module, so it could be related to KMail - though I don't see how: I hadn't interacted with KMail during the session. Though, KMail does a few actions automatically, such as checking mail and applying filters. Then this is bug 199375 Thanks *** This bug has been marked as a duplicate of bug 199375 *** |