Comment 98 for bug 1181666

Ok, I solved the problem in my case. Given it seemed to be a communication problem I go the idea it could be ownership of sockets. I found various folders in my home directory were not owned by my local user and/or were not readable. Root owned .dbus and .gvfs, below .local were files/folders owned by me but without read/write permission.

I did a "chmod u+rw -R ~.local" and "sudo chown -R [myuser]:[myusergroup] /home/[myuser]" and a reboot and so far no problems since a few hours.

Maybe it would be a good idea to check for that once in a while. There may be valid reasons of not-user-owned folders or files, but probably a warning message would help. Also I believe everything below .local should be read-writeable for the user and owned by it. Please correct me if I am wrong.