Description of problem: gnucash won't start anymore Attempting to start it from the console results in the following error: [remmy@silvertown ~]$ gnucash Backtrace: In unknown file: ?: 0* [primitive-load-path "slib/guile.init"] <unnamed port>: In procedure primitive-load-path in expression (primitive-load-path name): <unnamed port>: Unable to find file "slib/guile.init" in load path It has worked before, but I am not sure if I've used it since upgrading from Mageia 1 to 2.
what if you install slib?
slib was already installed. I did urpmi guile, which removed gnucash, then did urpmi gnucash again, and now it works. A bit puzzled. This after reading https://qa.mandriva.com/show_bug.cgi?id=64068
No problems with gnucash on my i586 system. Both slib and guile were installed automatically when I installed gnucash, shortly after Mageia 2 was released.
One possible explanation - you need guile1.8 and not guile-2.0 for gnucash. You may have been missing guile1.8 for some reason. It was perhaps installed when you installed gnucash the second time.
See also https://bugs.mageia.org/show_bug.cgi?id=4882#c13 and https://bugs.mageia.org/show_bug.cgi?id=4882#c15
I think that James is right. I just attempted to install Lilypond, which needs guile-2.0. I got a message that guile-1.8 was incompatible, and I would need to uninstall gnucash first.
CC: (none) => laidlaws
Did you upgrade from Mageia 1, or install a pre-release version of Mageia 2? There is no guile-1.8 in Mageia 2. There is instead guile1.8. The name was changed so that it could co-exist with guile-2.0.
I have the following: guile-runtime-2.0.5-4.mga2 guile1.8-runtime-1.8.8-11.mga2 guile1.8-1.8.8-11.mga2 libguile17-1.8.8-11.mga2 libguile2.0_22-2.0.5-4.mga2 libguilereadline18_18-2.0.5-4.mga2 I have no guile-2.0 packages installed or available.
Yes - I think there is a packaging bug: guile1.8 conflicts with guile-2.0.5-4, which would seem to defeat the purpose of renaming the package: # urpmi guile The following packages have to be removed for others to be upgraded: ...... guile1.8-1.8.8-11.mga2.i586 (due to conflicts with guile[>= 2.0.3]) ....
I use gnucash regularly. As an interim measure, I will shift musescore and Lilypond to Cauldron. Good luck!
I think that this bug may be related to bug 5767.
Certainly this extract from bug 5767 seems to match my experience: "Hence, it is safe to remove guile1.8 from Requires: of gnucash and lilypond." It is the Requires: line that is the problem. Apparently the suggestion didn't work.
*** Bug 7756 has been marked as a duplicate of this bug. ***
CC: (none) => mark.dawsonbutterworth
This is a bit odd. I have been running GnuCash 2.4.10 with no issues at all under Mageia 2. I have also been using Lilypond 2.15.31. I filed bug 7756 today, which has been marked as a duplicate of this bug. Note that both GnuCash and Lilypond still work for me - I have not upgraded lilypond or guile from the latest update (see 7756), as this looks likely to be going to kill GnuCash. I appear to have two versions of guile coexisting without problems: [root@ML350G5 Download]# rpm -qa | grep guile guile-runtime-2.0.5-4.mga2 guile1.8-1.8.8-11.mga2 libguile2.0_22-2.0.5-4.mga2 guile1.8-runtime-1.8.8-11.mga2 libguile17-1.8.8-11.mga2
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
This bug depends on the two versions of guile being required: 1.8 and 2.0.3. I have kept to running gnucash on my Official system and Lilypond on something else to avoid the conflict. AFAIK, the bug is still presenrt in Mga 3.
then change version as explained
I will verify what I said, first.
Still present in Mga 3. No gnucash in Cauldron, so I couldn't test there. This was originally reported in x86-64. I am running i586. Message in terminal (with gnucash already installed) follows: sudo urpmi lilypond [sudo] password for doug: The following packages have to be removed for others to be upgraded: gnucash-2.4.11-4.mga3.i586 (due to missing guile1.8, due to missing libgnc-backend-xml-utils.so.0, due to missing libgnc-qof.so.1, due to missing libgnc-gnome.so.0, due to missing libgnc-module.so.0, due to missing libgnc-business-ledger.so.0, due to missing libgnc-backend-sql.so.0, due to missing libgnc-core-utils.so.0) guile1.8-1.8.8-12.mga3.i586 (due to conflicts with guile[>= 2.0.3]) libgnucash0-2.4.11-4.mga3.i586 (due to missing libgncmod-dialog-tax-table.so, due to missing libgncmod-app-utils.so, due to missing libgncmod-engine.so, due to missing libgncmod-gnome-utils.so, due to missing libgncmod-register-core.so, due to missing libgncmod-calculation.so, due to missing libgncmod-report-gnome.so, due to missing libgncmod-register-gnome.so, due to missing libgncmod-gnome-search.so, due to missing libgncmod-ledger-core.so, due to missing libgncmod-html.so, due to missing libgncmod-report-system.so) (y/N) n
Hardware: x86_64 => i586Version: 2 => 3
I can confirm that the current 2.6.0 version of gnucash, when downloaded as a tarball, built, and installed using "make install" works with the later version of guile, so is compatible with Lilypond, but the Mageia rpm is still incompatible. Would the package maintainer be able to pick up this latest version please?
I now have both packages running side-by-side in Cauldron, so there may be no issue in Mga 4.
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD
I can confirm that the issue is still present in the 64-bit version of Mageia 4. I haven't changed the platform as I have no reason to believe it is unique to this architecture.
Status: RESOLVED => REOPENEDVersion: 3 => 4Resolution: OLD => (none)
Running Cauldron. I have Gnucash running. Tried to install guile 1.8. rpmdrake wouldn't let me without uninstalling guile 2.0.9 and gnucash. But is that the original bug as set by Remco? I have no trouble starting gnucash-2.6.5 from the console or from a launcher.
Sorry, for "console" I should have written "xterm."
Doug has a valid point - the bug headline is not the problem we now have (which is that Gnucash and Lilypond can't co-exist). Would the package maintainer like me to open this as a new bug (although this is what my original bug report 7756 said, and this was marked as a duplicate)?
addendum: can't co-exist when installed from rpmdrake.
Fair comment. They are marked as incompatible. I don't understand why. In the beginning of Mageia, Virtualbox needed an old version of Python. As I understood the official reaction, it was that "We will use the version we have. The problem is VirtualBox', not ours." But the problem was that of the users who looked elsewhere. I simply downloaded the RPM from Mandriva's repo and installed it alongside the Mageia RPM. If you can install both versions of the library without ill effects, there is no reason why it can't be made possible.
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
I will confirm this one, but the ONLY fix is to install guile 1.8. Other distros do it, but really, lilypond needs to get updated to current libraries.
Thomas, could you have a look at this issue? It looks like gnucash's maintainer happily ignored this bug for 3 years, and maybe you have some ideas as lilypond maintainer.
Source RPM: gnucash.2.4.10-9.mga2 => gnucash, lilypondCC: (none) => thomasSummary: gnucash doesn't start => gnucash and lilypond can't coexist due to conflicting guile versions
I would rather blame Lilypond. The current version of Lilypond is 2.19.27, (unstable) released on Sep 12 last, and it still does not work with the Series 2 of guile. It may be just a nuisance bug now. How often does the clash really matter? For myself, I now use MuseScore, and I am slowly transferring my Lilypond files to MuseScore format. I needed one last week (the first for months,) and to avoid the hassle, I entered it afresh into MuseScore.
As I said in another report, the Lilypond folks are still pretty clear that it will not work with guile (2). I packaged it using guile2 and so far (although not much testing) I haven't discovered any problem using it. On the other side, I believe we have fixed the coexistence of GnuCash and lilypond in mga5. But I need to do some testing to confirm.
mga5 doesn't have this problem. I installed both with # urpmi gnucash lilypond It installed 65 deps and I run GnuCash and lilypond So thsi bug doesn't apply to mga5. Who is going to close it?
Thanks for checking Thomas, closing as OLD then.
Status: REOPENED => RESOLVEDResolution: (none) => OLD
Confirmed. I have gnucash installed and as a test, ran "sudo urpmi lilypond." I wasn't told to remove gnucash first.