Comment 38 for bug 870874

I investigated this some more and found the following:

- Added a local user (not in LDAP, but with home dir on NFS): this user can log in without problems
- For a newly created user in the LDAP server logging in doesn't work and appears to be hanging.
  + Several processes use a lot of CPU time:
    ++ gvfsd-trash --spawner :1.2 /org/gtk/gvfs/exec_spaw/0
    ++ //bin/dbus-daemon --fork --print-pid 6 --print-address 8 --session
    ++ nautilus -n
    ++ compiz
  + related to gvfsd-trash I found that on the NFS server the permissions and time of the directory ~/.gvfs are:
      drwx------ 2 gtest users 4.0K Apr 19 13:53 .gvfs
     whereas on the client machine ls -lad ~/.gvfs gives:
      dr-x------ 2 gtest users K Apr 19 15:36 .gvfs
     (the time on this last entry is correct). Subsequently I killed the gvfsd-trash process a couple of times (until it wasn't restarted anymore) and a partially working desktop showed up. With that I mean: the Unity bar was present, as well as the top menu bar with the status icons. However, in the central desktop space nothing but blackness. No program I started showed a window, although Alt-Tab showed their icons. I could also log out using the menu in the top right corner, but I had to hit the enter key to select logout from the popup window (which I couldn't see).
After that the permissions and time on the .gvfs directory where back at their original state (drwx and 13:53, respectively).

Maybe this bug isn't (only) related to at-spi2-core anymore, but also to gvfs?