After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 316878 - Windows 98 crash on gtk_option_menu_set_menu
Windows 98 crash on gtk_option_menu_set_menu
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.8.x
Other All
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2005-09-21 21:20 UTC by buliabyak
Modified: 2006-08-23 02:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description buliabyak 2005-09-21 21:20:01 UTC 
Steps to reproduce:
Download latest Inkscape snapshot, for example:

http://inkscape.org/win32-snap/inkscape-0509191800.zip

and run it on Windows 98. It crashes on start. I found that the crash happens in

 gtk_option_menu_set_menu(GTK_OPTION_MENU(us->menu), m);

call in spus_rebuild_menu() in helper/unit-menu.cpp. Both pointers passed to the
call are valid. The same build works OK in win2k/xp. Same code never crashed
with previous versions of gtk (2.4, 2.6).

Stack trace:
Unfortunately I cannot create a backtrace because when run from gdb.exe
(included in the package) inkscape crashes immediately without any backtrace.

Other information:
Comment 1 Adib Taraben 2005-09-26 22:39:54 UTC 
I can confirm this defect on a M$-Virtual PC running Win98

I use a more recent gdb than that from inkscape package and see more info:
-it throws follong error message:
Pango-ERROR **: file shape.c: line 75 (pango_shape): assertation failed:
(glyphs->num_glyphs > 0) aborting...
-if I press ok there comes an other one:
Pango-CRITICAL (recursed) **: _pango_engine_shape_shape: assertation
'PANGO_IS_FONT (font)' failed aborting...

I have following backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x034b6930 in ?? ()
(gdb) bt

+ Trace 63213

  • #0 ??
  • #1 Gtk::wrap_init()
    at wrap_init.cc line 451
  • #2 Gtk::Main::init_gtkmm_internals()
    at main.cc line 425 

HTH, Adib.
theAdib@yahoo.com
Comment 2 Murray Cumming 2005-10-20 11:21:24 UTC 
A simpler test case would be helpful here. Maybe you could try the gtkmm or GTK+
examples, or the demo (which the win32 installers install).
Comment 3 Tor Lillqvist 2005-10-20 11:28:20 UTC 
Try running without the ms-windows theme engine. (Comment out the
gtk-theme-name="ms-windows" line from your gtkrc file.) Or try changing the
system default font in your Display Settings to for instance Arial.
Comment 4 Tor Lillqvist 2005-10-20 11:30:54 UTC 
And actually, I am a bit surprised that you are able to even start an
application against GTK+ 2.8.* on Win98; as far as I know cairo uses APIs that
aren't present in Win9x. Is the version number entered wrong?
Comment 5 Hans Breuer 2005-10-20 18:40:53 UTC 
The APIs like CreateFontIndirectW() are there but just non functional stubs
returning the error return. And as noted in
http://mail.gnome.org/archives/gtk-devel-list/2005-October/msg00015.html
there is no testcase need. Every gtk app will crash with this, i.e. without
being able to create any font.
Comment 6 Tor Lillqvist 2005-10-20 21:01:38 UTC 
Ah yes, so what this bug actually means is that GTK+ 2.8.* doesn't run on Win9x?
(Which is known and more or less by design, but not really advertised.) The
symptom just happens to be (for Inkscape, at least) that it crashes in
gtk_option_menu_set_menu()?
Comment 7 Tor Lillqvist 2006-08-23 02:05:26 UTC 
It is extremely unlikely that anybody will ever bother to work on getting Win9x support back. Resolving as WONTFIX.