Bug 622766 - [abrt] crash in telepathy-haze-0.3.3-2.fc13: IA__g_object_ref: Process /usr/libexec/telepathy-haze was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in telepathy-haze-0.3.3-2.fc13: IA__g_object_ref: Process /usr/l...
Status: CLOSED DUPLICATE of bug 600893
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-haze   
(Show other bugs)
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Peter Gordon
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:2f69cdcc6f92a44198a437e9104...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-10 11:32 UTC by Andres Rios
Modified: 2010-11-09 15:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-09 15:18:05 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 (12.69 KB, text/plain)
2010-08-10 11:32 UTC, Andres Rios
no flags Details

Description Andres Rios 2010-08-10 11:32:41 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/telepathy-haze
component: telepathy-haze
crash_function: IA__g_object_ref
executable: /usr/libexec/telepathy-haze
global_uuid: 2f69cdcc6f92a44198a437e9104ff1070a8c025b
package: telepathy-haze-0.3.3-2.fc13
rating: 4
reason: Process /usr/libexec/telepathy-haze was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1.Don't know

Comment 1 Andres Rios 2010-08-10 11:32:43 UTC
Created attachment 437844 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 15:18:05 UTC

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

Comment 3 Karel Klíč 2010-11-09 15:18:05 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 #600893.

Sorry for the inconvenience.

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