KDEinit problem

[Waldo Bastian]

.desktop files have an entry X-DCOP-ServiceType and X-DCOP-ServiceName that 
essentially tell the launcher how the application will register itself with 
DCOP. Once the application has registered in that way, the launcher will 
return successfully.

In general, if the process that gets started exits before the application is 
registered with DCOP, it assumes something went wrong and returns an error.

X-DCOP-ServiceType can have the following values:
* None - Don't wait for DCOP registration, return success immediate.
* Unique - Application registers as a unique application
* Multi - Application registers as name-<pid>
* Wait - Wait till the process exists and return success.

On Saturday 31 December 2005 07:33, Anders Lund wrote:
> Hi,
>
> Since KDE 3.5 Kate is no longer a KUniqueApplication, instead we support
> named sessions, and also allows to open files in existing instances.
>
> The latter is implemented by using DCOP to find the application instance to
> use and ask it to open the URL. This is done in the main() function, and it
> seems to cause a problem with kdeinit, which experiences an error. For
> example when opening files from konqueror in this way (with --use in the
> kate command line) one gets 2 (!) errors with the text
>
>     "KDEInit could not launch 'kate'."
>
> I have tried calling KStartupInfo::setWindowStartupId( winId, startupId );
> with the result of KStartupInfo::currentStartupIdEnv() and the window ID
> retrived via DCOP and also calling KStartupInfo::appStarted( startupId ),
> to no avail. Looking at the kinit code (in klauncher) it seems like this
> error is produced when the process exits at a time that kinit feels is
> premature.
>
> The question is:
>
>   Is there a way to let kinit know that the request is sufficiently
> processed?
>
> TIA,
> -anders
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20051231/97cf1acd/attachment.sig>