Bug 98032

Summary: Automatically mount share that file is located on when file is accessed
Product: [Unmaintained] kio Reporter: Jarne Cook <j.cook>
Component: generalAssignee: David Faure <faure>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jarne Cook 2005-01-28 01:20:05 UTC 
Version:           2.3.1 (using KDE 3.3.2,  (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-6)
OS:                Linux (i686) release 2.6.10-i8600

This suppose this really should be a kdelibs/base (or something lower for all applications).

--
The file file:/home/jcook/mnt/jupiter/jcook/mta/mkvirtual/mkvirtual.php could not be loaded, as it was not possible to read from it.

Check if you have read access to this file.
--

That is the error message I get.


Now when I go to system:/ and open "Remote Share (www) [/home/jcook/mnt/jupiter/www]" it get's automatically mounted.

It would be nice if the kde libs would auto mount the share if a file is attempted to be read (or whatever).

(it would be ideal if the same thing was done at the kernel level but ... I dont see that happening)
Comment 1 Anders Lund 2005-01-28 10:25:45 UTC 
Reassigning to KIO, since this is not kate specific.
Comment 2 Nate Graham 2018-04-23 18:25:57 UTC 
If you use a KIOSlave to access the file, this works perfectly (e.g. you access it at "smb://myserver/myshare/path/to/file". If you use a manual mount (e.g. using `mount` or an fstab entry), then KIO can't have any knowledge of this because you didn't use it to mount the share, so it has no way of knowing that mounting some location is required to access the file.

If KIO could mount things itself, then it would know about mounts and this would work without you needing to acc the file using a KIO-compatible path such as "smb://myserver/myshare/path/to/file". That's tracked with Bug 75324.

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