This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Amaya 10.0 (amaya_wx-10.0.1-1.i386-f8.rpm) on openSUSE 11.0 reports: "(amaya_bin:16371): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed" on startup. Amaya seems to work, but there seems to be a minor problem. Installed GTK are gtk-1.2.10-1049.1 and gtk2-2.12.9-37.1, but amaya seems to be statically linked.
(In reply to comment #0) > Amaya 10.0 (amaya_wx-10.0.1-1.i386-f8.rpm) on openSUSE 11.0 reports: > "(amaya_bin:16371): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion > `!GTK_WIDGET_REALIZED (widget)' failed" on startup. > Amaya seems to work, but there seems to be a minor problem. > > Installed GTK are gtk-1.2.10-1049.1 and gtk2-2.12.9-37.1, but amaya seems to be > statically linked. > Gtk is not statically linked and that bug is well known. To prevent that problem you have to launch amaya and not amaya_bin.
Of course I started "amaya" (and not "amaya.bin"). But the executable seems to be amaya.bin, so the error message from the executable will quote "amaya.bin". What made you think I started "amaya.bin" directly? Here's a trace (after yet another amaya crash): sh -x amaya + AMAYA_INSTALLDIR=Amaya + PREFIX=/usr/share + AMAYAGUI=wx + env XLIB_SKIP_ARGB_VISUALS=1 G_SLICE=always-malloc /usr/share/Amaya/wx/bin/amaya_bin 08:02:46: Deleted stale lock file '/home/windl/.amaya_bin-windl'. (amaya_bin:23708): Gtk-CRITICAL **: gtk_widget_set_colormap: assertion `!GTK_WIDGET_REALIZED (widget)' failed
The problem must be fixed with the new wxWidgets version used with Amaya 11.1