Bug 677184 - [abrt] telepathy-gabble-0.11.6-2.fc15: disconnect_callbacks: Process /usr/libexec/telepathy-gabble was killed by signal 6 (SIGABRT)
Summary: [abrt] telepathy-gabble-0.11.6-2.fc15: disconnect_callbacks: Process /usr/lib...
Keywords:
Status: CLOSED DUPLICATE of bug 680836
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-gabble
Version: rawhide
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2f1ad4f058b644402953984f1e2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-13 23:39 UTC by Andy Lawrence
Modified: 2012-03-20 15:54 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 15:54:27 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (18.00 KB, text/plain)
2011-02-13 23:39 UTC, Andy Lawrence 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Andy Lawrence 2011-02-13 23:39:16 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 18436 bytes
cmdline: /usr/libexec/telepathy-gabble
component: telepathy-gabble
Attached file: coredump, 21934080 bytes
crash_function: disconnect_callbacks
executable: /usr/libexec/telepathy-gabble
kernel: 2.6.38-rc4_andy_feb12.1+
package: telepathy-gabble-0.11.6-2.fc15
rating: 4
reason: Process /usr/libexec/telepathy-gabble was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Rawhide)
How to reproduce: Opened Empathy with gnome-shell running
time: 1297639921
uid: 500
Comment 1 Andy Lawrence 2011-02-13 23:39:18 UTC 
Created attachment 478524 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 15:54:27 UTC 
Backtrace analysis found this bug to be similar to bug #680836, closing as duplicate.

Bugs which were found to be similar to this bug: bug #639738, bug #680836

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 680836 ***
Note You need to log in before you can comment on or make changes to this bug.