Bug 607971

Summary: [abrt] crash in midori-0.2.6-1.fc13: raise: Process /usr/bin/midori was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Raphael Groner <projects.rg>
Component: midoriAssignee: Peter Gordon <peter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: maxamillion, peter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:fa68eeea9d1f763365e036eedaae9cf3d35b7a67
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-25 10:45:08 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 Raphael Groner 2010-06-25 10:19:46 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/midori http://www.o2.de/1goal?o2crm=o2crm_28031361793768
component: midori
crash_function: raise
executable: /usr/bin/midori
global_uuid: fa68eeea9d1f763365e036eedaae9cf3d35b7a67
kernel: 2.6.33.5-124.fc13.x86_64
package: midori-0.2.6-1.fc13
rating: 4
reason: Process /usr/bin/midori was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. open Midori with some url
2.
3.
Comment 1 Raphael Groner 2010-06-25 10:19:49 UTC 
Created attachment 426837 [details]
File: backtrace
Comment 2 Raphael Groner 2010-06-25 10:45:08 UTC 
Closing this bug cause I think it is the problem described in bug #604499.

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