Description of problem:Gnucash dependencies libgncmod-**-utils are installed under /usr/lib/gnucash, but gnucash can't find them. Applies to /usr/lib64/gnucash/libgncmod-gnome-utils.so and ditto/libgncmod-app-utils.so at least Version-Release number of selected component (if applicable): How reproducible: gnucash can't start. I added a link from libgncmod-gnome-utils.so to /usr/lib64/libgncmod-gnome-utils.so, now libgncmod-app-utils.so is blocking the startup. Steps to Reproduce: 1. See above. 2. 3.
I confirm the problem.
Severity: normal => majorCC: (none) => bittwister2
The code for gnucash has been completely rewritten. The folder /usr/lib64/gnucash contains about 18 library files and a subdirectory. Re-linking them all was a bit of a chore, and may have made upgrading difficult.
Assigning to the registered maintainer.
Assignee: bugsquad => lists.jjorgeCC: (none) => marja11
Hi. Can you please try with gnucash 3.4-3 just built. It will be available on the mirrors shortly. Cheers, Stig
CC: (none) => smelror
Will do, Stig. It is after midnight here.
$ gnucash gnucash: error while loading shared libraries: libgncmod-gnome-utils.so: cannot open shared object file: No such file or directory $ uname --processor x86_64
Source RPM: gnucash-3.4-1.mga7 => gnucash-3.4-3.mga7.src.rpm
Thanks for checking, Bits. Having a sleepless night. Unfortunately, my Comment 2 contained references to my posts on the newsgroup. libgncmod-gnome-utils.so is in the same folder as the ones I mentioned. My workaround was to add the folder /usr/lib64/gnucash to my LD_LIBRARY_PATH. That was a complete cure for me as user. No doubt the package could do the same as a system fix.
Thanks for testing. Have pushed 3.4-4 with the help of Jani and Zezinho. Cheers, Stig
As of just now, libgnucash0 has reached the mirrors, but not the gnucash rpm itself.
The gnucash rpm has now arrived, and yes, it starts without any hitches.
Installed rpm : gnucash-3.4-4.mga7 $ gnucash ran setup to completion. Have not done any other testing. Meets the go/no go test for me.
Bug seems fixed. Allowing the installer to find those libraries was the entire bug; any other problem is a fresh bug. Closing.
Status: NEW => RESOLVEDResolution: (none) => FIXED