From kde-devel Tue Jul 01 10:18:10 2014 From: Aleix Pol Date: Tue, 01 Jul 2014 10:18:10 +0000 To: kde-devel Subject: Re: Should KDED4 run all the time? Message-Id: X-MARC-Message: https://marc.info/?l=kde-devel&m=140420994916755 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============8741157073143599640==" --===============8741157073143599640== Content-Type: multipart/alternative; boundary=001a11c1736ef87a8a04fd1f18f1 --001a11c1736ef87a8a04fd1f18f1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Jul 1, 2014 at 4:45 AM, Ian Wadham wrote: > Hi Sune, > > Thanks for replying, Sune. > > On 30/06/2014, at 11:37 PM, Sune Vuorela wrote: > > On 2014-06-28, Ian Wadham wrote: > >> When fixing some bugs in the KCrash-DrKonqi sequence on Apple OS X, > >> I have come to a point where Dr Konqi attempts to call kded4, using > DBus, > >> and issues a message "Failed to communicate with kded. Make sure it is > running." > > > > In the kdelibs4.x-age, yes. kded should be running all the time no > matter what. > > In Linux and a KDE desktop manager, that is fine: kded4 is part of the > structure > of a KDE desktop manager. But in Apple OS X (or other desktop managers), > that > should not be a requirement, if KDE is to be truly portable. > > Other desktop managers have their own ways of handling directory and file > changes, > battery level updates, device mounts, software update registration or > whatever. So > maybe kded4 is not really needed at all on such platforms. > > In particular, the absence of kded4 should not prevent a user from > reporting > a crash in a KDE application on Apple OS X or any other desktop manager, > should it? I don't think *anything* should prevent that=E2=80=A6 :-) > > I do not think it is reasonable to ask the MacPorts developers to include > kded4 in startup procedures for every user, on the off chance that he or > she will use a KDE app sometime and that app will crash. > > So I will proceed to patch around the requirement for kded4 in Dr Konqi i= n > Apple OS X, unless someone has a better idea or can point out some more > frequent and vital need for kded4 in a non-KDE desktop manager. > > > Unfortunately, it isn't refcounting its users so it is running like > forever. > > Cheers, Ian W. > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to > unsubscribe << > Yes, I agree that with portability in mind, requiring a kded running with some services kills the mood quite a bit. Patches are welcome indeed, although I wonder whether it wouldn't be interesting to look into this on KF5 already, but maybe it just doesn't make a difference. Aleix --001a11c1736ef87a8a04fd1f18f1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, Jul 1, 2014 at 4:45 AM, Ian Wadham <iandw.au@gmail.com>= wrote:
Hi Sune,

Thanks for replying, Sune.

On 30/06/2014, at 11:37 PM, Sune Vuorela wrote:
> On 2014-06-28, Ian Wadham <ia= ndw.au@gmail.com> wrote:
>> When fixing some bugs in the KCrash-DrKonqi = sequence on Apple OS X,
>> I have come to a point where Dr Konqi attempts to call kded4, usin= g DBus,
>> and issues a message "Failed to communicate with kded. Make s= ure it is running."
>
> In the kdelibs4.x-age, yes. kded should be running all the time no mat= ter what.

In Linux and a KDE desktop manager, that is fine: kded4 is part of th= e structure
of a KDE desktop manager. =C2=A0But in Apple OS X (or other desktop manager= s), that
should not be a requirement, if KDE is to be truly portable.

Other desktop managers have their own ways of handling directory and file c= hanges,
battery level updates, device mounts, software update registration or whate= ver. =C2=A0So
maybe kded4 is not really needed at all on such platforms.

In particular, the absence of kded4 should not prevent a user from reportin= g
a crash in a KDE application on Apple OS X or any other desktop manager, should it? =C2=A0I don't think *anything* should prevent that=E2=80=A6 = :-)

I do not think it is reasonable to ask the MacPorts developers to include kded4 in startup procedures for every user, on the off chance that he or she will use a KDE app sometime and that app will crash.

So I will proceed to patch around the requirement for kded4 in Dr Konqi in<= br> Apple OS X, unless someone has a better idea or can point out some more
frequent and vital need for kded4 in a non-KDE desktop manager.

> Unfortunately, it isn't refcounting its users so it is running lik= e forever.

Cheers, Ian W.

Yes, I = agree that with portability in mind, requiring a kded running with some ser= vices kills the mood quite a bit.

Patches are welcome indeed, although I wonder wh= ether it wouldn't be interesting to look into this on KF5 already, but = maybe it just doesn't make a difference.

Aleix
--001a11c1736ef87a8a04fd1f18f1-- --===============8741157073143599640== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << --===============8741157073143599640==--