Summary: | Akonadi imap crash [KMime::Content::hasContent, Akonadi::SerializerPluginMail::parts, Akonadi::ItemSerializer::parts] | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Robet Piasek <dagger> |
Component: | IMAP resource | Assignee: | Christian Mollekopf <chrigi_1> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andysem, crglasoe, kdepim-bugs, mbriza, vkrause |
Priority: | NOR | Keywords: | triaged |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Robet Piasek
2011-06-09 12:08:44 UTC
It seems network connectivity change has nothing to do with it. It just randomly crashed few more times with same backtrace as above. (In reply to comment #1) > It seems network connectivity change has nothing to do with it. It just > randomly crashed few more times with same backtrace as above. If this crash is still reproducible, please rebuild kdepimlibs and kdepim-runtime in debug mode to get a better backtrace. *** Bug 289692 has been marked as a duplicate of this bug. *** *** Bug 289929 has been marked as a duplicate of this bug. *** from bug 289692 I have been experiencing this crash since updating to 4.7.2 The migration to Kmail2 was troublesome. Only one imap account is causing this error. The crash can be reproduced every time. -- from bug 289929 I don't know what is happening. This really is getting annoying. I fire Kontact/Kmail and without any prompting I receive this crash. Can I repeat it? No. Does it repeat? Yes. Randomly. This is not the place to add rants, I know. But this implementation of Kmail or Akonadi really is poor. It casts a very bad light on all of the Open Source community. It makes all of us lobbying and supporting Open Source look like fools for using something that simply does not work. The crash can be reproduced every time. As this seems reproducible for you, please install the debug package for kdepimlibs to get a better backtrace Created attachment 68700 [details]
New crash information added by DrKonqi
akonadi_imap_resource (4.8) on KDE Platform 4.8.00 (4.8.0 "release 2" using Qt 4.8.0
My akonadi IMAP resource crashed in background. I suspect, there were connectivity issues involved (possibly, a socket operation timed out) because I have a torrent client active.
-- Backtrace (Reduced):
#6 Akonadi::ItemSync::setFullSyncItems (this=0x0, items=...) at /usr/src/debug/kdepimlibs-4.8.0/akonadi/itemsync.cpp:145
#7 0x00007f97264d7e52 in Akonadi::ResourceBase::itemsRetrieved (this=<optimized out>, items=...) at /usr/src/debug/kdepimlibs-4.8.0/akonadi/resourcebase.cpp:901
[...]
#10 0x00007f97249f8b44 in KIMAP::FetchJob::headersReceived (this=<optimized out>, _t1=<optimized out>, _t2=<optimized out>, _t3=<optimized out>, _t4=<optimized out>, _t5=<optimized out>) at /usr/src/debug/kdepimlibs-4.8.0/build/kimap/fetchjob.moc:115
#11 0x00007f9724a1bcf8 in KIMAP::FetchJobPrivate::emitPendings (this=0x7c2820) at /usr/src/debug/kdepimlibs-4.8.0/kimap/fetchjob.cpp:57
#12 0x00007f9724a1348b in KIMAP::FetchJob::handleResponse (this=0x8c2030, response=...) at /usr/src/debug/kdepimlibs-4.8.0/kimap/fetchjob.cpp:236
This bug is also reported in the Red Hat Bugzilla for Fedora 16 (KDE SC 4.7.4) on https://bugzilla.redhat.com/show_bug.cgi?id=794785 . The IMAP resource has a new maintainer, reassigning to him. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |