From kde-core-devel  Fri May 26 15:45:47 2006
From: =?UTF-8?B?xLBzbWFpbCBEw7ZubWV6?= <ismail () pardus ! org ! tr>
Date: Fri, 26 May 2006 15:45:47 +0000
To: kde-core-devel
Subject: Re: D-BUS required changes in KDE 4
Message-Id: <447722AB.40901 () pardus ! org ! tr>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=114865838808298

Thiago Macieira wrote On 26-05-2006 18:37:
> David Faure wrote:
>> On Friday 26 May 2006 11:35, Thiago Macieira wrote:
>>> David Faure wrote:
>>>> On Friday 26 May 2006 11:20, Thiago Macieira wrote:
>>>>> There are two things I have found out during my port of kdelibs to
>>>>> D-BUS that we will have to address:
>>>>>
>>>>> 1) Currently, the D-BUS session daemon isn't automatically started.
>>>>> This requires the user to have his scripts set up to start the
>>>>> daemon *before* any KDE application is started. For a KDE session,
>>>>> we can fix that with startkde, but imagine a user running KMail in
>>>>> TWM: KMail will refuse to start.
>>>> We currently have code to start kdeinit (which starts dcopserver)
>>>> when a kde application doesn't manage to contact dcopserver (cf
>>>> KApplication::startKdeinit and KApplication::dcopFailure). Can't we
>>>> do exactly the same with DBUS?
>>> We could, but why not do it in the libdbus-1 library itself and let
>>> all programs using D-BUS to benefit from it?
>> Sounds good.
> 
> That does answer the question, though: is it a feature we should push for 
> in D-BUS or should we simply mandate that the daemon be running in all 
> circumstances?

The latter, distros should take care of that in init scripts.

/ismail