https://bugs.kde.org/show_bug.cgi?id=397953
--- Comment #11 from Méven Car <meve...@gmail.com> --- (In reply to Nate Graham from comment #5) (In reply to David Edmundson from comment #6) > >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 > > Because 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... Currently the File manager setting in componentchooser kcm, makes the selected file manager associated with mimetype inode/directory. The kcminit hook could just pick up this setting and apply it to $XDG_RUNTIME_DIR/dbus-1/services for file managers where there is a corresponding "[D-BUS Service] Name=org.freedesktop.FileManager1" service defined, excluding krusader and other File manager with no org.freedesktop.FileManager1 DBUS support, removing the transient file a the end of the session. Relevant spec: https://dbus.freedesktop.org/doc/dbus-daemon.1.html We are not the only ones dealing with the situation: https://bugzilla.redhat.com/show_bug.cgi?id=1394927 -- You are receiving this mail because: You are watching all bug changes.
