Bug 639738 - [abrt] telepathy-gabble-0.9.18-1.fc14: raise: Process /usr/libexec/telepathy-gabble was killed by signal 6 (SIGABRT)
Summary: [abrt] telepathy-gabble-0.9.18-1.fc14: raise: Process /usr/libexec/telepathy-...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-gabble
Version: 14
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b640fc29485af75c36bb7df7568...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-03 19:39 UTC by John Watzke
Modified: 2010-12-02 19:06 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-02 19:06:34 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (16.14 KB, text/plain)
2010-10-03 19:39 UTC, John Watzke 		no flags Details
View All

Description John Watzke 2010-10-03 19:39:31 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/telepathy-gabble
comment: I was having connection issues with Google Talk (see bug639730) and after the failed connection attempt I closed Empathy and got this crash.
component: telepathy-gabble
crash_function: raise
executable: /usr/libexec/telepathy-gabble
kernel: 2.6.35.4-28.fc14.x86_64
package: telepathy-gabble-0.9.18-1.fc14
rating: 4
reason: Process /usr/libexec/telepathy-gabble was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1286134598
uid: 500
Comment 1 John Watzke 2010-10-03 19:39:33 UTC 
Created attachment 451303 [details]
File: backtrace
Comment 2 Brian Pepple 2010-12-02 15:15:35 UTC 
I've been unable to reproduce this bug, are you able to?
Comment 3 John Watzke 2010-12-02 19:06:34 UTC 
No, I haven't been able to reproduce this since around beta when we were trying to figure out the issue with connecting to GoogleTalk.  Since then, the components of Empathy have gotten updates so it may have been resolved in some other update or perhaps with the fixes to 639730.
Note You need to log in before you can comment on or make changes to this bug.