After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 340234 - Modify gnome-vfs2 so that write access to $HOME is not required
Modify gnome-vfs2 so that write access to $HOME is not required
Status: RESOLVED WONTFIX
Product: gnome-vfs
Classification: Deprecated
Component: File operations
2.14.x
Other All
: Normal enhancement
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-01 00:10 UTC by W. Michael Petullo
Modified: 2008-09-06 18:55 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description W. Michael Petullo 2006-05-01 00:10:00 UTC 
I am writing a CGI program that uses gnome-vfs2 to abstract various protocols. 
Version 2.14.1 of the gnome-vfs library will not initialize if the process does
not have write access to $HOME.  Allowing an Apache process to write to its
$HOME is often a bad idea.

Could gnome-vfs2 avoid requiring ~/.gnome2/gnome-vfs/ ?

Or, is the use of gnome-vfs2 by a CGI program just a bad idea?
Comment 1 André Klapper 2008-09-06 18:55:01 UTC 
gnome-vfs has been deprecated and superseded by gio/gvfs since GNOME 2.22, hence mass-closing many of the gnome-vfs requests/bug reports. This means that gnome-vfs is NOT actively maintained anymore, however patches are still welcome.

If your reported issue is still valid for gio/gvfs, please feel free to file a bug report against glib/gio or gvfs.

@Bugzilla mail recipients: query for
      gnome-vfs-mass-close
to get rid of this notification noise all together.


General further information: http://en.wikipedia.org/wiki/GVFS 
Reasons behind this decision are listed at http://www.mail-archive.com/gnome-vfs-list@gnome.org/msg00899.html