http://bugzilla.opensuse.org/show_bug.cgi?id=980068
http://bugzilla.opensuse.org/show_bug.cgi?id=980068#c17
--- Comment #17 from Christopher Yeleighton
(In reply to Christopher Yeleighton from comment #14)
What error message?
Cannot load libkdeinit5_khelpcenter5.so: File not found.
And what are you doing exactly to get that error message?
I tell Konversation to show the handbook.
As I wrote, if I do that here, I only get "KDEInit could not launch khelpcenter5" which actually comes from susehelp. So sorry, I cannot reproduce this.
The message appears in .xsession-errors.
Just to be clear: I do agree with you in that point that if somebody needs a library, it should require it on a package level. Whether that is figured out by rpmbuild automatically (which is when it is linked in at "load-time"), or we add a manual dependency (necessary if it is loaded at run-time) is secondary though.
But we'd need to know *what* something loads it. And I don't see anything except khelpcenter5.
susehelp calls kshell5 and kshell5 probably talks to kinit5 (the utility is undocumented). So yes, I was wrong. Sorry about that. I suppose kinit5 loads libraries at runtime on demand and it is by design.
I try to explain the situation again: - KDE Frameworks check whether the executable "khelpcenter" exists. If it does, it gets started, if not a web browser is run instead. - We patch KDE Frameworks to use susehelp instead of khelpcenter. So in our case, KDE Frameworks check whether the executable (script) "susehelp" exists. If it does, it gets started, if not a web browser is run instead. - susehelp tries to find out on which desktop it runs. In a Plasma5 session, it basically just runs khelpcenter5.
So it seems that it would be appropriate to say that khelpcenter5 supplements susehelp and KF5.
I hope the problem is finally clear now.
So do I :-) -- You are receiving this mail because: You are on the CC list for the bug.