STEPS TO REPRODUCE 1. use a distribution with gnome 2. install Dolphin 3. download a file with Firefox or a chromium-based browser 4. when the download is completed, use the 'open containing folder' feature of your browser OBSERVED RESULT No file manager opens. 'Open containing folder' feature works again after uninstalling Dolphin. Journal log prints these messages after the provided steps : nov 14 13:14:47 arch-laptop dbus-daemon[6632]: [session uid=1000 pid=6632] Activating via systemd: service name='org.freedesktop.FileManager1' unit='plasma-dolphin.service' requested by ':1.109' (uid=1000 pid=8197 comm="/opt/vivaldi/vivaldi-bin --enable-crashpad https:/") nov 14 13:14:47 arch-laptop systemd[1183]: Starting Dolphin file manager... nov 14 13:14:47 arch-laptop dolphin[20873]: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. nov 14 13:14:47 arch-laptop dbus-daemon[6632]: [session uid=1000 pid=6632] Successfully activated service 'org.freedesktop.FileManager1' nov 14 13:14:47 arch-laptop systemd[1183]: Started Dolphin file manager. nov 14 13:14:48 arch-laptop systemd[1183]: plasma-dolphin.service: Consumed 1.024s CPU time. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6
EXPECTED RESULT: Dolphin should not break the 'Open containing folder' feature of internet browsers on Gnome
The reverse is also the case. Installing Nautilus on Plasma breaks Dolphin from being opened. It's kind of a fundamental flaw of the org.freedesktop.FileManager interface. It's undefined which implementation gets activated if there are multiple
I have Nautilus on my Arch Linux that runs Plasma 5.26.3. Nautilus instead of the default Dolphin opens. Possibly this bug is a duplicate of bug 397953
Yep. It's for this reason that on Fedora, they have a daemonized Dolphin instance constantly running in the background when you're in a Plasma session, so it will prefer the already-running app and always give you Dolphin. *** This bug has been marked as a duplicate of bug 397953 ***