https://bugs.kde.org/show_bug.cgi?id=413825
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|1 |0
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
Priority|NOR |VLO
--- Comment #3 from Harald Sitter <sit...@kde.org> ---
What you describe is how a sound mail client would/will/does work though.
You really shouldn't force smb to open with dolphin specifically. You should
delegate the opening to actual "opening" technology, which dolphin is not.
e.g. `xdg-open` or `kioclient5 exec` both will correctly open any URI, be it
directory or file, with the relevant application as per the URI's mimetype. So,
if the URI points to a shared directory it will open in dolphin, if it points
to a pdf it will open in a PDF reader and so on and so forth.
Or to put it very simply: dolphin doesn't register for any file mimetypes, so
it can rightly expect to not ever be called with file URIs (some exceptions
apply; I am sure).
Funneling all URIs through dolphin is at best suuuuuuuuuuuuuuuper inefficient
because you are forking a GUI app to carry out the job of opening a resource
for which it will ultimately, likely, not be responsible. At worst it blows up
in ways like the one you describe because dolphin is not designed to be a file
opener.
That being said, I am rather thinking this bug is in Dolphin not SMB KIO. The
higher level application should query the mimetype from smb and then carry out
an action based on the result. Dolphin probably just wants to call listdir and
gets back that error.
Needs some investigation.
--
You are receiving this mail because:
You are watching all bug changes.
