kded won't start anymore

[Andreas Pakulat]

On 27.06.08 15:42:51, David Faure wrote:
> On Friday 20 June 2008, Matt Rogers wrote:
> > On Fri, Jun 20, 2008 at 10:17:36PM +0200, Sven Burmeister wrote:
> > > On Friday 20 June 2008 17:44:20 David Faure wrote:
> > > > On Tuesday 17 June 2008, Andreas Pakulat wrote:
> > > > > kded should automatically restart
> > > >
> > > > Yes I think so too.
> > > 
> > > 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 would use 0 
> > > space if kded is active and help the users that do not know what's wrong if 
> > > cookies, global shortcuts etc. do not work anymore.
> > > 
> > > Sven
> > 
> > Or kded could just restart on its own like plasma does. 
> 
> Done now. This functionality is now available to all unique applications, using
> KCrash::setFlags(KCrash::AutoRestart) (after the kapplication exists).
> It works like the plasma handler (which I'll port to that shared code on monday),
> i.e. after a crash the autorestart is only re-enabled after 10 seconds.
> So it's no longer "one crash and you're doomed", it's now "two crashes within
> 10 seconds and you're doomed", and I think you'd have to be a pretty fast
> clicker to trigger the crashing action twice in 10s.

Well, the global-shortcuts crash is as fast as your cpu, its not
triggered by doing something, its simply triggered by reading global
shortcut config that contains "multimedia" keys (like play,pause,volume
up/down and also browse, email ...)

Anyway, thanks for this fix.

Andreas

-- 
Slow day.  Practice crawling.