Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 548631 - [abrt] crash detected in empathy-2.28.1.2-1.fc12
Summary: [abrt] crash detected in empathy-2.28.1.2-1.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 532307
Alias: None
Product: Fedora
Classification: Fedora
Component: empathy
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peter Gordon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7aa294c4e53fd80e323890f7071...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-18 00:28 UTC by Ken Barber
Modified: 2009-12-18 00:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-18 00:35:20 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (deleted)
2009-12-18 00:28 UTC, Ken Barber 		no flags Details
View All

Description Ken Barber 2009-12-18 00:28:11 UTC 
abrt 1.0.0 detected a crash.

How to reproduce
-----
1. Start empathy
2. Connect
3. Wait 1-5 minutes

Comment: This has happened only once, so I'm sorry but I have little information on how to reproduce it exactly - I was connected for 5 minutes to a single XMPP service, and received the crash. I was idle, no messages and no other user joins (according to logs of ejabberd). Server is running ejabberd-2.0.5-8.el5 (from epel) on an rhel5.4 box. Connection was using TLS.
Attached file: backtrace
cmdline: empathy
component: empathy
executable: /usr/bin/empathy
kernel: 2.6.31.6-166.fc12.x86_64
package: empathy-2.28.1.2-1.fc12
rating: 4
reason: Process was terminated by signal 6
Comment 1 Ken Barber 2009-12-18 00:28:14 UTC 
Created attachment 379127 [details]
File: backtrace
Comment 2 Brian Pepple 2009-12-18 00:35:20 UTC 

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