https://bugs.kde.org/show_bug.cgi?id=397953
David Edmundson <k...@davidedmundson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|KIO::highlightInFileManager |KIO::highlightInFileManager
|does not respect default |does not respect default
|file manager setting when |file manager setting when
|chosen app implements the |launched via FileManager1
|FileManager1 DBus protocol |DBus activation
--- Comment #6 from David Edmundson <k...@davidedmundson.co.uk> ---
>Could the "default file manager" UI force the chosen app to be the one that
>exports the FileManager1 DBus interfac
In a way.
Very new DBus daemon also sources XDG_RUNTIME_DIR/dbus-1/services
Becuase it's transient, we can special case exporting the relevant file manager
there in some kcminit hook like the workaround above.
But it's more complex. If we exported krusader like that, it would get
activated, not register the bus name and the calling client would sit around
not getting a reply...
We can't use a custom desktop file tag as we need it in nautilus...
---
I don't understand the relevant of that list of other bug reports?
--
You are receiving this mail because:
You are watching all bug changes.
