Midori received SIGSEGV on start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Midori Web Browser |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I recently tried to open Midori after an update, and then crash miserably, no windows neither alerts, just won' start.
I'm on Debian Testing/Stretch, I don't know if it's related, but maybe yes.
midori -g
Thread 1 "midori" received signal SIGSEGV, Segmentation fault.
0x00007ffff1508348 in WTF::String:
#0 0x00007ffff1508348 in WTF::String:
#1 0x00007ffff1080bf4 in OpaqueJSString:
#2 0x00007ffff105bb9b in JSEvaluateScript () from /usr/lib/
#3 0x00007ffff7b73e37 in sokoke_
#4 0x00007ffff7b94e2d in midori_
#5 0x00007ffff7b5a459 in midori_
#6 0x000055555555726a in main ()
Version
Midori 0.5.11 ((null)) Midori
GTK+ 2.24.30 (2.24.30) Glib 2.48.1 (2.48.1)
WebKitGTK+ 2.4.11 (2.4.11) libSoup 2.54.1
Observation
If I start with "--plain" option it has no problems
Best regards.
description: | updated |
Hey,
I've just fixed this bug on Debian. See:
https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 834236
The issue is actually a regression introduced by a recent update on webkitgtk. I'll file a bug against them later, but for now the fix above should suffice.
I thought about submitting a patch to upstream Midori but (a) the project is scheduled to switch to GTK-3/WebKit2 soon, and (b) the development is really slow lately. For now, I'll keep the fix on Debian.