Bug 684236 - [abrt] evolution-2.30.3-1.fc13: ____strtoul_l_internal: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.30.3-1.fc13: ____strtoul_l_internal: Process /usr/bin/evol...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e15d5360e20247b3426698f2505...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-11 14:44 UTC by Timothy Ward
Modified: 2011-03-11 16:47 UTC (History)
3 users (show)

Fixed In Version: evolution-data-server-2.91.91
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-11 16:47:54 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (39.37 KB, text/plain)
2011-03-11 14:44 UTC, Timothy Ward 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Timothy Ward 2011-03-11 14:44:47 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: evolution
comment: This is the first open since moving a lot of emails from inbox to various folders within evolution for storage and backup.
component: evolution
crash_function: ____strtoul_l_internal
executable: /usr/bin/evolution
kernel: 2.6.34.8-68.fc13.i686.PAE
package: evolution-2.30.3-1.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1299854131
uid: 500

How to reproduce
-----
1. Clicked on icon to open evolution
2. Evolution crashed
3.
Comment 1 Timothy Ward 2011-03-11 14:44:49 UTC 
Created attachment 483743 [details]
File: backtrace
Comment 2 Timothy Ward 2011-03-11 14:54:10 UTC 
Removing the .evolution/mail/local/folders.db file and starting evolution seems to work.
Comment 3 Milan Crha 2011-03-11 16:47:54 UTC 
Thanks for a bug report. This is usually caused by a damage of the folders.db file, as you found yourself. Thi sis fixed with the current F15 version, which is 2.91.91.
Note You need to log in before you can comment on or make changes to this bug.