Bug 724030

Summary: [abrt] pidgin-2.9.0-1.fc14: sighandler: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: jose carlos rebeque <jcrrebeque>
Component: pidginAssignee: Stu Tomlinson <stu>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: fedora, itamar, shakka.by, stu
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:f1c9db47425700fba0f9c9ee0abe00e409c470c3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-30 12:50:24 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 jose carlos rebeque 2011-07-21 18:05:11 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 19435 bytes
cmdline: pidgin
component: pidgin
Attached file: coredump, 31973376 bytes
crash_function: sighandler
executable: /usr/bin/pidgin
kernel: 2.6.35.13-92.fc14.i686
package: pidgin-2.9.0-1.fc14
rating: 4
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1311270631
uid: 500

How to reproduce
-----
1.TRAVAMENTO DE PACOTE.
2.
3.
Comment 1 jose carlos rebeque 2011-07-21 18:05:15 UTC 
Created attachment 514255 [details]
File: backtrace
Comment 2 shakka.by 2011-08-01 18:06:21 UTC 
Package: pidgin-2.9.0-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Launch pidgin
2. Move contact in another category
3. Pidgin crash


Comment
-----
I just moved a contact to another category and pidgin crashed after a little moment.
Comment 3 abrt-bot 2012-03-30 12:50:24 UTC 
Backtrace analysis found this bug to be similar to bug #720781, closing as duplicate.

This comment is automatically generated.

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