Bug 652895

Summary: [abrt] empathy-2.32.0.1-2.fc14: g_logv: Process /usr/libexec/empathy-auth-client was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Johannes Schmid <jhs>
Component: empathyAssignee: Brian Pepple <bdpepple>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: bdpepple
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:214dffdabe41c19d533f0899e543ecbeab62fb34
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-14 20:46:18 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 Johannes Schmid 2010-11-13 11:52:43 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/empathy-auth-client
component: empathy
crash_function: g_logv
executable: /usr/libexec/empathy-auth-client
kernel: 2.6.35.6-48.fc14.x86_64
package: empathy-2.32.0.1-2.fc14
rating: 3
reason: Process /usr/libexec/empathy-auth-client was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1289648807
uid: 500

comment
-----
The backtrace looks very much like a memory corruption/multi-threading issue. I don't know exactly why the 
debug packages are missing (they are installed). If you need any more information, just ping me.

How to reproduce
-----
It happens on startup of the GNOME session where empathy is in the autostart configuration. It doesn't seem to
cause any problems because empathy still works and all protocols are connected correctly (ICQ, MSN, Jabber, 
Facebook).
Comment 1 Johannes Schmid 2010-11-13 11:52:46 UTC 
Created attachment 460217 [details]
File: backtrace
Comment 2 Brian Pepple 2010-11-14 20:46:18 UTC 

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