A recent upgrade to kmymoney resulted in breakage. kmymoney will not start reports following error: kmymoney: error while loading shared libraries: libkmm_models.so: cannot open shared object file: No such file or directory
Very strange. A few questions to tackle this: a) How did you install the software? Did you compile yourself or used some package? b) What is the output of the following two commands on your system: ldd /usr/bin/kmymoney | grep models find /usr -name libkmm_models.so I see here: thb@thb-nb:~$ ldd /usr/bin/kmymoney | grep models libkmm_models.so => /usr/lib64/libkmm_models.so (0x00007f8c15975000) thb@thb-nb:~$ find /usr -name libkmm_models.so /usr/lib64/libkmm_models.so
Hello Thomas, As it was listed above this was installed as an apt upgrade from the repositories. Worth noting: I am running the development version of neon. The library in question is missing. Similar omissions have happened before with the kmymoney. I am betting that someone simply forgot to link this library as a dependency. However, to answer your other queries: ldd /usr/bin/kmymoney | grep models: libkmm_models.so => not found find /usr -name libkmm_models.so: Nothing listed
Then this is clearly a packaging problem. I doubt that it is a missing dependency as the library in question is built as part of KMyMoney and the regular build system installs it as part its run (make install). So we need to contact the packager to make him aware of the problem.
Agreed on the packaging issue, and isn't that what this 'bug tracking system' is for... to alert the Neon Team that there is a problem with this package? Would it be better if I posted such bug reports to the KDE Neon Mailing List?
Yes, but this bug tracking system is not for neon only but for all of KDE devlopment and the product KMyMoney is used for KMyMoney development/bug fixing not for packaging. That is why I moved this entry to the neon queue so that someone can take care of it and fix it.
Thank you for attention to this matter.. but must you state the obvious? The Platform field above is there to address many distributions. Friendly Advice: Several times you nonchalantly stuck a few digs to me.. But I understand that such digs feed some peoples ego.. It is support such as this that makes users shy away from posting. Be a little less condescending and more people might post bugs. It's just something to think about.. You have a great day.
Packaging updated, rebuilding now, thanks for the report Indeed Neon bugs best on the neon product, one of the nice things about being a KDE project is bugs can be easily reassigned. https://packaging.neon.kde.org/extras/kmymoney.git/commit/?id=3de32070ea8e38ac2a7811731bc40a2e61e56bff
Git commit 8bdae55854dd96171e0306cc0ee1c6317b6e4aa4 by Thomas Baumgart. Committed on 04/06/2018 at 13:16. Pushed by tbaumgart into branch 'master'. Correctly version libkmm_models.so M +1 -0 kmymoney/models/CMakeLists.txt https://commits.kde.org/kmymoney/8bdae55854dd96171e0306cc0ee1c6317b6e4aa4
Thomas now I have the same issue with libkmm_payeeidentifier_loader.so. Should that get a version or just package it unversioned?
(In reply to Nicholas Loch from comment #6) Nicholas, such things are not at all obvious to everyone, so stating them is very reasonable. With neon listed as the platform, but not as the product, the bug went to the KMyMoney queue, and would not likely have been seen by any neon developer without changing the queue, which is what Thomas did.
Git commit dd77e1f94f1d6c56bc4ca59e5e6380f7f41a7fee by Thomas Baumgart. Committed on 04/06/2018 at 17:58. Pushed by tbaumgart into branch 'master'. Correctly version libkmm_payeeidentifier_loader Now all shared libraries have a valid so version M +2 -0 kmymoney/mymoney/payeeidentifier/CMakeLists.txt https://commits.kde.org/kmymoney/dd77e1f94f1d6c56bc4ca59e5e6380f7f41a7fee
sorted although other compile problems now affecting build
Hi Jack, OK.. I guess my ego was a bit bruised and I lashed out. I will try to be more precise in future posts or I will wait for someone else to point out a bug.. Jonathon thanks for taking care of this issue.. waiting patiently for a working build.