Bug 598131 - [abrt] crash in evolution-2.30.1-6.fc13: IA__g_object_unref: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.1-6.fc13: IA__g_object_unref: Process /usr/bin...
Status: CLOSED DUPLICATE of bug 597766
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:ff65a6f2f60da761d530d2627e2...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-31 14:14 UTC by Petr Muller
Modified: 2016-09-20 02:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 15:30:45 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (65.94 KB, text/plain)
2010-05-31 14:14 UTC, Petr Muller
no flags Details

Description Petr Muller 2010-05-31 14:14:04 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: The reproducer is kind of cryptic, tried it twice, saw the crash both time. I haven't tried if some of the steps can be actually omitted.
component: evolution
crash_function: IA__g_object_unref
executable: /usr/bin/evolution
global_uuid: ff65a6f2f60da761d530d2627e26544dab67f5e7
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 writing a new message
2. In "To: " field, start writing some name Evo already knows and will auto-fill
3. Right-click on the filled name and from the context menu select "Edit <name>"
4. CPU starts to spin up, click somewhere in the text area for the message
5. kaboom

Comment 1 Petr Muller 2010-05-31 14:14:07 UTC
Created attachment 418312 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 15:30:45 UTC

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

Comment 3 Karel Klíč 2010-11-09 15:30:45 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 #597766.

Sorry for the inconvenience.

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