Segmentation fault at start (seems glib-related)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Midori Web Browser |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Midori doesn't start (even after deleting config) and it outputs this in the console:
(midori4:12305): GLib-GObject-
Backtrace available at http://
Reproducible with Midori 0.4.6, 0.4.7 and 0.4.8. However, I've used the first two version intensively for months and got no segfault at start. More so, while playing with GDB and Midori in a test account with no Midori settings, at the beginning it segfaulted then it started just fine for a few times and now it segfaults again.
Can't give a paste of the about:version page because Midori doesn't start but I'm trying to stitch together all the info by hand:
Midori version: 0.4.{6,7,8}
GTK+ 2.24.12, GLIB 2.32.4
WebKitGTK+ 1.8.3, libsoup 2.38.1
cairo 1.12.10
gcr no
granite no
libnotify 0.7.5
libunique 1.1.6
Platform X11; Linux x86_64
Identification: Automatic (but I'm sure it doesn't matter)
Video Formats H264 [x] Ogg Theora [x] WebM [x]
Thanks!
I should mention that the only "unstable" package in my Gentoo setup is cairo and I've tried the "stable" version 1.10.2 too, with no success. I've also tried in vain the "unstable" glib package version 2.34.3 (this has also required updated gobject- introspection- common and gobject- introspection packages). In the process I have recompiled all *glib*, *gobject* and *webkit* packages several times.
The only thing that makes Midori working again is compiling it against the GTK3 version of WebKit. But I don't want that, I'm using Xfce and GTK+ 2.x desktop apps only.