[KDE/Mac] org.kde.KLauncher service not found [help]

[Ian Wadham]

Hi René and David,

On 02/10/2015, at 10:23 PM, René J.V. Bertin wrote:
> On Friday October 02 2015 13:14:22 David Faure wrote:
>>> who takes care of [that=] launching kdeinit4, and how is it supposed to find kdeinit4?
> 
>> Well, kdeinit4 is started by KToolInvocation::startKdeinit() in kdecore.
>> 
>> It finds kdeinit4 on $PATH and just executes it.

I sometimes find that kdeinit4 and klauncher are running "magically"
on my OS X system and sometimes not.  I do not start them explicitly.

If they are not running, I get grumbles (on stderr), from kio and
knotification mostly (e.g. when a KDE 4 app I am developing uses
KMessageBox).  But I just ignore them and go soldiering on.

I know you cannot ignore them in KDE 4 apps more complex than
mine.  Things crash, modules go missing, etc.

That is why I was trying (in vain, ultimately) to get to grips with the
whole kdeinit4/klauncher4/kded4/kio complex and figure out how
it should fit in to the OS X environment.

> Ah, good (if that method is invoked when launching an app that needs the tool started through kdeinit4). That should mean that all I have to do is ensure that the kdeinit4 executable is in the path, probably through a wrapper script that does
> 
> open -W kdeinit4 --args "$@"

That is the least of your worries.

I believe that a lot of things in the kdeinit4/klauncher4/kded4/kio
complex do not work properly in an OS X environment and have
never been fully tested on OS X.

I also believe that, on OS X, some of the bugs in the KDE 4
versions will carry forward to the Frameworks versions.  IIUC
there has been a cleanup and simplification of the complex in
Frameworks, but, as far as I am aware, no *integration* testing
on OS X.

I hope I am wrong to be pessimistic about this, otherwise QSP
is going to look like a walk in the park…

Cheers, Ian W.