Bug 1357178 - midori fails to start fed24 lxde live
Summary: midori fails to start fed24 lxde live
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: midori
Version: 24
Hardware: i686
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-16 06:57 UTC by justineuro
Modified: 2016-07-17 05:06 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-16 17:03:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description justineuro 2016-07-16 06:57:36 UTC
Description of problem:
fails to start at command line and from Applications Menu

Version-Release number of selected component (if applicable):
[liveuser@localhost ~]$ midori --version

Midori 0.5.11 ((null)) Midori
GTK+ 2.24.29 (2.24.30)	Glib 2.47.5 (2.48.1)
WebKitGTK+ 2.4.9 (2.4.11)	libSoup 2.53.2
cairo 1.14.4 (1.14.6)	libnotify No
gcr 3.19.4	granite No

Copyright (c) 2007-2013 Christian Dywan

Please report comments, suggestions and bugs to:
	https://bugs.launchpad.net/midori
midori
Check for new versions at:
	http://www.midori-browser.org

How reproducible:
perfectly

Steps to Reproduce:
1. midori at cmd line
2.
3.

Actual results:
[liveuser@localhost ~]$ midori
The configuration couldn't be loaded: No such file or directory
Segmentation fault (core dumped)


Expected results:
[midori browser should open???]

Additional info:
[liveuser@localhost ~]$ midori -g
Launching command: '/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 "/lib/libthread_db.so.1".
The configuration couldn't be loaded: No such file or directory

Thread 1 "midori" received signal SIGSEGV, Segmentation fault.
0xb4c47cc5 in WTF::String::isolatedCopy() const () from /lib/libjavascriptcoregtk-1.0.so.0
#0  0xb4c47cc5 in WTF::String::isolatedCopy() const () from /lib/libjavascriptcoregtk-1.0.so.0
#1  0xb4720986 in OpaqueJSString::string() const () from /lib/libjavascriptcoregtk-1.0.so.0
#2  0xb46f346d in JSEvaluateScript () from /lib/libjavascriptcoregtk-1.0.so.0
#3  0xb7f577f0 in sokoke_js_script_eval () from /lib/libmidori-core.so.1
#4  0xb7f7e00b in midori_speed_dial_construct () from /lib/libmidori-core.so.1
#5  0xb7f80fad in midori_speed_dial_new () from /lib/libmidori-core.so.1
#6  0xb7f20707 in midori_normal_app_new () from /lib/libmidori-core.so.1
#7  0x800029fd in main ()
[liveuser@localhost ~]$

Comment 1 Kevin Fenzi 2016-07-16 17:03:10 UTC
Yes, unfortunately this was not fixed until after release. 

You need to update the webkitgtk package and it should work. That won't help the case on the live media, but there's really nothing we can do there. ;(

Comment 2 justineuro 2016-07-17 05:06:33 UTC
Thanks!  Much appreciated! :)


Note You need to log in before you can comment on or make changes to this bug.