Page 1 of 1

[SOLVED] Midori crash by opening a page

PostPosted: Mar 17th, '12, 20:52
by paiiou
Hello,
When I launch midori, the page indexhtml displays well, but as soon as midori open a http page, midori closes.
My environment is Xfce.

This is what I read, when I open midori in a terminal:
Code: Select all
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gdk-CRITICAL **: gdk_keymap_get_modifier_mask: assertion `GDK_IS_KEYMAP (keymap)' failed
Gdk-CRITICAL **: gdk_keymap_get_for_display: assertion `GDK_IS_DISPLAY (display)' failed
Gtk-CRITICAL **: _gtk_replace_virtual_modifiers: assertion `GDK_IS_KEYMAP (keymap)' failed
La configuration n'a pu être chargée : Aucun fichier ou dossier de ce type

Re: Midori crash by opening a page

PostPosted: Mar 17th, '12, 21:18
by doktor5000
Is this a fresh install or an upgrade from Mandriva, is this with a fresh /home, and does it also happen with another user (like xguest f.ex.)?
Also please show the output of
Code: Select all
rpm -q midori
in a terminal.

Re: Midori crash by opening a page

PostPosted: Mar 17th, '12, 21:28
by paiiou
Hello doktor5000
doktor5000 wrote:Is this a fresh install or an upgrade from Mandriva, is this with a fresh /home, and does it also happen with another user (like xguest f.ex.)?
Also please show the output of
Code: Select all
rpm -q midori
in a terminal.


This is a fresh install (cauldron) with an update of this morning.
Midori is 0.4.4-1
But it has been for several weeks since I have the problem.
I use at present chromium-browser.
I wonder if, with Xfce, I do not miss a package or a configuration.

Re: Midori crash by opening a page

PostPosted: Mar 17th, '12, 22:03
by doktor5000
Then you've posted this in the wrong subforum, all problems related to cauldron belong in viewforum.php?f=15

FWIW, here it works under LXDE, additionally to your output (which is not really relevant to the problem you see) i get:
Code: Select all
Gtk-WARNING **: Theme parsing error: gtk.css:58:46: Unknown value 'GTK_SHADOW_NONE' for enum type 'GtkShadowType'
ERROR: Invalid browser function table. Some functionality may be restricted.
java version "1.6.0_22"
OpenJDK Runtime Environment (IcedTea6 1.10.4) (fedora-24.b22.10.mga2-i386)
OpenJDK Client VM (build 20.0-b11, mixed mode)


The only other issue i see is when closing midori normally, i get:
Code: Select all
Gdk-ERROR **: The program 'midori4' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 12061 error_code 3 request_code 153 minor_code 3)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the GDK_SYNCHRONIZE environment
   variable to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Trace/breakpoint trap (core dumped)


The only other thing i can think of is either a problem with the GTK theme that is used under XFCE
or that you're missing some Gnome3 libraries. For the former, please show the output of
Code: Select all
gsettings get org.gnome.desktop.interface gtk-theme

Re: Midori crash by opening a page

PostPosted: Mar 18th, '12, 09:23
by paiiou
Forgiveness to have posted in the bad column(section).
Here is the answer to gsettings get org.gnome.desktop.interface gtk-theme

GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
'Adwaita'

Re: Midori crash by opening a page

PostPosted: Mar 18th, '12, 09:32
by paiiou
I have just noticed that it is the last line which displays at the time of the crash:

Instruction non permise (core dumped)

Re: Midori crash by opening a page

PostPosted: Mar 18th, '12, 11:24
by doktor5000
OK, then you should look up https://wiki.mageia.org/en/Debugging_software_crashes
and proceed as explained there (enable core_release_debug and install midori-debug, and then run midori inside gdb)
You may have to install a big number of -debug packages, but gdb will tell you this.

If you have the full backtrace, open a bug report https://wiki.mageia.org/en/How_to_report_a_bug_properly
and attach the backtrace there.

Re: [Solved]Midori crash by opening a page

PostPosted: Mar 22nd, '12, 15:05
by paiiou
Since update of yesterday evening (gtk, dconf ...), midori work correctly.