Bug 597950

Summary: [abrt] crash in telepathy-gabble-0.9.11-1.fc13: Process /usr/libexec/telepathy-gabble was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: jasonbenedict
Component: telepathy-gabbleAssignee: Brian Pepple <bdpepple>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: bdpepple, sander
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:5deacc7f012375ec6c3904c0ad206caa3be4f8f6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-02 14:51:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description jasonbenedict 2010-05-31 05:17:53 UTC 
abrt 1.1.0 detected a crash.

architecture: x86_64
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: 5deacc7f012375ec6c3904c0ad206caa3be4f8f6
kernel: 2.6.33.4-95.fc13.x86_64
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. enable / disable "facebook chat"
2.
3.
Comment 1 jasonbenedict 2010-05-31 05:17:56 UTC 
Created attachment 418156 [details]
File: backtrace
Comment 2 Brian Pepple 2010-06-18 22:50:17 UTC 
Could you please verify that this bug is still present with the latest version of Empathy (empathy-2.30.1.1-1.fc13)? This version includes a fix for facebook chat (you'll most likely needed to delete & re-add the account - for the new server to be picked up in acct.cfg). Thanks!
Comment 3 Brian Pepple 2010-12-02 14:51:40 UTC 
Closing since no additional information has been provided. Assuming the problem has been solved. If not, please re-open with additional info. Thanks!