Bug 611413

Summary: [abrt] crash in pidgin-2.7.1-3.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:3c733cda1b7442e853ec10707cf1c95d02b10802
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-09 15:58:51 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 D.S. Ljungmark 2010-07-05 07:37:29 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: pidgin
component: pidgin
crash_function: raise
executable: /usr/bin/pidgin
global_uuid: 3c733cda1b7442e853ec10707cf1c95d02b10802
kernel: 2.6.33.5-124.fc13.x86_64
package: pidgin-2.7.1-3.fc13
rating: 4
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

comment
-----
[spider@Waves]~% rpm -qa |grep -E '(purp|pidg)'
libpurple-2.7.1-3.fc13.x86_64
purple-msn-pecan-0.1.0-1.fc13.x86_64
purple-microblog-0.2.4-3.fc13.x86_64
pidgin-libnotify-0.14-4.fc13.x86_64
pidgin-rhythmbox-2.0-5.fc12.x86_64
pidgin-musictracker-0.4.20-3.fc13.x86_64
pidgin-2.7.1-3.fc13.x86_64
pidgin-evolution-2.7.1-3.fc13.x86_64
pidgin-otr-3.2.0-3.fc12.x86_64


Might be -otr related?

How to reproduce
-----
1. Closed pidgin
2.
3.
Comment 1 D.S. Ljungmark 2010-07-05 07:37:31 UTC 
Created attachment 429479 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 15:58:51 UTC 

*** This bug has been marked as a duplicate of bug 592747 ***
Comment 3 Karel Klíč 2010-11-09 15:58:51 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.