kded4 lockup (which makes the desktop unusable so this is important)

[Michael Pyne]

On Thursday 08 May 2008, Andreas Hartmetz wrote:
> Did you know...
> FAM has been the default backend of KDirWatch for years but it was not
> actually used due to a typo in an #ifdef (!!!) that was fixed four
> days ago.
> As a workaround for that nasty lockup I have modified KDirWatch to use
> inotify as the default backend again, this time in a more obvious
> manner:
> *snip*

> I can't believe it.
> Update your kdelibs now.
> I believe that we should still look for ways to make kded (way) more
> robust. Strange things will happen everytime one module takes down or,
> worse, locks up kded.

Ironically as soon as I read this thread kded4 wedged in me in exactly this 
fashion... (second time I've seen it happen since I've been back)

If it happens again I'll post back.

Regards,
 - Michael Pyne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080508/abebaf28/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080508/abebaf28/attachment.sig>