A tester has run into the following bug when opening the "file browser" tool window of RKWard, installed from a Mac .DMG, created on the binary factory. While, here, it is about kioslave, I suppose that similar bugs will be lurking at various other place related to "libexec" binaries: Unable to create io-slave. Can not find 'kioslave' executable at '/Users/rkward/Music/rkward.app/Contents/MacOS, /Users/rkward/Music/ rkward.app/Contents/libexec, /Users/packaging/Craft/BinaryFactory/ macos-64-clang/lib/libexec/kf5' Now, this corresponds to the follow source code in kio: https://cgit.kde.org/kio.git/tree/src/core/slave.cpp#n506 I.e. these paths correspond to QCoreApplication::applicationDirPath(), QLibraryInfo::location(QLibraryInfo::LibraryExecutablesPath), and then the compile-time path, respectively. For Mac, neither the first nor third would be suitable options (but notably, the third path is probably hiding the bug from developers!). QLibraryInfo::LibraryExecutablesPath should be usable, but not trivially so: 1. The "libexec"-folder is at XYZ.app/Contents/Frameworks/libexec, and that does seem more reasonable than XYZ.app/Contents/libexec . If we want to use that, one way will be to append to qt.conf (already created by macdeployqt): "LibraryExecutables = Frameworks/libexec" 2. However, the follow-up problem is that most binaries are in subfolders "kf5"/ "kauth". This is not where the above code is looking, however. It looks directly in libexec . So the installation directory should probably omit the "kf5" as on Windows (https://cgit.kde.org/extra-cmake-modules.git/tree/kde-modules/KDEInstallDirs.cmake#n441).
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!