Bug 625618

Summary: [abrt] midori-0.2.6-1.fc13: Process /usr/bin/midori was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kyle <drizzle.linux>
Component: midoriAssignee: Peter Gordon <peter>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: kevin, maxamillion, peter
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:42904a8253421a7d553f8816f88ae86d967488a3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-29 19:27:11 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 Kyle 2010-08-19 23:38:16 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: midori
component: midori
crash_function: IA__g_type_check_instance_cast
executable: /usr/bin/midori
kernel: 2.6.33.6-147.2.4.fc13.i686
package: midori-0.2.6-1.fc13
rating: 4
reason: Process /usr/bin/midori was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1282256219
uid: 500
Comment 1 Kyle 2010-08-19 23:38:19 UTC 
Created an attachment (id=439820)
File: backtrace
Comment 2 Kevin Fenzi 2010-08-29 19:27:11 UTC 
This looks like the same dns issue from bug 595699.
Can you try the suggestions there?

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