GNOME Bugzilla – Bug 325136
File Browser can't detect the new permission properties of one renamed object
Last modified: 2006-12-13 17:16:12 UTC
This bug has been opened here: http://bugzilla.ubuntu.com/show_bug.cgi?id=21554 "1.Open FileBrowser by click "Places"->"Home Folder"; 2.Open menu "File Browser"->"File"; 3.Create one new folder "permission_check"; 4.Rename folder "permission_check" to "permission_checked"; 5.Right click this folder and choose "properties" item; 6.Choose tag "Permissions", and it shows "The permission of 'permission_checked' could not be determined"."
Other ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/35332 "After creating a new directory or file (via right-click), the permissions of new directory or file begins showing as "The permissions of 'XXX' could not be determined." Some old files/directories also end up being affected. This occurs in both user's home and other places within filesystem (tested in the apache directory /var/www, but not elsewhere incase it led to major breakage) Permissions show fine via "ls -l" and file/directory usage is as per permissions shown with said command. Note: This is similar to, but not identical to this bug report --> https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/33211"
Other Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/nautilus/+bug/38679 "Can't Change Groups Back Once Changed In Nautilus Steps to reproudce: 1: Create a file with gedit. Type some things in it, and save it to ~/test 2: Open ~ in nautilus 3: Right click on test and click properties 4: Change the group to anything but the default 5: Close the properties window 6: Open the properties of test 7: It says "The permissions of this file cannot be determined." This is a bug, as you can determine the permissions the the command line and even change the group. Also along the same lines: Nautilus can't determine the permissions of a blank file. Strange. Perhaps related."
Works fine with GNOME 2.17.3 apparently, marking fixed