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 612922 - The procedure entry point g_assertion_message could not be located in the dynamic link library libglib-2.0-0.dll
The procedure entry point g_assertion_message could not be located in the dyn...
Status: RESOLVED DUPLICATE of bug 634978
Product: glade
Classification: Applications
Component: general
3.6.x
Other Windows
: Normal major
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-03-15 08:21 UTC by Václav Kocian
Modified: 2011-01-22 09:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Václav Kocian 2010-03-15 08:21:10 UTC 
It's the only I have got from glade after install it on Windows. I have tried both, the installation with gtk together and separate installation of gtk and glade and behavior is always he same.
Comment 1 André Klapper 2010-03-26 09:52:23 UTC 
Can you please come up with exact steps and what this is about at all?
glade-- is not mentioned anywhere in your description.

Also see https://bugzilla.gnome.org/page.cgi?id=bug-writing.html
Comment 2 Václav Kocian 2010-03-26 09:58:57 UTC 
Yes, it is about the Glade, version 3.6.4. Steps:
Download installer
Install
Click on the icon in the start menu

Nothing, but the error message, happens.

V.K.
Comment 3 André Klapper 2010-03-26 10:36:05 UTC 
Which exact glib version is installed under Windows?
Comment 4 Václav Kocian 2010-03-26 10:45:12 UTC 
The glib version is 2.22.4. However, I did not install it. I guess, that it came together with the Glade or the GTK installation.
Comment 5 Tristan Van Berkom 2011-01-22 09:16:40 UTC 
So far we dont have a proper build script for win32.

Were looking into it in bug 634978 so I'm moving this there.

Have to attribute this mistake to being a flaw in a previously
created win32 build.

*** This bug has been marked as a duplicate of bug 634978 ***