Hi all,
This is a Hardy updated/upgraded machine. I don't have anything of samba. The
only thing I have is ntfs3-g driver which uses fuse, I think that's why I have
.gvfs
$ ls -ld .gvfs
dr-x-- 2 shirish shirish 0 2008-10-23 21:08 .gvfs
Ralph, this is what it shows on my system (using
I ran into this bug while trying to accomplish
sudo ls -l .* user.txt
ls: cannot access .gvfs: Permission denied
if you see any error with this please lemme know.
--
Superuser cannot access ~/.gvfs folder when mounted
https://bugs.launchpad.net/bugs/225361
You received this bug notification
That (user others than the one who mounted the fs can't access it, including
root) is not completely true.
I have two systems (not connected to eachother), both running Ubuntu 8.04.
On one of them I have one user, created during install, and member of
sudoers. On this system I use a script that
In my opinion, this doesn't reall give enough information to confirm
that the behaviour isn't down to user error. For example, on the second
machine the cut-and-pasted output of
for u in A B C; do ls -ld /home/$u{,/.gvfs}; df /home/$u/.gvfs; id
$u; done
would be useful.
--
Superuser
upstream closed the bug as not a gvfs one
This is all unfortunate, but its a decision that has been taken by the fuse
people at the kernel level (user others than the one who mounted the fs can't
access it, including root) and there is nothing we can do about it.
** Changed in: gvfs (Ubuntu)
** Changed in: gvfs
Status: New = Invalid
--
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
Apparently I didn't have any .gvfs filesystems mounted, because now that
I have VirtualBox-OSE-modules installed, it's causing the .gvfs
permission errors all over again. Sorry for the confusion!
--
Superuser cannot access ~/.gvfs folder when mounted
https://bugs.launchpad.net/bugs/225361
You
that's no issue but 8 comments have been added in a few days now which
means 8 mails sent to whoever is subscribed to the bug
--
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
could people stop adding comments to this bug? the bug has been marked
triaged and no confirmation is required, you are just mail spamming
other subscribers now
--
Superuser cannot access ~/.gvfs folder when mounted
https://bugs.launchpad.net/bugs/225361
You received this bug notification
It may have originally been confirmed and triaged but surely it's normal
to respond to a `It looks like it's recently been fixed, please check'
request. To not do so might mislead people into thinking it has indeed
been fixed. That is not spamming.
--
Superuser cannot access ~/.gvfs folder
there is no reason why the issue should have changed since gvfs didn't
change recently and one person replying is enough in any case, no need
to have several comments stating the same thing
--
Superuser cannot access ~/.gvfs folder when mounted
https://bugs.launchpad.net/bugs/225361
You
I'm sorry my comment was regarded as spam. I woke up that morning and
noted that .gvfs was no longer causing me any exceptions in my nightly
rsync, where it had generated issues every night since I upgraded to
hardy. I don't know what changed, but felt it might be important to tell
someone that
Me too same problem as Ralph
sudo strace -e trace=lstat64 stat /home/pt123/.gvfs/
[sudo] password for pt123:
lstat64(/home/pt123/.gvfs/, 0xbffba7b4) = -1 EACCES (Permission denied)
stat: cannot stat `/home/pt123/.gvfs/': Permission denied
Process 8670 detached
Linux 2.6.24-18-generic #1 SMP
It appears the latest round of updates has fixed this. Please check to
see if you're still having this issue.
--
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
This is an up to date 8.04 i386.
$ sudo strace -e trace=lstat64 stat /home/ralph/.gvfs
lstat64(/home/ralph/.gvfs, 0xbfe8be54) = -1 EACCES (Permission denied)
stat: cannot stat `/home/ralph/.gvfs': Permission denied
Process 30706 detached
$
I think the problem still exists.
Here's the results on my system:
[EMAIL PROTECTED]:~$ sudo strace -e trace=lstat64 stat /home/craig/.gvfs
[sudo] password for craig:
lstat64(/home/craig/.gvfs, {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
File: `/home/craig/.gvfs'
Size: 4096Blocks: 8 IO Block: 4096
Interesting. There's a couple of differences in the .gvfs inode between
the two of us. Your perms are 0700, mine are 0500. Your access time is
today but your modify and change aren't, all three of mine are the same
value. Do you have anything mounted on .gvfs, if not, perhaps it's just
a
what about --exclude=~/.gvfs ?
I don't think most shells will expand the tilde when it's not at the
start of a word like that.
$ echo --exclude=~/foo
--exclude=~/foo
$
The problem here isn't that the issue can't be worked around, typically
adding an --exclude or several as Chris
what about --exclude=~/.gvfs ?
2008/6/5 Chris Hines [EMAIL PROTECTED]:
I am by no means an expert in development, but I've been getting around
this by adding --exclude /home/.../.gvfs. It's worked, although it's a
pain to backup more than one home account at a time. I'm not sure if
this is
I am by no means an expert in development, but I've been getting around
this by adding --exclude /home/.../.gvfs. It's worked, although it's a
pain to backup more than one home account at a time. I'm not sure if
this is relevant at all to the correction of this bug.
--
Superuser cannot access
Is there a particular package that is causing this error to occur, and
if so, is it possible to remove this package without seriously hampering
the user experience? I'm finding it's cropping up more and more in my
daily activities, and I want to get rid of it.
--
Superuser cannot access ~/.gvfs
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
discussing the setting is not really useful too, setting to medium to
avoid random comment but the issue is a manpower one mainly and the
change is not going to make a real difference there if nobody starts
working on the issue
--
Superuser cannot access ~/.gvfs folder when mounted
the permission issue is a fuse one, not really due to gvfs, the mounts
could be using a different directory though
** Changed in: gvfs (Ubuntu)
Importance: Low = Medium
--
Superuser cannot access ~/.gvfs folder when mounted
https://bugs.launchpad.net/bugs/225361
You received this bug
there is a bug about the issue on
http://bugzilla.gnome.org/show_bug.cgi?id=534284
** Changed in: gvfs (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs)
Status: Confirmed = Triaged
** Also affects: gvfs via
** Changed in: gvfs
Status: Unknown = New
--
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
This bug should clearly be confirmed. As well as Thomas Nybergh
spotting the same problem, I also raised a duplicate, bug #227724.
** Changed in: gvfs (Ubuntu)
Status: New = Confirmed
--
Superuser cannot access ~/.gvfs folder when mounted
https://bugs.launchpad.net/bugs/225361
You
drwx-- 2 wg wg 4096 2008-04-25 23:12 /home/user/.gvfs
I'm sorry, I forgot to replace wg (the real user name) by user for
readability:
drwx-- 2 user user 4096 2008-04-25 23:12 /home/user/.gvfs
--
Superuser cannot access ~/.gvfs folder when mounted
I'm experiencing a similar problem.
I did a clean install of 8.04 (32 bit, alternate installer) without
overwriting my /home. After the install, I created a user and changed
ownership of the old /home/thomas, but when I was about to remove parts
of my settings files i encountered permission
29 matches
Mail list logo
