Bug 684439

Summary: [abrt] pidgin-2.7.10-1.fc14: sighandler: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Joel Uckelman <uckelman>
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, stu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:00d2823f723489b870dd488a183d9e14de99d913
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 15:12:16 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 Joel Uckelman 2011-03-12 15:47:24 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 71991 bytes
cmdline: pidgin
component: pidgin
Attached file: coredump, 132067328 bytes
crash_function: sighandler
executable: /usr/bin/pidgin
kernel: 2.6.35.11-83.fc14.x86_64
package: pidgin-2.7.10-1.fc14
rating: 4
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1299944746
uid: 500

How to reproduce
-----
1. Started Google voice call.
2. Other user accepted.
3. Pidgin crashed.
Comment 1 Joel Uckelman 2011-03-12 15:47:27 UTC 
Created attachment 483907 [details]
File: backtrace
Comment 2 Joel Uckelman 2011-03-12 15:52:53 UTC 
Package: pidgin-2.7.10-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Started Audio Call over XMPP/Google Talk.
2. Other party accepted.
3. Pidgin crashed.


Comment
-----
Seems to be reproducible every time.
Comment 3 abrt-bot 2012-03-20 15:12:16 UTC 
Backtrace analysis found this bug to be similar to bug #710257, closing as duplicate.

Bugs which were found to be similar to this bug: bug #680699, bug #710257

This comment is automatically generated.

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