https://bugs.kde.org/show_bug.cgi?id=365331
--- Comment #5 from RJVB <rjvber...@gmail.com> --- Edit: it would *seem* that the issue has resolved itself in 5.3.0 . I agree something was wrong, but digiKam is the only application where I've seen this happen with my build settings, and only for a few Qt libraries. I don't know how the AppImage stuff is finagled together, but I'm not using that. I'm just using unpatched CMake files and everything KF5 is built with the settings required to apply full rpaths to all binaries. Qt5 itself is built that way too. I'd agree the problem was fully on my end if I saw this happening to all Qt libraries (in DK or in other applications too), but that isn't the case. The simplest explanation would be that somehow the rpath information is dropped for the affected Qt libraries -- You are receiving this mail because: You are watching all bug changes.
