Phillip Susi wrote: > That is really just a contributing factor, not the problem. The > problem is that people are having utilities fail when they run into > .gvfs because root can't access it ( and this is by design, not a bug > ).
It is a bug in that, under Unix, by design, that should *never* happen to a process running as root. > The utilities in question shouldn't be messing with .gvfs in the first > place, so a simple solution is to move it somewhere they aren't going > to run into it. Sorry, that's not possible. As root, it's entirely valid, and not uncommon, for me to run `find / ...' which will descend and find .gvfs wherever to decide to move it to. Nikolaus Rath and S B, take a look at my earlier comment https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/225361/comments/11 I understand this configuration of FUSE has been chosen because of security concerns, as opposed to using its allow_users or allow_root options. However, I'm not sure those concerns remain valid given Ubuntu automatically mounts the filesystems on a USB flash drive I insert, and I doubt every piece of filesystem code in the kernel is robust against maliciously concocted corrupt filesystems. -- ~/.gvfs causes various errors https://bugs.launchpad.net/bugs/225361 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
