Bug 590619 - [abrt] crash in telepathy-gabble-0.9.11-1.fc13: Process /usr/libexec/telepathy-gabble was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in telepathy-gabble-0.9.11-1.fc13: Process /usr/libexec/telepath...
Keywords:
Status: CLOSED DUPLICATE of bug 585614
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-gabble
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:09f6ddfc578f23bc6c545cdcdb6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-10 10:44 UTC by Peng Huang
Modified: 2010-05-25 08:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 08:41:01 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (15.51 KB, text/plain)
2010-05-10 10:44 UTC, Peng Huang 		no flags Details
View All

Description Peng Huang 2010-05-10 10:44:23 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/telepathy-gabble
component: telepathy-gabble
crash_function: IA__g_type_check_instance_is_a
executable: /usr/libexec/telepathy-gabble
global_uuid: 09f6ddfc578f23bc6c545cdcdb643eb04dfe7e8c
kernel: 2.6.33.3-85.fc13.i686
package: telepathy-gabble-0.9.11-1.fc13
rating: 4
reason: Process /usr/libexec/telepathy-gabble was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Use gtalk
2. Don't do anything for a while
3. Try to type some message with gtalk
4. crash
Comment 1 Peng Huang 2010-05-10 10:44:25 UTC 
Created attachment 412793 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 08:41:01 UTC 

*** This bug has been marked as a duplicate of bug 585614 ***
Comment 3 Karel Klíč 2010-05-25 08:41:01 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 #585614.

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