Bug 608182

Summary: [abrt] crash in pidgin-2.7.1-1.fc12: raise: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Rob <pembart>
Component: pidginAssignee: Warren Togami <wtogami>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: itamar, stu, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:f6f676f4c5236bd194e46abe7ee43097bed14520
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-26 01:16:05 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 Rob 2010-06-25 21:52:45 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: pidgin
comment: No real steps to follow, Pidgin simply appears to be crashing out at random since today's update, which included an update for Pidgin.  I first thought it may be due to custom smileys being loaded, but before the second crash no smileys were used in any of my chats
component: pidgin
crash_function: raise
executable: /usr/bin/pidgin
global_uuid: f6f676f4c5236bd194e46abe7ee43097bed14520
kernel: 2.6.32.14-127.fc12.i686
package: pidgin-2.7.1-1.fc12
rating: 4
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.
2.
3.
Comment 1 Rob 2010-06-25 21:52:47 UTC 
Created attachment 427003 [details]
File: backtrace
Comment 2 Rob 2010-06-25 21:54:39 UTC 
Also worth noting that before today's update (allowing all available updates to be applied on a daily basis, as and when available), Pidgin has never once crashed on this system.
Comment 3 Stu Tomlinson 2010-06-26 01:16:05 UTC 

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