Bug 468010 - symbol lookup error in kibkmm_csvimportercore.so.5
Summary: symbol lookup error in kibkmm_csvimportercore.so.5
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: importer (show other bugs)
Version: 5.1.3
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-31 18:35 UTC by Clinton
Modified: 2023-05-01 03:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Clinton 2023-03-31 18:35:28 UTC
I've installed kmymoney in Manjaro from the community repo.

https://archlinux.org/packages/community/x86_64/kmymoney/

Install goes fine, all dependencies are met. However I get the console error:

    kmymoney: symbol lookup error: /usr/lib/libkmm_csvimportercore.so.5: undefined symbol: _ZNK14MyMoneyAccount10currencyIdEv

and then KMyMoney quits.

STEPS TO REPRODUCE
1. From an amd64 Manjaro installation, with KDE SC, install the kmymoney from the community repo.
2. Try to start it.

OBSERVED RESULT
It doesn't start.

Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 5.15.104-2-MANJARO (64-bit)
Graphics Platform: X11
Processors: 16 × Intel® Core™ i7-10700KF CPU @ 3.80GHz
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1650/PCIe/SSE2
Manufacturer: ASUS
Comment 1 Jack 2023-03-31 19:20:35 UTC
First, you mention Manjaro, but the link is for ArchLinux.  Is that correct?  I can imagine possible issues using an Arch package on Manjaro if any dependent packages have been compiled differently between the two systems. 
My memories of issues with symbols beginning with _Z are all Windows related, but in any case related to compiling/linking.
I would suggest reporting to a Manjaro forum or mailing list.
Comment 2 Clinton 2023-03-31 20:27:23 UTC
(In reply to Jack from comment #1)
> First, you mention Manjaro, but the link is for ArchLinux.  Is that correct?
> I can imagine possible issues using an Arch package on Manjaro if any
> dependent packages have been compiled differently between the two systems. 
> My memories of issues with symbols beginning with _Z are all Windows
> related, but in any case related to compiling/linking.
> I would suggest reporting to a Manjaro forum or mailing list.

Thanks for the quick reply. I just downloaded the package from the ArchLinux page listed, and compared it to the package downloaded from the Manjaro community repository and confirmed that they share the same md5sum. i.e.:

   https://archlinux.org/packages/community/x86_64/kmymoney/download/
   https://osmirror.org/manjaro/stable/community/x86_64/kmymoney-5.1.3-4-x86_64.pkg.tar.zst
   Both of which have md5sum: 49ed9b60dc03ef5d05d2d59bff0b57bb

So in this instance, ArchLinux is the correct downstream forum for addressing bugs, even though their packages are being reused by Manjaro. Manjaro doesn't even have a bugtracker for this or most other packages, for instance.

As to whether this is an upstream issue to be addressed here on the KDE bug tracker, or downstream with Arch, I am uncertain.
Comment 3 Jack 2023-03-31 20:59:10 UTC
It's a compile/link issue, not something in the code, so I don't see anything KMyMoney or KDE can do about it.  It's OK to leave this bug open for now, while you see what Arch says, and it would be worth posting a link here to their bug once you file it.  
In the past, I've mostly seen this type of issue on Windows, any my faulty memory says it's related to mismatched versions of dependencies, but take that with a grain of salt for now.
Comment 4 Thomas Baumgart 2023-04-01 07:58:26 UTC
Hmm, it's not a compile/link issue in the classical sense during build time but more a link loader problem, as it happens at runtime. The said symbol is not found when the csvimporter lib is loaded. The symbol MyMoneyAccount::currencyId() itself lives in the core library libkmm_mymoney.so.5. All this leads to the conclusion that this is a downstream/packaging issue but certainly not an upstream KDE one.

@Jack: Regarding the construction of mangled names see e.g. http://web.mit.edu/tibbetts/Public/inside-c/www/mangling.html. This is not (only) related to Windows.

_ZNK14MyMoneyAccount10currencyIdEv

_Z name is mangled
N nested name indicator
K const indicator
14 length of name MyMoneyAccount
10 length of name currencyId
Ev argument void

and in class MyMoneyAccount you find "QString currencyId() const;"
Comment 5 Jack 2023-04-01 20:22:43 UTC
I do realize there is nothing windows specific about this.  I also think I found the same page on name mangling.  Am I correct that it seems to imply that the names have been mangled differently in the calling and called files, probably due to the two files being compiled by different tool chains, or some similar issue?  Might it be that the csvimporter plugin is not part of the newly installed version, but is left over from some earlier version, from a different repo?
Comment 6 Bug Janitor Service 2023-04-16 03:45:40 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-05-01 03:46:15 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!