Comment 3 for bug 581352

I had a closer look and it is really a problem of the name for the gvfs mountpoint. I also realized that this problem has been reported before, and I'm closing this bug as a duplicate. Please have a look at bug 287689 for further information and maybe test the workaround posted there.