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 669581 - 2.4.10 Fails to open on Windows - libgdk-win32-2.0-0.dll is faulting
2.4.10 Fails to open on Windows - libgdk-win32-2.0-0.dll is faulting
Status: RESOLVED FIXED
Product: GnuCash
Classification: Other
Component: General
2.4.x
Other Windows
: Normal normal
: ---
Assigned To: Christian Stimming
Geert Janssens
Depends on:
Blocks:
 
 
Reported: 2012-02-07 15:52 UTC by Steven N
Modified: 2018-06-29 23:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Steven N 2012-02-07 15:52:59 UTC
The following error appears in Windows event log when attempting to start GnuCash 2.4.10. As it lists a Report Id, I suspect the crash has something to do with my saved reports, however, I am unable to find that Report Id in my "saved-reports-2.4" file. I have attempted to fully uninstall and reinstall, however the error persists. I am using Windows 7 x64.

Faulting application name: gnucash.exe, version: 0.0.0.0, time stamp: 0x4f2f45b1
Faulting module name: libgdk-win32-2.0-0.dll, version: 2.24.8.0, time stamp: 0x4eca77af
Exception code: 0xc0000005
Fault offset: 0x0001ac1c
Faulting process id: 0x1548
Faulting application start time: 0x01cce5aec9e3bb80
Faulting application path: C:\Program Files (x86)\gnucash\bin\gnucash.exe
Faulting module path: C:\Program Files (x86)\gnucash\bin\libgdk-win32-2.0-0.dll
Report Id: 08ed04f4-51a2-11e1-97e2-001fd0a3f2cc
Comment 1 Geert Janssens 2012-02-07 17:14:52 UTC
Thank you for reporting this bug. I can confirm I run into this as well. I reported it via the mailing list [1].

This bug seems to surface when your display is set to a colour depth less than 24-bit.

I'm not sure how you check this on Windows 7. On Windows XP, you can check your display settings as follows:
- Right-click somewhere on the desktop
- Select Properties
- Click on the settings tab

Since I access my Windows XP installation via Remote Desktop (RDP), the maximum depth I can use is by default 16 bits. In this setup GnuCash crashes as well on my system. If I connect via VNC (another mechanism to work with a remote computer), I can configure a display using 24bit and then GnuCash works.

So far that's the only workaround I have found so far.

[1] http://lists.gnucash.org/pipermail/gnucash-devel/2012-February/033553.html
Comment 2 Steven N 2012-02-07 17:31:07 UTC
I am also able to confirm that this is caused by the bit depth. I was accessing my Win7 computer via RDP as well, but was able to change the color to 32-bit and successfully launch GnuCash.
Comment 3 Steven N 2012-02-08 14:04:28 UTC
Just as an additional FYI, GnuCash seems to run fine in a 16-bit (or even 15-bit) RDP session, as long as the program was initially launched when the color bit was higher.
Comment 4 Geert Janssens 2012-02-08 14:29:19 UTC
Some googling revealed that this is actually a bug in gtk+ 2.24.8's cairo
library [1] and a fix should be available in gtk+ 2.24.9.

So once the 2.24.9 Windows binaries are available, we can build a new version
of GnuCash that hopefully fixes this.


[1]
http://python.6.n6.nabble.com/2-24-8-issue-on-win32-with-16bpp-display-td1945063.html
Comment 5 Geert Janssens 2012-02-09 16:21:39 UTC
GnuCash has been updated to use gtk+ 2.24.10 on Windows. With this change, a 16bit display depth no longer causes a crash.

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.
Comment 6 John Ralls 2017-09-24 22:49:13 UTC
Reassign version to 2.4.x so that individual 2.4 versions can be retired.
Comment 7 John Ralls 2018-06-29 23:06:08 UTC
GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=669581. Please update any external references or bookmarks.