SUMMARY I noticed that when I right click on a picture, and select Open in File Manager, instead of Dolphin showing the contents of the folder where the picture is located, nothing happens. Upon inspecting the running processes, I noticed that there's a stuck process that is using all the CPU: kde-open5 file://<path to folder> I don´t know when it started. I'm currently using the digiKam-8.4.0-20240421T104710-Qt6-x86-64.appimage, but it used to work in previous versions. I thought it might have something to do with the folder path having spaces or special characters, but it doesn't seem to matter. Also, running that kde-open5 command directly on a bash console seems to open Dolphin to that folder. STEPS TO REPRODUCE 1. Right click on a picture. Open in File Manager. OBSERVED RESULT Nothing happens EXPECTED RESULT File browser should open at that location. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 LTS digiKam-8.4.0-20240421T104710-Qt6-x86-64.appimage (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION
I'm already on a KF6 desktop. But I can also confirm the problem with the AppImage, Dolphin does not open. However, I don't have 100% system load, but I see these messages: /usr/bin/dolphin: /tmp/.mount_digiKaO1moPr/usr/lib/libQt6Gui.so.6: version `Qt_6.7.0_PRIVATE_API' not found (required by /usr/bin/dolphin) /usr/bin/dolphin: /tmp/.mount_digiKaO1moPr/usr/lib/libQt6Core.so.6: version `Qt_6.7.0_PRIVATE_API' not found (required by /lib64/libQt6Core5Compat.so.6) With my native Qt6 developer version there are no problems opening Dolphin. Maik
I can confirm the bug under Arch Linux with kioclient 6.0.4 (output of "kde-open --version"). When executing xdg-open like "xdg-open /path/to/file.txt", the kde-open5 command is called with a "file://path/to/file.txt" parameter and directly fails (as far as I can see with exit code 1 but without logging to stdout/stderr). When using xdg-open, this process is endlessly recreated causing a high CPU load. My expected behavior is that kde-open/kde-open5 is able to deal with "file://..." parameters. Relevant environment variables on my machine might be XDG_CURRENT_DESKTOP=KDE and KDE_SESSION_VERSION=5.