Bug 597950 - [abrt] crash in telepathy-gabble-0.9.11-1.fc13: Process /usr/libexec/telepathy-gabble was killed by signal 11 (SIGSEGV)
[abrt] crash in telepathy-gabble-0.9.11-1.fc13: Process /usr/libexec/telepath...
Product: Fedora
Classification: Fedora
Component: telepathy-gabble (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Brian Pepple
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-05-31 01:17 EDT by jasonbenedict
Modified: 2010-12-02 09:51 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-02 09:51:40 EST
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 (14.73 KB, text/plain)
2010-05-31 01:17 EDT, jasonbenedict
no flags Details

  None (edit)
Description jasonbenedict 2010-05-31 01:17:53 EDT
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
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"
Comment 1 jasonbenedict 2010-05-31 01:17:56 EDT
Created attachment 418156 [details]
File: backtrace
Comment 2 Brian Pepple 2010-06-18 18:50:17 EDT
Could you please verify that this bug is still present with the latest version of Empathy (empathy- 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 09:51:40 EST
Closing since no additional information has been provided. Assuming the problem has been solved. If not, please re-open with additional info. Thanks!

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