Bug 597957

Summary: [abrt] crash in midori-0.2.4-1.fc13: raise: Process /usr/bin/midori was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: wmak.othermail
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: i686   
OS: Linux   
Whiteboard: abrt_hash:1871c27524134b4e60c186e1ff9c8585138499ad
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-28 23:41:46 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 wmak.othermail 2010-05-31 05:36:23 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: midori
comment: Midori cannot even be launched - crashes immediately.
component: midori
crash_function: raise
executable: /usr/bin/midori
global_uuid: 1871c27524134b4e60c186e1ff9c8585138499ad
kernel: 2.6.33.4-95.fc13.i686
package: midori-0.2.4-1.fc13
rating: 4
reason: Process /usr/bin/midori was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
How to reproduce: Crash on launch.
Comment 1 wmak.othermail 2010-05-31 05:36:27 UTC 
Created attachment 418161 [details]
File: backtrace
Comment 2 Kevin Fenzi 2010-08-28 23:41:46 UTC 
This is caused by the java plugin. See bug 604499

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