https://bugs.kde.org/show_bug.cgi?id=480134
--- Comment #125 from caulier.gil...@gmail.com --- Hi Maik, Replacing KService with an alternative sounds like a very complex task. We can also disable the KService calls in digiKam in case of AppImage, but we will lack important features. So we need to understand why the crash in KService appears here. I surprised about to see a crash when we use a dedicated Ksycoca database file name. This must prevent a concurrent access. Perhaps we needs to use mutex here. I see also in the KF5 implementation some problems with memory sharing (typically under Windows only). There are also thread usages where protection must be set... Gilles -- You are receiving this mail because: You are watching all bug changes.
