Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 597769

Summary: [abrt] crash in pidgin-2.7.0-2.fc13: raise: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: D.S. Ljungmark <spider>
Component: pidgin-otrAssignee: Paul Wouters <pwouters>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: itamar, pwouters, stu, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:8f8f5ed119e916ff149008eab7dbaa3a332df123
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 15:58:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description D.S. Ljungmark 2010-05-30 12:57:20 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: pidgin
comment: Beautiful crash . just the perfect service I'm used to.
component: pidgin
crash_function: raise
executable: /usr/bin/pidgin
global_uuid: 8f8f5ed119e916ff149008eab7dbaa3a332df123
kernel: 2.6.33.5-112.fc13.x86_64
package: pidgin-2.7.0-2.fc13
rating: 4
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.Minimize pidgin (AFK)
2. Close pidgin from system tray
3.

Comment 1 D.S. Ljungmark 2010-05-30 12:57:23 UTC
Created attachment 418019 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 15:58:42 UTC

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

Comment 3 Karel Klíč 2010-11-09 15:58:42 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #592747.

Sorry for the inconvenience.