Bug 352105 - KMail 4.14.9: dumpDeadLetters after sending a large file
Summary: KMail 4.14.9: dumpDeadLetters after sending a large file
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: 4.14.7
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-01 16:08 UTC by Axel Braun
Modified: 2017-06-29 14:55 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Startup-messages (25.37 KB, text/plain)
2015-09-01 16:10 UTC, Axel Braun
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Axel Braun 2015-09-01 16:08:11 UTC
After sending a (way too large) file by Email Kmail crashes and does not come up again, Find the startup messages in the attachment.
The important part may be:
akonadi_imap_resource_0(26309)/libakonadi Akonadi::CollectionSync::Private::findUnprocessedLocalCollections: Collection ID: 125    remote ID: "" 
   name: "Gesendet" 
   url: KUrl("akonadi://?collection=125") 
   parent: 18 "imap://judith@xxxx.de@imap.xxxx.de/" 
   resource: "akonadi_imap_resource_0" 
   rights: QFlags(0x1|0x2|0x4|0x8|0x10|0x20) 
   contents mime type: ("inode/directory") 
   isVirtual: false 
    CachePolicy:  
   inherit: true 
   interval: 5 
   timeout: -1 
   sync on demand: true 
   local parts: ("ENVELOPE", "HEAD", "RFC822") 
    CollectionStatistics: 
   count: -1 
   unread count: -1 
   size: -1 

As a short term solution , is there any way I can get rid of the damaged mail?

Reproducible: Always

Steps to Reproduce:
1. start KMail
2.
3.
Comment 1 Axel Braun 2015-09-01 16:10:20 UTC
Created attachment 94324 [details]
Startup-messages

when starting KMail from the command line
Comment 2 Denis Kurz 2017-06-23 20:21:29 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Axel Braun 2017-06-29 14:54:22 UTC
can not reproduce in 5.5.2
Comment 4 Axel Braun 2017-06-29 14:55:08 UTC
Seems to work in latest KMail 5.5.2, closing