[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: Should KDED4 run all the time?
From: Aleix Pol <aleixpol () kde ! org>
Date: 2014-07-01 10:18:10
Message-ID: CACcA1Rop4631N6SsKuanQE=JfiAwYkK1OxvJJQWDBXiiH-FHYQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Tue, 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 <iandw.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, 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… :-)
>
> 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
> 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
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Jul 1, 2014 \
at 4:45 AM, Ian Wadham <span dir="ltr"><<a href="mailto:iandw.au@gmail.com" \
target="_blank">iandw.au@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi Sune,<br> <br>
Thanks for replying, Sune.<br>
<div class=""><br>
On 30/06/2014, at 11:37 PM, Sune Vuorela wrote:<br>
> On 2014-06-28, Ian Wadham <<a \
href="mailto:iandw.au@gmail.com">iandw.au@gmail.com</a>> wrote:<br> </div><div \
class="">>> When fixing some bugs in the KCrash-DrKonqi sequence on Apple OS \
X,<br> >> I have come to a point where Dr Konqi attempts to call kded4, using \
DBus,<br> >> and issues a message "Failed to communicate with kded. Make \
sure it is running."<br> ><br>
> In the kdelibs4.x-age, yes. kded should be running all the time no matter \
what.<br> <br>
</div>In Linux and a KDE desktop manager, that is fine: kded4 is part of the \
structure<br> of a KDE desktop manager. But in Apple OS X (or other desktop \
managers), that<br> should not be a requirement, if KDE is to be truly portable.<br>
<br>
Other desktop managers have their own ways of handling directory and file \
changes,<br> battery level updates, device mounts, software update registration or \
whatever. So<br> maybe kded4 is not really needed at all on such platforms.<br>
<br>
In particular, the absence of kded4 should not prevent a user from reporting<br>
a crash in a KDE application on Apple OS X or any other desktop manager,<br>
should it? I don't think *anything* should prevent that… :-)<br>
<br>
I do not think it is reasonable to ask the MacPorts developers to include<br>
kded4 in startup procedures for every user, on the off chance that he or<br>
she will use a KDE app sometime and that app will crash.<br>
<br>
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<br>
frequent and vital need for kded4 in a non-KDE desktop manager.<br>
<div class=""><br>
> Unfortunately, it isn't refcounting its users so it is running like \
forever.<br> <br>
</div>Cheers, Ian W.<br>
<div class="HOEnZb"><div class="h5"><br>
>> Visit <a href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub" \
target="_blank">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> to \
unsubscribe <<<br> </div></div></blockquote></div><br></div><div \
class="gmail_extra">Yes, I agree that with portability in mind, requiring a kded \
running with some services kills the mood quite a bit.</div><div \
class="gmail_extra"><br></div>
<div class="gmail_extra">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.</div><div class="gmail_extra">
<br></div><div class="gmail_extra">Aleix</div></div>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic