http://bugzilla.opensuse.org/show_bug.cgi?id=987596
http://bugzilla.opensuse.org/show_bug.cgi?id=987596#c2
Kyrill Detinov changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CONFIRMED
CC| |dimstar@opensuse.org
--- Comment #2 from Kyrill Detinov ---
At least Midori starts running "midori --plain".
What I see in a terminal:
% midori -g
Launching command: '/usr/bin/gdb' --batch -ex 'set print thread-events off' -ex
run -ex 'set logging on /run/user/1000/midori/gdb.bt' -ex 'bt'
--return-child-result --args midori
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Thread 1 "midori" received signal SIGSEGV, Segmentation fault.
0x00007ffff23a5f48 in WTF::String::isolatedCopy() const () from
/usr/lib64/libjavascriptcoregtk-1.0.so.0
#0 0x00007ffff23a5f48 in WTF::String::isolatedCopy() const () from
/usr/lib64/libjavascriptcoregtk-1.0.so.0
#1 0x00007ffff1f1e524 in OpaqueJSString::string() const () from
/usr/lib64/libjavascriptcoregtk-1.0.so.0
#2 0x00007ffff1ef94cb in JSEvaluateScript () from
/usr/lib64/libjavascriptcoregtk-1.0.so.0
#3 0x00007ffff7b72dcf in sokoke_js_script_eval () from
/usr/lib64/libmidori-core.so.1
#4 0x00007ffff7b87405 in midori_speed_dial_construct () from
/usr/lib64/libmidori-core.so.1
#5 0x00007ffff7b6f839 in midori_normal_app_new () from
/usr/lib64/libmidori-core.so.1
#6 0x00005555555573a5 in main ()
@Dominique, may it be related to the latest changes in the
libjavascriptcoregtk-1_0-0 package?
--
You are receiving this mail because:
You are on the CC list for the bug.