Bug 669881

Summary: [abrt] pidgin-2.7.9-1.fc14: sighandler: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Wade Mealing <wmealing>
Component: pidginAssignee: Stu Tomlinson <stu>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: itamar, stu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2cfae8a84c1eaacbdfa4be530b9ba0047e085dbe
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 18:58:15 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 Wade Mealing 2011-01-15 11:40:41 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: pidgin --session 29f054913-10ff-4dae-8967-cb079f70cb4c --display :0.0
component: pidgin
crash_function: sighandler
executable: /usr/bin/pidgin
kernel: 2.6.35.10-74.fc14.x86_64
package: pidgin-2.7.9-1.fc14
rating: 4
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1295091195
uid: 500

How to reproduce
-----
1. Copied and pasted some html into the pidgin
2. Edited it by hitting backspace a few times.
3. Crash

Comment 1 Wade Mealing 2011-01-15 11:40:44 UTC
Created attachment 473638 [details]
File: backtrace

Comment 2 Wade Mealing 2011-01-15 14:50:16 UTC
I think that the html may have included an underline  ( --- ) perhaps, I thought I saw it there for a moment.

Comment 3 abrt-bot 2012-03-20 18:58:15 UTC
Backtrace analysis found this bug to be similar to bug #689758, closing as duplicate.

Bugs which were found to be similar to this bug: bug #557486, bug #640074, bug #689758

This comment is automatically generated.

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