On Wednesday 30 December 2009 23:29:47 Dietz Pröpper wrote: > Hi, > > I have already mailed to the list regarding this issue. > But it seems to me that not nepomuk is the culprit, as indicated > in the discussion. (see bug #560893) > > I built me a completely nepomuk-free digikam (at least I think I did ;-)) > but can still observe the same behaviour. Digikam eats 90+% of cpu time > after a short time running and does not terminate properly. > > Attached is a strace of a digikam running mad, being closed, hanging around > and then being killed. Dietz, Could I ask you to start the marble application, without digikam, and see if you get the same result. I suspect this issue is being caused by the marble plugin widget in digikam. Have a look at this report of mine: https://bugs.kde.org/show_bug.cgi?id=220236 Thanks, Mark
Attachment:
signature.asc
Description: This is a digitally signed message part.