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 668403 - 2.4.9 and above won't start if Lilypond is in the PATH (guile version conflict)
2.4.9 and above won't start if Lilypond is in the PATH (guile version conflict)
Status: RESOLVED OBSOLETE
Product: GnuCash
Classification: Other
Component: Windows
2.4.x
Other Windows
: Normal major
: ---
Assigned To: Christian Stimming
Geert Janssens
: 670103 680108 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-01-21 19:58 UTC by pamaceclo
Modified: 2018-06-29 23:05 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Windows level reporting (1.82 KB, text/plain)
2012-01-29 14:53 UTC, pamaceclo
Details
Windows level error detail (611 bytes, text/plain)
2012-01-29 16:13 UTC, pamaceclo
Details

Description pamaceclo 2012-01-21 19:58:41 UTC
On Windows 7 64 bits, the new GNUCASH 2.4.9 cannot be launched. Program aborts without any further notice.

Problem disappears when reverting to 2.4.8
Comment 1 André Klapper 2012-01-21 21:16:04 UTC
Is there any output when you start the application from a terminal/console/commandline window?
Comment 2 Geert Janssens 2012-01-22 21:02:06 UTC
This is most likely due to a known bug in the Windows installer package. Can you try to simply uninstall and reinstall GnuCash ?
Comment 3 John Ralls 2012-01-28 18:34:46 UTC
OP, are you using an admin or a user account? If a user account, does it work if you try with an admin account?
Comment 4 pamaceclo 2012-01-28 19:25:05 UTC
Well, to answer your questions:

André: no nothing reported on terminal window
Geert: I did this several time, without any result
John: I'm an admin on this machine

This is exactly the same problem than the issue discussed on Gnucash Nabble forum under the URL :
http://gnucash.1415818.n4.nabble.com/gnucash-2-4-9-crashes-on-Windows-7-tp4309366p4334466.html

I tried everything suggested in this thread without any success... and I'm not alone in this situation.

