From kde-core-devel Sat Jun 21 18:18:17 2008 From: Lubos Lunak Date: Sat, 21 Jun 2008 18:18:17 +0000 To: kde-core-devel Subject: Re: kded won't start anymore Message-Id: <200806212018.17402.l.lunak () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=121407235920852 On Saturday 21 of June 2008, Sven Burmeister wrote: > On Friday 20 June 2008 23:38:54 Matt Rogers wrote: > > On Fri, Jun 20, 2008 at 10:17:36PM +0200, Sven Burmeister wrote: > > > One could create a plasmoid that checks every x seconds whether kded is > > > still running and displays a button to restart, if not. This way it Or one could stop being obsessed with Plasma and think it can solve everything including world hunger :). It doesn't make any sense to have UI elements for restarting an internal and vital KDE service, not to mention the fact that some people run KDE applications without Plasma. Besides, there already is an application responsible for launching other applications and keeping the track of it, and that is the session manager. In fact the session management protocol has support for such automatic restarting of apps, but it has never been implemented in ksmserver. If somebody feels like writing code for restarting, how about that ;) ? > So instead of hiding the problem, using a plasmoid or any other kind of > information, would enable the user to understand that issue to the extent > that he can avoid and report it, i.e. kded is crashing after I do xy. One > could display a short text which explains that without kded neither cookies > nor global shortcuts work and allow the user to restart kded, even though > he might not know anything about ALT+F2 or konsole. AFAIK kded can not be > started from the menu, even if one would assume that a user knows the name > of the app, which I consider highly unlikely. > > Without this the user is put in danger of either ending up with no kded, an > endless loop or not understanding the issue and hence reporting: my cookies > don't work, global shortcuts stopped working instead of: doing xy crashes > kded. > > I hope this explains why I am in favour of transparency and mediating 'Transparent' is a word for something that is there but cannot be seen, right :) ? That's not what you're describing. And I'd disagree, kded is supposed to try to sort out its problems on its own, since the user generally won't have any clue what it is all about anyway. -- Lubos Lunak KDE developer -------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: l.lunak@suse.cz , l.lunak@kde.org Lihovarska 1060/12 tel: +420 284 028 972 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz