Bug 242056

Created attachment 48111 [details]
New crash information added by DrKonqi

Additional info:

After working for a short while, I went to sleep.   I awoke with the error message showing (crash handler) so I was doing nothing when this error occured.   I still suspect that it crashed during a routine poll of mail or perhaps not the poll itself but if a message came in for processing because I did notice successful polls earlier but I didn't remember receiving new messages.

Created attachment 48295 [details]
New crash information added by DrKonqi

Since the original report, I did a CLEAN INSTALL of 11.3 rc1 (SuSE) and the symptom is the same.   I then upgraded to KDE:factory 4.4 KMail and again the symptom is the same.   The error appears to occur when polling the openSuSE mailing list off of Gmail after importing a few hundred messages.   I also have other servers I subscribe to for other mail that (so far) have not exhibited this crash but I can't be sure as occasionally several threads are downloading at once when it crashes but I have attempted to disable polling of other servers and it seems it is coming from Gmail from which I only get openSuSE and related mailing lists.   I do my best to not use it for personal mail and I do have their spam checker turned on so I normally see little or no junk mail coming in.   A side effect of this is that I cannot read *any* mail and all mail is reloaded each time I restart the PIM OR KMail by itself.   This problem did NOT exist prior to upgrading to RC1

Additional information:

I removed the spam checker and bogofilter - no effect.   Then I turned off ALL mail servers except GMAIL - No effect.   Then I logged into GMAIL via webmail and started deleting messages.   I deleted 100 at a time (there were 408 initially and all were one of the openSuSE mail lists as far as I could tell) and until I deleted 400 of them, there was no effect.   I don't know which message was tripping up Kmail, but it accepted the last 8 messages.   I have no way to tell which message was the problem, but I do know that nothing related to spam checking made a difference, nor did changing from rc1 to 4.4.5 factory (guess it was (hard to tell exactly what KDE:factory had that was different than the DVD)) but that didn't make a difference.   It was definitly DATA related which means that it can occur again in the future and the data came from openSuSE mailing list via GMAIL.   The first occurance of the bug was after an UPDATE install of RC1, the 2nd was after a CLEAN INSTALL, the 3ird was after updating to KDE:factory version of KMail and PIM. (FWIW)

I subscribe to opensuse KDE factory project buildservice packaging zypper buglists (which seemed to be being updated when crashing) and pacman which was not being updated as far as I could tell nor was it after the error stopped occurring after deleting 400 messagess from Gmail.)_

Created attachment 48316 [details]
New crash information added by DrKonqi

Was reading mail when an automatic scheduled mail poll occurred to GMAIL.com  

I had many successful polls after deleting (via web) messages from GMAIL(pop3), but apparantly a message has come in that has triggered this failure again.

Created attachment 48505 [details]
New crash information added by DrKonqi

This most recent failure occured after update to RC2 update.   I have done fsck on the system with badblocks check to ensure disk integrity, expired and compacted all folders and deleted messages in the maillists that are associated with GMail to no avail.   It will poll and even download messages for a short while, but after a short period of time (with or without other system activities), the error will occur, even if I am just sitting there doing nothing except wondering how long this time....   not even moving the mouse.   This error has persisted through 2 different kernel updates, even an update to/from the KDE factory repository for the latest.  I have performed memory checks lasting overnight, done badblock checks on the drives, etc.   The only thing that makes this system 'unusual' is that I use both LVMs and RAIDs on this system, BUT I have done so for a very long time, predating the onset of this error.   Again, this error suddenly started after an update of my system from openSuSE milestone 7 to RC1, and it was immediate, meaning the first error was noticed within minutes of starting Kontact/Kmail, eg, on the first poll of Gmail.com.   I can turn off GMail.com polls and leave the polls to the other servers and (so far) there have been NO other failures.   If there is no mail at Gmail.com, the error does not occur, so the poll itself does not seem to be the cause, only the processsing of the incoming mail.   As Gmail is where the most traffic comes from, that does increase the odds of a processing error, but I do have one other server with high traffic (several hundred messages/24hrs) that does not seem to trigger this failure (so far).

Created attachment 49311 [details]
New crash information added by DrKonqi

This system has been updated to 11.3 GM

Additionally, I am using KDE repos (factory) and 4.4.5 versions

This problem persists and on occasion will fail if even ONE message comes from gmail.com maillists, but NEVER from any other source regardless of how many messages are processed.   It therefore seems impossible to continue to use KMail much longer as this report seems to not have been addressed, or even looked at as far as I can tell.

I have tried badblocks (zero detected), fsck, (nothing detected), erasing all messages (no effect), expiring all folders (no effect), compacting all folderss (sometimes seems to help some but very seldom), memtest for 24hrs (no errors detected), AMD dual core w/3g ram 2g swap (which is never touched).

Please!!!!

SVN commit 1170898 by mlaurent:

Just a workaround for #242056
Need more info about it
CCBUG: 242056


 M  +3 -1      kmaccount.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1170898

Your email from gmail is moving from filter.
Could you give me info about it ?

For the moment I just fix crash but not fixed bug.
I need more info.
I can't reproduce here.

Thanks 
Regards.

(In reply to comment #8)
> Your email from gmail is moving from filter.
> Could you give me info about it ?
> 
> For the moment I just fix crash but not fixed bug.
> I need more info.
> I can't reproduce here.
> 
> Thanks 
> Regards.

I'm not sure what you mean by mail from gmail is moving from filter....   You mean the crash is occuring on a filter?   If so, the filter simply sees that the mail is 


[Filter #28]
Applicability=0
AutomaticName=false
ConfigureShortcut=false
ConfigureToolbar=false
Icon=
StopProcessingHere=true
ToolbarName=<List-Post>:<mailto:opensuse@opensuse.org>
accounts-set=
action-args-0=.Mail Lists.directory/.MiscLists.directory/OpenSuSE
action-name-0=transfer
actions=1
apply-on=check-mail,manual-filtering
contentsA=<mailto:opensuse@opensuse.org>
fieldA=List-Post
funcA=contains
name=<List-Post>:<mailto:opensuse@opensuse.org>
operator=and
rules=1


and moves it to the appropriate folder.

I have many other folders, many also from Gmail, some from other servers, none but this one ever caused the fault.

I updated KDEPIM to 4.4.5 from WIL's git and the problem went away.  I then 'upgraded' to the latest in the KDE repo, overwriting Wil's version, but the problem didn't reoccur.   I had reindexed the folder, even deleted all messages and let it rebuild starting with zero messages and the errors persisted until I used Wil's version which stopped it cold.   I restored a backup of about 10000 messages and imported them into the inbox and applied the filters again and they all went through and ended up in the right folders.   

I can't reproduce the error anymore so I guess I must have gotten your 'fix' either from Will or from one of the repo updates.  

Now if you can fix the Contacts dying  when updating the data in a custom field :)   It does update, but you have to restart Kontact and find the contact you were editing to see the change 'took'.   No error message, just goes away...

Thanks
Richard

*** Bug 252057 has been marked as a duplicate of this bug. ***