Please describe the problem:
Nautilus is currently unuseable on filesystems with POSIX ACLs set.
It shows readonly emblems on files an folders that are not writeable
acording to the standard unix permissions, but that are writeable 
according to ACLs. What it makes it reallyunuseable is that several 
actions like creating folders is not possible, because nautilus guesses 
that the user has no permissions.
At the moment, nautilus can not be used in corporate environments that
really need ACLs to allow fine granted permissions for example on group
folders.



Steps to reproduce:
1. create a folder on an acl capable filesystem, e.g. /tmp/acl-test 

2. set some acl entrys

# setfacl -m u::root:rwx,g::r-x,o::---,u:pa:rwx /tmp/acl-test

3. getfacl shows the following permissions:

# getfacl /tmp/ac-test# file: tmp/acl-test
# owner: root
# group: root
user::rwx
user:pa:rwx
group::r-x
mask::rwx
other::--- 

4. Try to work on that directory with user pa, who has full permissions


Actual results:
Although user pa has all permissions on the directory, he can not
create/delete folders/files on /tmp/acl-test using nautilus.
Besides, nautilus shows false emblems.

Expected results:
Unless there is ACL support in gnome-vfs one should be able to disable
the abbility of nautilus to guess which permissions a user has on a specific 
file or folder. Instead, nautilus should not disable any functionality like
folder creation or file deleting. Like KDEs konqueror, nautilus should try to
perform the requested action and if there are not enough permissions, there
should be an error message.

Does this happen every time?
Yes.

Other information: