GNOME Bugzilla – Bug 594756
Crash on start in *__GI_____strtoul_l_internal()
Last modified: 2010-12-09 09:31:54 UTC
I've had problems with a message that would not load, with an error like "could not load message: could not find main part in FETCH response". Then I got a crash. Now I can't even start Evo, the crash always occurs on start (I'll try some tests, like disconnecting my computer - I guess I'll get rid of it some way). Reported on: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/427410
+ Trace 217474
Created attachment 142919 [details] CAMEL_DEBUG=all log of the crash (I've replaced personal identifiers by something like user@server.com.)
After starting it again in calendar mode (using '-c calendar') and quickly changing mail folder, I was able to get it working. Without changing folder, it was still crashing when going to mail mode. Offline/Online did not change anything. Now I can read all my mail folders. Some interesting messages have appeared that are not in the previous log, but they appeared when crashing as well as now, when it's working: [...] ** (evolution:6785): DEBUG: EI: SHELL STARTUP camel-imap-provider-Message: Unable to load summary: no such table: INBOX/DRAFT camel-imap-provider-Message: Unable to load summary: no such table: INBOX/QUARANTAINE camel-imap-provider-Message: Unable to load summary: no such table: INBOX/Listes camel-imap-provider-Message: Unable to load summary: database disk image is malformed camel-imap-provider-Message: Unable to load summary: no such table: INBOX/TRASH camel-imap-provider-Message: Unable to load summary: no such table: INBOX/QUARANTAINE camel-imap-provider-Message: Unable to load summary: no such table: INBOX/TRASH camel-imap-provider-Message: Unable to load summary: database disk image is malformed camel-imap-provider-Message: Unable to load summary: no such table: INBOX/Listes camel-imap-provider-Message: Unable to load summary: no such table: INBOX/DRAFT Segmentation fault
*** Bug 595172 has been marked as a duplicate of this bug. ***
*** Bug 595169 has been marked as a duplicate of this bug. ***
*** Bug 595173 has been marked as a duplicate of this bug. ***
*** Bug 595224 has been marked as a duplicate of this bug. ***
*** Bug 595225 has been marked as a duplicate of this bug. ***
*** Bug 601988 has been marked as a duplicate of this bug. ***
*** Bug 601987 has been marked as a duplicate of this bug. ***
This seems to be just a different variation of bug #573125. In this case the integer field value is going to be transformed from a string to int, but because the value in the column is NULL (not an empty string), instead of a number, it crashes. The above bug contains patch which will fix this, same as some workaround steps how to fix the issue.
*** This bug has been marked as a duplicate of bug 573125 ***