I'd argue that, based on https://wiki.ubuntu.com/Bugs/Importance, this
bug's Importance should be Medium.  As described in the duplicate I
raised, things like automatically checking the success of a daily tar(1)
now fails because it always exits with a non-zero status instead of only
rarely:

For ~/.gvfs to not follow normal Unix semantics is a major pain.  As
root, one can normally tar up a user's home directory, perhaps as part
of a daily backup regime, without problems.  That's the point of running
it as root.  Since the introduction of ~/.gvfs:

    $ sudo tar cf /dev/null .gvfs .bash_profile
    tar: .gvfs: Cannot stat: Permission denied
    tar: Error exit delayed from previous errors
    $ echo $?
    2
    $

So checking the exit status of tar for any backups problems now fails.
Every day.

I'd argue tar is pretty core and it's having a medium or severe impact,
as outlined under Medium.

-- 
Superuser cannot access ~/.gvfs folder when mounted 
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

Reply via email to