Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 597782 - [abrt] crash in evolution-2.30.1-6.fc13: get_camel_folder: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
[abrt] crash in evolution-2.30.1-6.fc13: get_camel_folder: Process /usr/bin/e...
Status: CLOSED DUPLICATE of bug 596909
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
abrt_hash:8f4a6b395adefa23a7034ced98f...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-30 09:51 EDT by Harald Jensås
Modified: 2010-11-08 12:35 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-08 12:35:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (58.33 KB, text/plain)
2010-05-30 09:51 EDT, Harald Jensås
no flags Details

  None (edit)
Description Harald Jensås 2010-05-30 09:51:48 EDT
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: get_camel_folder
executable: /usr/bin/evolution
global_uuid: 8f4a6b395adefa23a7034ced98fd90e92cb6216f
kernel: 2.6.33.4-95.fc13.x86_64
package: evolution-2.30.1-6.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Start Evolution.
2. Set system in "stand-by" or sleep mode.
3. Wake up system.
4. Reconnect to Network.
5. Evolution status box says "Reconnecting to...."
6. CRASH.
Comment 1 Harald Jensås 2010-05-30 09:51:50 EDT
Created attachment 418025 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 12:35:35 EST

*** This bug has been marked as a duplicate of bug 596909 ***
Comment 3 Karel Klíč 2010-11-08 12:35:35 EST
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #596909.

Sorry for the inconvenience.

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