Bug 623836 - [abrt] crash in evolution-2.30.2-4.fc13: __libc_free: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.2-4.fc13: __libc_free: Process /usr/bin/evolut...
Keywords:
Status: CLOSED DUPLICATE of bug 614864
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6c99acdf24e8ada36cae1a7e81b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-12 22:32 UTC by Jeff Raber
Modified: 2010-11-09 15:48 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 15:48:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (44.92 KB, text/plain)
2010-08-12 22:32 UTC, Jeff Raber
no flags Details

Description Jeff Raber 2010-08-12 22:32:13 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: Repeatedly crashes immediately after openening.  I am using MS Exchange via OWA.
component: evolution
crash_function: __libc_free
executable: /usr/bin/evolution
global_uuid: 6c99acdf24e8ada36cae1a7e81b558f301798be2
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: evolution-2.30.2-4.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.  Open Evolution.
2.  Entered Credentials when prompted (Using Exchange via OWA)
3.  Crash

Comment 1 Jeff Raber 2010-08-12 22:32:15 UTC
Created attachment 438551 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 15:48:24 UTC

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

Comment 3 Karel Klíč 2010-11-09 15:48:24 UTC
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 #614864.

Sorry for the inconvenience.


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