Midori received SIGSEGV on start

[Lenny Andreu]

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::isolatedCopy() const () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0
#0 0x00007ffff1508348 in WTF::String::isolatedCopy() const () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0
#1 0x00007ffff1080bf4 in OpaqueJSString::string() const () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0
#2 0x00007ffff105bb9b in JSEvaluateScript () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0
#3 0x00007ffff7b73e37 in sokoke_js_script_eval () from /usr/lib/libmidori-core.so.1
#4 0x00007ffff7b94e2d in midori_speed_dial_construct () from /usr/lib/libmidori-core.so.1
#5 0x00007ffff7b5a459 in midori_normal_app_new () from /usr/lib/libmidori-core.so.1
#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.

[Sergio Durigan Junior (sergiodj)]

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.

[Lenny Andreu (landreuhs-29)]

Hi,

Thanks for your fast reply, I think it will dead alone xD

I will wait until the fix go to Testing to test (I still have 0.5.11-ds1-3 today).

Thanks again Sergio.

[Lenny Andreu (landreuhs-29)]

Hi again,

It's fixed in the upgrade you mention above, thanks!

Solved.