Bug 395616 - KIO::highlightInFileManager does not respect default file manager preference when chosen app does NOT implement the FileManager1 DBus protocol
Summary: KIO::highlightInFileManager does not respect default file manager preference ...
Status: RESOLVED DUPLICATE of bug 397953
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.49.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-19 15:53 UTC by Till Schäfer
Modified: 2018-09-16 20:24 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Till Schäfer 2018-06-19 15:53:03 UTC
If a mail attachment is saved, a message pops up, that contains the button "Open folder where attachment was saved". The action of this button always triggers dolphin, even if another file manager (here: krusader) is selected in the system settings as the default file manager. 

Thus, kmail should respect the choice of the default file manager configured in the system settings.
Comment 1 Laurent Montel 2018-06-20 04:51:39 UTC
We use:
KIO::highlightInFileManager(mUrls);
Please report it against kio package thanks
Comment 2 Kai Uwe Broulik 2018-06-27 14:44:50 UTC
Krusader does not implement the org.freedesktop.FileManager1 interface. Only Dolphin (and Nautilus) do and are autostarted by DBus when a call is placed.
Comment 3 Till Schäfer 2018-06-27 15:15:21 UTC
Maybe a fallback would be good, that just starts the application if the current choice does not implement the DBUS interface. There may be a ton of other (maybe obscure) file managers or custom scripts (e.g., just drop to a shell) that do not implement the DBUS interface. 

Interestingly, the device manager respects my choice of file manager. Do they use KIO as well? Maybe, they have implemented a workaround?
Comment 4 Patrick Silva 2018-09-16 20:24:09 UTC

*** This bug has been marked as a duplicate of bug 397953 ***