Bug 342498 - akonadi_archivemail_agent crashed while archiving shortly befor ending
Summary: akonadi_archivemail_agent crashed while archiving shortly befor ending
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Archive Mail Agent (show other bugs)
Version: 1.12.91
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 356641 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-01-05 07:08 UTC by Foli Ayivoh
Modified: 2021-01-16 04:34 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
akonadi_archivemail_agent crash backtrace (8.17 KB, text/plain)
2015-01-05 07:16 UTC, Foli Ayivoh
Details
stack backtrace (2.72 KB, text/plain)
2016-01-06 19:48 UTC, quazgar
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Foli Ayivoh 2015-01-05 07:08:45 UTC
i was setting up archiving of my local mail folder (maildir) with all it's subfolders daily. I started archiving at once and it started immediatly archiving and everything seemed working fine. The archiving must have crashed shortly before ending of the archiving!

Reproducible: Didn't try

Steps to Reproduce:
1. configure and starting archiving
2. 
3.

Actual Results:  
crash shortly before ending

Expected Results:  
finish the archiving

lacal mail folder (maildir) with about 1000+ subfolders and about 10GB in size (all files)
target folder (partition) has about 200+GB of space
Comment 1 Foli Ayivoh 2015-01-05 07:16:58 UTC
Created attachment 90225 [details]
akonadi_archivemail_agent crash backtrace
Comment 2 Laurent Montel 2015-01-05 07:40:51 UTC
kdepim version ?
Comment 3 quazgar 2016-01-06 19:46:25 UTC
Still reproducibly happening with 4.14.10 here, I'll also attach a stack trace. Please ask if you need more info.
Comment 4 quazgar 2016-01-06 19:48:02 UTC
Created attachment 96490 [details]
stack backtrace
Comment 5 quazgar 2016-01-22 14:22:53 UTC
*** Bug 356641 has been marked as a duplicate of this bug. ***
Comment 6 quazgar 2016-01-22 14:52:03 UTC
Tried to reproduce this bug again, this is the final output of ~/.xsession-errors while attempting to archive my folders:

[...]
request for item 414095 still pending - waiting 
processing retrieval request for item 414095  parts: ("RFC822", "HEAD")  of resource: "akonadi_maildir_resource_4" 
AkonadiAgentServer(10778)/libakonadi Akonadi::ProtocolHelper::streamPayloadToFile: Wrote 4649 bytes to  "/home/daniel/.local/share/akonadi/file_db_data/1218380_r0"
AkonadiAgentServer(10778)/libakonadi Akonadi::ProtocolHelper::streamPayloadToFile: Wrote 150675 bytes to  "/home/daniel/.local/share/akonadi/file_db_data/1218382_r0"
continuing 
request for item 414095 succeeded 
posting retrieval request for item 391868  there are  1  queues and  0  items in mine 
request for item 391868 still pending - waiting 
processing retrieval request for item 391868  parts: ("RFC822")  of resource: "akonadi_maildir_resource_4" 
AkonadiAgentServer(10778)/libakonadi Akonadi::ResourceBase::itemRetrieved: Item does not provide part "RFC822" 
continuing 
request for item 391868 succeeded 
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

terminate called after throwing an instance of 'Akonadi::PayloadException'
  what():  Akonadi::PayloadException: No payload set
*** KMail got signal 6 (Exiting)
*** Dead letters dumped.
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kontact_11264_X0YXm4" now serving: () 
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kontact_11264_wTRcqn" now serving: () 
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kontact_11264_T01n8A" now serving: () 
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kontact_11264_iGr6wD" now serving: () 
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kontact_11264_HTgoVp" now serving: () 
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kontact_11264_AmzoWS" now serving: () 
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kontact_11264_89NJiO" now serving: () 
void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification source "kontact_11264_MP4qJA" now serving: () 
KCrash: Application 'kontact' crashing...
KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit
KCrash: Connect sock_file=/home/daniel/.kde4/socket-droggelbecher/kdeinit4__0
Comment 7 Justin Zobel 2020-12-17 05:27:01 UTC
Thank you for the crash report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 8 Bug Janitor Service 2021-01-01 04:35:02 UTC
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
mark the bug 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!
Comment 9 Bug Janitor Service 2021-01-16 04:34:18 UTC
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!