In an effort to assist further I installed smb4k from (KDE-Extra), but have not been able to replicate the issue you report. What smb4k action triggers it specifically?
For reference I get…
~> nm -D /usr/lib64/libsmb4kcore.so |grep _ZN9KFileItem16staticMetaObjectE
U _**ZN9KFileItem16staticMetaObjectE**
No, the smb4k version from KDE-Extra is what I have installed, but I was speculating if sauerland was referring to KDE-Frameworks being required as well for some reason. In any case, I’m not observing smb4k failing to load.
Yes, I installed the same version and demonstrated that the symbol in question is undefined, but it does not make the application crash (or unusable) during my tests using it. (I usually just rely on the Dolphin SMB KIO for accessing samba shares in any case.)
Just searched around and found https://www.reddit.com/r/kde/comments/uc9kr4/after_upgrading_to_plasmashell_to_5244_i_get_a/ which suggests incompatible versions of Plasma and Frameworks but no suggestion of how to fix it. How cold this happen on a new install of Leap 15.4. The only thing which did not change was my home directory, could this cause it? How can I tell if I do have incompatible versions? Plasma Frameworks is 5.90.0-bp154.1.42.
That thread suggested K3b will have the same issue and indeed when I installed it it does crash in exactly the same way with exactly the same error message and symbol!!!
Leap 15.4 does not even have smb4k. Do not blame Leap for something you do yourself.
Plasma Frameworks is 5.90.0-bp154.1.42
I do not know what exactly you mean with Plasma Frameworks, but current version of plasma-framework package in [noparse]KDE:Frameworks5[/noparse] is 5.96.0.
Of course not. Nobody said there is smb4k in [noparse]KDE:Frameworks5[/noparse] repository (unfortunately it is again impossible to understand what exactly you mean under “Frameworks”).
So the question is which repository should I be using for SMB4K in Leap 15.4?
The answer is “it depends”. There are two Leap 15.4 repositories in [noparse]KDE:Extra[/noparse] project. One builds against vanilla Leap 15.4 and another builds against [noparse]KDE:Applications[/noparse] which itself builds against [noparse]KDE:Frameworks5[/noparse]. I installed the former and it starts just fine.
10:~ # zypper ar obs://KDE:Extra KDE:Extra
10:~ # zypper in --no-recommends smb4k
bor@10:~> smb4k
Icon theme "breeze" not found.
bor@10:~>
The latter indeed has issues as of now, this is not unusual - some required packages failed to build, or something changed in structure/version/names/… of required packages so dependent packages fail to build until someone fixed them. So what you have there is outdated smb4k package which has been built against some earlier versions of KDE libraries that are no more available.
The answer is “it depends”. There are two Leap 15.4 repositories in KDE:Extra project. One builds against vanilla Leap 15.4 and another builds against KDE:Applications which itself builds against KDE:Frameworks5. I installed the former and it starts just fine.
I understand and the first one is what I want to use, I can understand if what I want from it has issues and maybe I have to fix that myself but so far I’ve not been able to easily find the Extra repository built against the vanilla 15.4, I thought I’d found it but obviously not and in my view it is not easy to find.