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 342033 - creating a folder to computer not permitted but folder listed anyway
creating a folder to computer not permitted but folder listed anyway
Status: RESOLVED WONTFIX
Product: gnome-vfs
Classification: Deprecated
Component: Module: (other)
2.14.x
Other All
: Normal minor
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-16 20:26 UTC by Sebastien Bacher
Modified: 2008-09-06 19:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Attachments
patch (825 bytes, patch)
2006-10-03 15:48 UTC, William Jon McCann
none Details | Review
updated patch (2.58 KB, patch)
2006-10-05 19:06 UTC, William Jon McCann
none Details | Review

Description Sebastien Bacher 2006-05-16 20:26:54 UTC
That bug has been opened on https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/40701

"Start ubuntu dapper in live cd mode

Open places->Computer

Right-Click in the right pane of nautilus , click "create folder"

An error pops up saying operation not permitted ,

but a new folder has been created !!"
Comment 1 Josselin Mouette 2006-08-23 13:26:15 UTC
This bug was also reported as http://bugs.debian.org/383931 in the Debian BTS. It is reproducible in computer:/// place as well as in network:/// or smb:///.
Comment 2 William Jon McCann 2006-10-03 15:48:23 UTC
Created attachment 73954 [details] [review]
patch

Those menu items probably should appear at all.  The action is sensitized by the result of fm_directory_view_supports_creating_files() which uses the result of fm_directory_view_is_read_only() which does:

return !nautilus_file_can_write (file);

Which does:

	return !nautilus_file_denies_access_permission
		(file, GNOME_VFS_PERM_ACCESS_EXECUTABLE);
Which does:
	/* File system does not provide permission bits.
	 * Can't determine specific permissions, do not deny permission at all.
	 */
	if (nautilus_file_info_missing (file, GNOME_VFS_FILE_INFO_FIELDS_ACCESS)) {
		return FALSE;
	}

So, adding the access fields to file-info and setting only readable should do it.
Comment 3 Christian Neumair 2006-10-03 18:40:28 UTC
William: Thanks for your efforts!

We seem to have two separate issues here:

a) Some VFS modules don't provide the GNOME_VFS_FILE_INFO_FIELDS_ACCESS bit which will make Nautilus think it's fine to attempt any file ops
b) Nautilus adds a ghost file, even if the creation failed

William: Your patch resolves a) for computer://. Maybe you could add similar code for network:// and smb://?
Comment 4 William Jon McCann 2006-10-05 19:06:34 UTC
Created attachment 74087 [details] [review]
updated patch

Also fixes smb and network.
Comment 5 Rouben Tchakhmakhtchian 2007-01-14 08:52:45 UTC
Does this patch work? Will it be incorporated into a GNOME release?
Comment 6 André Klapper 2008-09-06 19:10:52 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 these notification emails 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