Bug 652895 - [abrt] empathy-2.32.0.1-2.fc14: g_logv: Process /usr/libexec/empathy-auth-client was killed by signal 6 (SIGABRT)
Summary: [abrt] empathy-2.32.0.1-2.fc14: g_logv: Process /usr/libexec/empathy-auth-cli...
Keywords:
Status: CLOSED DUPLICATE of bug 646130
Alias: None
Product: Fedora
Classification: Fedora
Component: empathy
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:214dffdabe41c19d533f0899e54...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-13 11:52 UTC by Johannes Schmid
Modified: 2010-11-14 20:46 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-14 20:46:18 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (25.26 KB, text/plain)
2010-11-13 11:52 UTC, Johannes Schmid 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.