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

Summary: [abrt] crash detected in empathy-2.28.1.2-1.fc12
Product: [Fedora] Fedora Reporter: Ken Barber <ken>
Component: empathyAssignee: Peter Gordon <peter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: bdpepple, peter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:7aa294c4e53fd80e323890f70711e20968154c45
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-18 00:35:20 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 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 ***