| Summary: | [abrt] evolution-2.32.2-1.fc14: ____strtoul_l_internal: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | a.lathrop | ||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | lucilanga, mbarnes, mcrha | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | abrt_hash:1e88113c5ba0418b70fffd26b7e259944ea7cd8c | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-04-12 05:03:25 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
a.lathrop
2011-04-11 11:06:24 UTC
Created attachment 491203 [details]
File: backtrace
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate. A reason is that the folders.db file has stored incorrect values in one of tables, in your case for your IMAP account. Because all the information for IMAP accounts is stored on the server, then you can safely move away whole ~/.local/share/evolution/mail/imap/<account> and tun evolution again, which will recreate it. The disadvantage is, unfortunately, that it'll "forget" all downloaded messages, thus will redownload them again. The other option is to examine ~/.local/share/evolution/mail/imap/<account>/folders.db file and delete all rows which has probably UID column set to NULL. See the original bug for more information about this. *** This bug has been marked as a duplicate of bug 672369 *** |