Thanks anyhow for your help(In reply to comment #3)
> OP, are you using an admin or a user account? If a user account, does it work
> if you try with an admin account?
Comment 5 John Ralls 2012-01-28 20:58:05 UTC
Yes, I understand that, but a couple of the participants in that thread have reported separately (Bug 668849, Bug 668891) that their crashes occur only when Gnucash is run from an unprivileged user account -- and the first one reports that running as an admin user first allows unprivileged accounts to run it afterwards. I've replicated *that* behavior with XP Home.

Since your crash occurs as an admin user, it would appear to be a different problem.

Please find your tracefile (see http://wiki.gnucash.org/wiki/Tracefile) and attach it here. If you're able, it would help a lot if you could get a stack trace as well.
Comment 6 John Ralls 2012-01-28 21:39:01 UTC
I've found the problem for 668849, which has to do with guile. Geert reported in that email thread that he'd gotten the crash in gdk, so maybe you and he are seeing the same thing.
Comment 7 pamaceclo 2012-01-29 14:26:27 UTC
The tracefile got after trying to run 2.4.9 under Windows 7 64 bit is a 0 bites file, so I cannot attach it (but anyway it's empty!)
Thanks again.
(In reply to comment #5)
> Yes, I understand that, but a couple of the participants in that thread have
> reported separately (Bug 668849, Bug 668891) that their crashes occur only when
> Gnucash is run from an unprivileged user account -- and the first one reports
> that running as an admin user first allows unprivileged accounts to run it
> afterwards. I've replicated *that* behavior with XP Home.
> 
> Since your crash occurs as an admin user, it would appear to be a different
> problem.
> 
> Please find your tracefile (see http://wiki.gnucash.org/wiki/Tracefile) and
> attach it here. If you're able, it would help a lot if you could get a stack
> trace as well.
Comment 8 pamaceclo 2012-01-29 14:53:20 UTC
Created attachment 206357 [details]
Windows level reporting

I might have an interesting clue for my problem. 

When looking at the attached error info from the Windows logging journal, it says the faulty module is :
C:\Program Files (x86)\LilyPond\usr\bin\libguile-17.dll

Lilypond is another application (for music notation), nothing to do with Gnucash. Problem might come from the fact that Gnucash fetches a module which belongs to another application.
Comment 9 John Ralls 2012-01-29 15:35:29 UTC
Yes, I know about Lilypond: They're the only other application using Guile. 

Can you look in your environment variables and see if there are any GUILE variables set?

Even if there aren't, you can try setting the following:
GUILE_HOME="c:\Program Files\gnucash\share\guile\1.8"
GUILE_IMPLEMENTATION_PATH="%GUILE_HOME%"
GUILE_LOAD_PATH="%GUILE_HOME%:%GUILE_LOAD_PATH%"

If you have Gnucash installed in "c:\Program Files (x86)", change the path accordingly, of course. That will probably break your Lilypad installation, but it will indicate a possible fix.
Comment 10 pamaceclo 2012-01-29 16:13:57 UTC
Created attachment 206363 [details]
Windows level error detail

John,
I did exactly what you suggest. Rebooted, reinstalled 2.4.9 and unfortunately, still the same kind pf problem. I'm attaching the new error report detail, but I think it is the same as before.
Thanks for helping me.
(please note that reverting back to 2.4.8 fixes the problem)
Comment 11 John Ralls 2012-01-29 16:41:10 UTC
There wasn't any need to reboot or to reinstall gnucash. Did you find anything in the environment variables?

Oh, wait... PATH. Lilypond is on your PATH, isn't it? Try removing it.
Comment 12 pamaceclo 2012-01-30 16:33:13 UTC
John, many many thanks!
That was it and now it runs !
Don't know why this was not a problem with 2.4.8
But anyhow,I can now launch and run 2.4.9. Best of all, it does not seem to ruin my Lilypond usage.
Many thanks again !

> There wasn't any need to reboot or to reinstall gnucash. Did you find anything
> in the environment variables?
> 
> Oh, wait... PATH. Lilypond is on your PATH, isn't it? Try removing it.
Comment 13 John Ralls 2012-01-30 16:55:15 UTC
OK, good. It didn't affect 2.4.8 because 2.4.9 upgraded the Guile installation on Windows to 1.8 -- it had been 1.6 before, so it was linking a different library name.

So we can look at how we're setting up PATH, and maybe I can work something out with the Lilypond guys so that we're not stepping on each other.
Comment 14 Mike Evans 2012-02-15 22:17:32 UTC
*** Bug 670103 has been marked as a duplicate of this bug. ***
Comment 15 forrest-gnome 2012-03-29 18:17:30 UTC
Windows XP.  GnuCash 2.4.10 crashes on first attempt to run.  

The workaround of removing Lilypond from the path resolved the problem for me.

On Windows XP:
Control Panel->System->Advanced Tab.
Click on Environment Variables button.
Find PATH under System Variables.
Edit to remove the entry naming LilyPond.
Comment 16 Mike Evans 2012-07-18 08:33:01 UTC
*** Bug 680108 has been marked as a duplicate of this bug. ***
Comment 17 carl.brusse 2012-09-05 05:38:49 UTC
Has anyone with these issues been using a custom theme for GnuCash as set by the "set a theme" program? 

Similar issue experienced by me just now when upgrading from 2.4.7 to 2.4.11. Re-installation ineffective, any version 2.4.9 or above experienced the same problem. Once or twice though it launched successfully but with strange UI elements that froze GnuCash when clicked on. Issue was resolved by launching "set a theme" and hitting the reset button. Suspect some of the old themes and the divided up libraries post-2.4.9 don't play nice with each other.
Comment 18 John Ralls 2017-09-24 22:19:36 UTC
Reassign version to 2.4.x so that individual 2.4 versions can be retired.
Comment 19 John Ralls 2018-06-29 23:05:22 UTC
GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=668403. Please continue processing the bug there and please update any external references or bookmarks.