Bug 693378 - [abrt] evolution-2.32.2-1.fc14: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.2-1.fc14: Process /usr/bin/evolution was killed by sign...
Keywords:
Status: CLOSED DUPLICATE of bug 665741
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3cea3d5b55f4b6a7e2c5e170f52...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-04 13:48 UTC by Larry O'Leary
Modified: 2011-04-05 06:09 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-04-05 06:09:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (87.72 KB, text/plain)
2011-04-04 13:48 UTC, Larry O'Leary
no flags Details

Description Larry O'Leary 2011-04-04 13:48:55 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 89824 bytes
cmdline: evolution
comment: As reported before, this appears to occur after a fresh startup or after Evolution has been closed for a while. In other words, if I lauch Evolution a second time, it seems to open just fine. If I close it and then relaunch it within a minutes or so, again, it opens just fine. But if I close it and leave it closed for a couple hours, relaunch results in the crash as well.
component: evolution
Attached file: coredump, 219508736 bytes
crash_function: camel_folder_search_set_folder
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.fc14.x86_64
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301924268
uid: 500

How to reproduce
-----
1. Launch Evolution

Comment 1 Larry O'Leary 2011-04-04 13:48:58 UTC
Created attachment 489775 [details]
File: backtrace

Comment 2 Milan Crha 2011-04-05 06:09:47 UTC
Thanks for a bug report. This particular one had been reported already, thus I'm marking it as a duplicate.

*** This bug has been marked as a duplicate of bug 665741 ***


Note You need to log in before you can comment on or make changes to this bug.