Please describe the problem:
Hello,
gvfs tries to find .Trash and .Trash-xxx entries in directories which are controlled by autofs. This causes automount to mount the corresponding trash directory which usually doesn't exist. This is just annoying as it wastes system (and in the case of NFS network) resources and fills the system log with error messages.


Steps to reproduce:
1. Create a automounter map to map a directory tree via NFS. Example:
       auto.master:
                 /net auto.net
       auto.net:
                 home -fstype=nfs myhost:/nsfexport/home
2. Start automounter
3. Start GNOME
4. cd into /net/home

Please note that this problem is not limited to NFS mounts. It also happens with local automounts.


Actual results:
The system mounts /net/home properly when accessed. However, it also tries to mount /net/.Trash and /net/.Trash-<uid>, which don't necessarily exist on the NFS server. Therefore, automount prints lots of error messages about not being able to mount /net/.Trash etc.

Expected results:


Does this happen every time?
Yes

Other information:
After taking a look at the source code of gvfs-trash.c, it should probably either observe the 'is_system_internal' flag of g_get_unix_mounts(), or alternatively observe the indirect mount flag, which gets set with all root directory automounts.