Bug 595466

Summary: [abrt] crash in midori-0.2.2-1.fc12: raise: Process /usr/bin/midori was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Konstantin Svist <fry.kun>
Component: midoriAssignee: Peter Gordon <peter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: antenna-5, kevin, maxamillion, peter
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:dde054c6b8c2c72cd35c83caf7a2d50803f4a90f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-29 00:20:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
File: backtrace none

Description Konstantin Svist 2010-05-24 17:29:00 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: midori
comment: Started up midori
component: midori
crash_function: raise
executable: /usr/bin/midori
global_uuid: dde054c6b8c2c72cd35c83caf7a2d50803f4a90f
package: midori-0.2.2-1.fc12
rating: 4
reason: Process /usr/bin/midori was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 Konstantin Svist 2010-05-24 17:29:01 UTC
Created attachment 416178 [details]
File: backtrace

Comment 2 Adam Miller 2010-05-26 15:35:59 UTC
https://admin.fedoraproject.org/updates/midori-0.2.6-1.fc12 is currently pending to go into updates-testing, please try reproducing the error with the latest version.

Thank you,

Comment 3 Konstantin Svist 2010-06-28 17:17:01 UTC
2.6 seems to work okay

Comment 4 Kevin Fenzi 2010-08-28 22:50:10 UTC
This seems to be the same crash as bug 597509. 

Please try the suggestions there.

Comment 5 Kevin Fenzi 2010-08-29 00:20:19 UTC

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