Bug 134626

Summary: Suggestion of extending vfs2
Product: [Fedora] Fedora Reporter: bednar <borkows>
Component: gnome-vfs2Assignee: Alexander Larsson <alexl>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: mattdm
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-09-01 14:48:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description bednar 2004-10-05 07:17:43 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041002
Firefox/0.10.1

Description of problem:
Actually most of apps cannot directly open files form vfs folders. One
have to copy such file form e.g. sftp: share to local disk edit it and
then upload back (using Nautilus). 
In KDE the files accesses via for example fish: protocol are
immediately copied to /tmp edited and automagically copied back to
original location. It is transparent to the apps if file lie on local
filesystem or on remote.
I thing gnome-vfs should give same functionality to be user friendly
it is gnoem-vfs should be transparent for ALL application. 

Version-Release number of selected component (if applicable):
gnome-vfs2-smb-2.8.1-5
gnome-vfs2-2.8.1-5

How reproducible:
Always

Steps to Reproduce:
1.Open PDF from remote location under Nautilus (sftp://)
2.
3.
    

Actual Results:  The PDF reader (xpdf, acroread, gv) cannot open file
from remote share,
one should first copy PDF file to local fs.

Expected Results:  xpdf opens file without any warning

Additional info:

Comment 1 Matthew Miller 2006-07-10 23:08:52 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!