On 12/02/11 20:23, manuk7 wrote: >>>> Please provide a complete backtrace. >>> Ok, I re-installed testing version of libglib. Then midori didn't >>> segfault anymore on "fr." but on "en." (this is probably because >>> history >>> has changed during this time; Now I kept a copy of my .config/midori >>> in >>> case we need to do others tests).
What version of libpcre3 do you have? What happens if you install the testing and the unstable version? > (midori:11426): GLib-CRITICAL **: g_regex_replace_eval: assertion `string != > NULL' failed > > (midori:11426): GLib-CRITICAL **: g_regex_replace_eval: assertion `string != > NULL' failed > > (midori:11426): GLib-CRITICAL **: g_regex_replace_eval: assertion `string != > NULL' failed > > (midori:11426): GLib-CRITICAL **: g_regex_replace_eval: assertion `string != > NULL' failed > > (midori:11426): GLib-CRITICAL **: g_regex_replace_eval: assertion `string != > NULL' failed > > Program received signal SIGSEGV, Segmentation fault. I'm not convinced this is a GLib bug. Please run midory as G_DEBUG=fatal_warnings gdb midory Then get a new backtrace. Emilio -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
