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 603774 - Programs cannot start with glib-2.22.3 installed
Programs cannot start with glib-2.22.3 installed
Status: RESOLVED FIXED
Product: java-gnome
Classification: Bindings
Component: Bindings Core
4.0.x
Other Linux
: Normal critical
: ---
Assigned To: Andrew Cowie
java-gnome bindings maintainers
Depends on: 563627
Blocks:
 
 
Reported: 2009-12-04 09:56 UTC by Andrew Cowie
Modified: 2010-03-03 04:36 UTC
See Also:
GNOME target: 2.28.x
GNOME version: 2.27/2.28


Description Andrew Cowie 2009-12-04 09:56:04 UTC 
Calling [org.gnome.glib] Glib.setProgramName() is recommended practice, but crashes your application  if GLib version 2.22.3 is installed on your system. That release introduced a check preventing g_set_prgname() from being called more than once, and since java-gnome does so during Gtk.init() [as a convenience, setting the program to "java" as a default] subsequently calling our Glib.setProgramName() causes a FatalError.

AfC
Comment 1 Benjamin Otte (Company) 2009-12-04 10:05:32 UTC 
I suspect the proper way to do this is to check that getProgramName() == NULL before setting the name so it doesn't overwrite anything that was set previously.
Comment 2 Andrew Cowie 2009-12-04 10:08:02 UTC 
Remove java-gnome's "helpful" call to g_set_prgname() with its default value from the Gtk.init() code path.

As a workaround to the application crashing, allow Glib.setProgramName() to be called before Gtk.init(). This does not fix our problem due to bug #563627 but at least it gives us a way forward. Needs testing.

Merged to java-gnome in Bazaar branch 'mainline' at revno 701.

AfC