On Sunday 21 August 2011 Aug, Oswald Buddenhagen wrote: > On Sun, Aug 21, 2011 at 02:54:41PM +0200, Thiago Macieira wrote: > > On Sunday, 21 de August de 2011 12:25:52 Oswald Buddenhagen wrote: > > > yes, when the faulty module crashes. not so when it deadlocks or > > > busy-loops. also, a restart typically loses state. > > > > True, but I don't remember that happening a single time to me in the past 3 > > years. I remember seeing people complain about kded taking 100% CPU, but it > > hasn't happened to me. > > > yes, things have stabilized meanwhile. but the problem will re-appear > during the kde5 cycle. it's inherent, after all.
Actually kded using 100% cpu happened to me last week, when I was travelling. Took me some googling to figure out that it was some incompability with libntrack and that I needed to install that from source. I even had to use gnome as my desktop for a day before I had time to figure out what was going on... -- Boudewijn Rempt http://www.valdyas.org, http://www.krita.org, http://www.boudewijnrempt.nl