[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdelibs-bugs
Subject:    [Bug 281312] Deadlock in FAM/KDirWatch usage
From:       Andreas Hartmetz <ahartmetz () gmail ! com>
Date:       2012-06-26 15:33:58
Message-ID: bug-281312-90985-vcWmyhKv9I () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=281312

Andreas Hartmetz <ahartmetz@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ahartmetz@gmail.com

--- Comment #20 from Andreas Hartmetz <ahartmetz@gmail.com> ---
AFAIK KDirWatch on FAM has never worked  well.
We had really bad problems with KDirWatch crashing kded4 in the time before the
4.0 release. Somebody fixed a typo in a preprocessor statement, which made FAM
the default backend, which seems to have been the intention at some point, but
didn't do anything due to the typo.
So we explicitly made inotify the default backend. FAM has not been fixed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Kdelibs-bugs mailing list
Kdelibs-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdelibs-bugs
[prev in list] [next in list] [prev in thread] [next in thread]