On Fri, 2008-05-02 at 10:14 -0400, Matthias Clasen wrote: > On Fri, 2008-05-02 at 09:31 -0430, Patrick O'Callaghan wrote: > > On Fri, 2008-05-02 at 09:02 -0400, Matthias Clasen wrote: > > > On Fri, 2008-05-02 at 08:59 -0400, Konstantin Ryabitsev wrote: > > > > On Fri, May 2, 2008 at 12:46 AM, Patrick O'Callaghan > > > > <pocallaghan@xxxxxxxxx> wrote: > > > > > Does that actually remove it if it already exists? I normally run KDE > > > > > but tried Gnome for a day or two just for laughs, and now I see a .gvfs > > > > > in my home directory, which I can't even run "ls -l" or "file" on, > > > > > including as root. I get "cannot access .gvfs: Transport endpoint is not > > > > > connected". If I hadn't read somewhere about the new GVFS filesystem I > > > > > would be totally at a loss as to what this was, and with no idea as to > > > > > how to find out. > > > > > > > > It seems to have also screwed up my backups -- is .gvfs a special kind > > > > of file? Duplicity doesn't like it one bit. > > > > > > It is just a directory. It is used as mountpoint for a fuse mount, which > > > has quite a few tools struggling a bit... > > > > If it's "just a directory" I should be able to do this: > > > > # ls -ld .gvfs > > ls: cannot access .gvfs: Permission denied > > > > This is simply unacceptable. A mysterious file in my home directory that > > I can't discover *anything* about! > > Running mount will tell you something about it True, but who thinks "Permission Denied? Oh, I'll just run 'mount'"? The basic tool for finding out about a file is 'ls' (followed in some case by 'file'). That's what one uses many times a day and it should be able to tell me something intelligible if run as root. I presume this is a bug in GVFS. poc -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
