Bug 615366 - [abrt] crash in evolution-data-server-2.30.2-2.fc13: __libc_free: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-data-server-2.30.2-2.fc13: __libc_free: Process /us...
Status: CLOSED DUPLICATE of bug 611429
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5c9eb79955068c402eddd2a69ac...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-16 15:47 UTC by Sanford Darlington
Modified: 2010-11-08 19:00 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-11-08 19:00:07 UTC


Attachments (Terms of Use)
File: backtrace (24.82 KB, text/plain)
2010-07-16 15:47 UTC, Sanford Darlington
no flags Details

Description Sanford Darlington 2010-07-16 15:47:13 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/e-addressbook-factory
comment: I'm using VPN while using Evolution.  Hasn't crashed on this before.
component: evolution-data-server
crash_function: __libc_free
executable: /usr/libexec/e-addressbook-factory
global_uuid: 5c9eb79955068c402eddd2a69acb4a201883ed5e
kernel: 2.6.33.6-147.fc13.x86_64
package: evolution-data-server-2.30.2-2.fc13
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Reply to an email.
2. Begin typing.
3. Crash!

Comment 1 Sanford Darlington 2010-07-16 15:47:15 UTC
Created attachment 432420 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-08 19:00:07 UTC

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

Comment 3 Karel Klíč 2010-11-08 19:00:07 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 #611429.

Sorry for the inconvenience.


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