lodlock <lodlock@no-mx.forums.opensuse.org> wrote:
>
> When attempting to use the update system I receive a unable to stat and
> permission denied on /home/whatever/.gvfs
>
> When looking at it with an ls -l it looks like
>
> ??? ? ? ? ? ? .gvfs
>
> I can not chown, touch, edit, remove, or do anything as the user of the
> home dir or as root. Both receive a permission denied.
This is also causing problems with rsync backups of /home.
I am also having to same issue, but it seems to carry over if I wish to use the gnome right click option of “Install Software” I receive an error of cannot stat .gvfs
I did some configuring and want to put back my backed up files
I can access my network drive
I can not copy files over it says “permission denied”
User is owner of directory and has sufficient rights
Even using su doesn’t resolve this
On console it states “can not access .gvfs. Permission denied”.
I’m not able to delete the .gvfs directory (says it is in use)
I am able to create new directories in the home folder of the user
I’ve been looking on the Internet and haven’t found solutions and the given tips in IRC didn’t work out. Does anybody here have ideas on how to fix this issue, besides doing a total re-install?
FUSE directories are only accessible by the UID that mounted them (unless other options were using during mount). I find this gvfs stuff highly annoying anyway, why is it suddenly needed in 11.0?
Did anyone ever figure this out? I am having the same issue also. This /home/$USER/.gvfs file is impossible to take ownership of or change permissions on. I actually wanted to take ownership of my home folder to test a program that won’t run, and this untouchable .gvfs folder is in the way. Funny…
> Did anyone ever figure this out? I am having the same issue also. This
> /home/$USER/.gvfs file is impossible to take ownership of or change
> permissions on. I actually wanted to take ownership of my home folder
> to test a program that won’t run, and this untouchable .gvfs folder is
> in the way. Funny…
I think this is a “well-know” bug, reported several times. So, maybe still
not fixed:
I went with:
> bureau:/home/hadg # umount gvfs-fuse-daemon
> bureau:/home/hadg # rm -rf .gvfs
worked for me.
Still, this .gvfs folder is a hack, and it is wrong that this issue remains in 12.1 (and probably 12.2 as well).
Local user tries to eliminate .gvfs from their own home directory:
> hadg@bureau:~> rm -rf .gvfs
> rm: kan ‘.gvfs’ niet verwijderen: Apparaat of hulpbron is bezig
(“cannot delete: device or source is busy”)
Local user figures out mount:
> hadg@bureau:~> mount | grep gvfs
> gvfs-fuse-daemon on /home/hadg/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
> hadg@bureau:~> umount gvfs-fuse-daemon
> umount: gvfs-fuse-daemon staat niet in fstab (en u bent niet root)
(“not in fstab (and you are not root)”)
Local user should not need root privileges for ANYTHING that happens in /home/{username}/.
Root tries to eliminate .gvfs:
> bureau:/home/hadg # rm -rf .gvfs
> rm: kan ‘.gvfs’ niet verwijderen: Is een map
(“cannot delete: it’s a folder”)
((excuse me??? with rm -rf as root?!?!?!?))
Am I the only person who thinks that this is unacceptable, and is a patent violation of the UNIX-style security paradigm?
(And if it is a GNOME hack, then just why am I getting this while using KDE?? Probably some dependency needing cleaned up?)
If any of the “Big Wigs” are reading this, I look forward to your comments!
K.
Kalenz wrote:
> I went with:
>> bureau:/home/hadg # umount gvfs-fuse-daemon
>> bureau:/home/hadg # rm -rf .gvfs
> worked for me.
>
> Still, this .gvfs folder is a hack, and it is wrong that this issue
> remains in 12.1 (and probably 12.2 as well).
Personally, I agree with you. But this ‘hack’ has been around for a long
time and is unlikely to change anytime soon. So I think you’re wasting
your breath (sorry, fingertips).