Here is a possible solution.

My system - Mint 19.1 x64 Cinnamon - had no .gvfs directory in /run -
but it did have one in /home, causing the rclone backup tool to report
errors. I discovered (from here:
https://forums.opensuse.org/showthread.php/387162-permission-denied-on-
gvfs) that I could remove the .gvfs folder thusly:

sudo umount /home/<username>/.gvfs
sudo rm -rf /home/<username>/.gvfs

(That webpage lists a different method for removing the directory. That
other method involves iodes; and that other method did not work on my
system, but the one I gave above did.)

So far, gvfs seems to work without the .gvfs directory in /home. (That
seems strange, considering there is no such directory in /run either.)
Nor has the .gvfs folder been regenerated - at least not yet.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/225361

Title:
  .gvfs can't be stat'd by root causing backup tools to fail

Status in gvfs:
  Expired
Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs package in ALT Linux:
  Expired

Bug description:
  Problem
  =======
  For security reasons ( possible DoS ), other users (esp. root) cannot access 
a fuse filesystem, and not even stat the mountpoint:

      $ sudo stat .gvfs
      stat: cannot stat `.gvfs': Permission denied
      $ sudo ls -la
      ls: cannot access .gvfs: Permission denied
      d?????????   ? ?     ?         ?            ? .gvfs

  This means "rsync --one-file-system" (and similar options for find,
  tar...) cannot know this is a different file system they actually want
  to exclude, and fail on the permission denied error.

  Please note that it is GOOD AND CORRECT that root cannot copy the
  .gvfs directory. The real problem is that the stat fails.

  Workarounds
  ===========
  * bind-mount the file system you want to backup beforehand (see comment #67)

  See also
  =======
  * Excellent description of the problem in bug 227724
  * fuse-devel mailing list saying this will all be solved someday using 
"private namespaces"
  http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/3497/focus=3502
  http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/7169/focus=7236
  http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/6197 (no answer at 
all)
  * Kernel documentation explaing the DoS
  http://www.kernel.org/doc/Documentation/filesystems/fuse.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/225361/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to