https://bugs.kde.org/show_bug.cgi?id=431474
Heinz Wiesinger <ppr...@liwjatan.at> changed:
What |Removed |Added
----------------------------------------------------------------------------
Product|KScreen |frameworks-kcoreaddons
Component|common |general
Assignee|kscreen-bugs-n...@kde.org |mp...@kde.org
CC| |kdelibs-b...@kde.org
Version|5.20.5 |5.79.0
--- Comment #2 from Heinz Wiesinger <ppr...@liwjatan.at> ---
I tracked this down to a pthread mutex lock in libfam, used by KDirWatch in
libplasma_wallpaper_imageplugin.
I recompiled kcoreaddons with support for FAM disabled, so it's using inotify
instead and all issues are gone. Resume is fast, there are no more issues with
kscreen and kdevelop is more responsive as well.
What I don't know is what caused it and where *exactly* that bug is. I checked
with some other slackware developers and none other experienced the issues I
did, even with FAM. So it's not a general issue and either environmental or
caused by a combination of apps I'm using.
I'm tempted to say it's just a thread locking issue in FAM directly, and
there's nothing that can be done about it in kcoreaddons, especially with
inotify working fine. But I would appreciate nonetheless if someone with more
knowledge about FAM/inotify could chime in here.
--
You are receiving this mail because:
You are watching all bug changes.
