Bug 372801 - Can't stream files from SMB in unsupported applications
Summary: Can't stream files from SMB in unsupported applications
Status: RESOLVED DUPLICATE of bug 75324
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
Depends on:
Reported: 2016-11-22 17:40 UTC by Miha Frangež
Modified: 2016-11-23 10:12 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Miha Frangež 2016-11-22 17:40:14 UTC
Opening a file from SMB sends a program the SMB uri instead of a local representation of the file. Since most programs aren't (and shouldn't) be capable of opening files from the network, this usually fails.

After editing vlc.desktop to remove smb (it doesn't work), I had to wait 2 minutes for Dolphin to download a video file from a local server, just to check if I've seen it already. This is terrible UX. 

A media player plays media files. If it can do it over SMB, that's cool, but it shouldn't be a requirement.

I really don't want to sound ungreatful to all the devs working on KDE and the entire Linux ecosystem, but these small things are what keep the adoption low.

So, here is my proposed solution:
Mount everything. No need to decide whether to copy, mount or stream. Just mount the share when needed, then unmount it when all handles are closed. It's simple and it always works.
Using gvfs would also work, although I doubt any KDE dev would want to.

A few more advantages of this approach: terminal access to remote files, next/previous buttons in programs would work, links to remote files...

I know I could easily mount the share with a single command, but that is not my point. A normal use wouldn't do that and would immediately switch back to Windows (I've seen it happen).
Comment 1 Elvis Angelaccio 2016-11-23 10:12:24 UTC
there is already a similar report, let's continue there.

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