Please check, if this issue is still seen.
Thanks
** Changed in: gvfs (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/435719
Title:
gvfs-fuse fails to
** Changed in: gvfs
Status: New = Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/435719
Title:
gvfs-fuse fails to start on NFS mounted homes
To manage notifications about this bug
@John : I supposed it's a bash script?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/435719
Title:
gvfs-fuse fails to start on NFS mounted homes
To manage notifications about this bug go to:
Timo's workaround is just what I was looking for. I wouldn't use
/tmp/.gvfs-$USER though since that's a predictable location. On a
machine where lots of people log in to it someone could maliciously pre-
create such directories for other users resulting in at best denial of
service and at worst
@John: Did you take a look at the patch i have proposed, it wouldn't
need a big adjustment for your needs.
Anyhow great that there is some interest in this topic. Would be great
if we could bring a patch to the package in time for the precise
release.
What the patch is lacking beside John's
@ossjunkie: Didn't look at it before my previous comment as I hadn't
noticed it was there. It looks OK apart from the predictable location.
As you say, not a big adjustment to change that though.
# only apply when home directory is on NFS
if [ $(stat -f -L -c %T $HOME) = nfs ]; then
# remove
I just came across this bug when debugging OOo on SMB shares. Therefore
i enhanced the proposed workaround by Timo so that the quirk only gets
executed if $HOME is really on a NFS share. Tested it successfully on an
old karmic machine and the current lucid workstations. Just see the
attachment.
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/435719
Title:
gvfs-fuse fails to start on NFS mounted homes
To manage notifications about this bug go to:
** Changed in: gvfs
Importance: Unknown = Medium
--
gvfs-fuse fails to start on NFS mounted homes
https://bugs.launchpad.net/bugs/435719
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
Not exactly helpful for the bug report, but a hint at Erik: I have found quite
a few traps in Ubuntu Software where it is assumed that the root user has
access to the user's home directory, which is not the case in such an
environment. Examples include usb-creator (fixed by now), pam_mount and
a simpler/cleaner (?) way would be to add a script in
/etc/X11/Xsession.d/, those are run as the user so no sudo'ing is
necessary (and I used /tmp, for keeping the namespace cleaner). This is
what we have now:
# create users gvfs mountpoint in /tmp
[ ! -d /tmp/.gvfs-$USER ] mkdir -m 0700
** Changed in: gvfs
Status: Unknown = New
--
gvfs-fuse fails to start on NFS mounted homes
https://bugs.launchpad.net/bugs/435719
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
I also have found this behavior to be a problem for our soon to be 60
workstation 200 user LDAP/NFS environment. We are running Ubuntu
10.04/amd64, autofs mounted NFS with rootsquashing on.
My workaround is: In /etc/gdm/PreSession/Default add the following
before the /sbin/initctl ... line:
#
Modify the second to last line of the above code to be:
sudo -u $USER rmdir ~/.gvfs || sudo -u $USER rm ~/.gvfs
--
gvfs-fuse fails to start on NFS mounted homes
https://bugs.launchpad.net/bugs/435719
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
Thank you for your bug report. The issue is an upstream one and it would
be nice if somebody having it could send the bug the to the people
writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)
** Changed in: gvfs (Ubuntu)
Importance: Undecided = Low
** Changed in: gvfs (Ubuntu)
I followed your link and posted the bug upstream here:
https://bugzilla.gnome.org/show_bug.cgi?id=596176
** Bug watch added: GNOME Bug Tracker #596176
http://bugzilla.gnome.org/show_bug.cgi?id=596176
--
gvfs-fuse fails to start on NFS mounted homes
https://bugs.launchpad.net/bugs/435719
You
Thank you for sending the bug to GNOME
** Changed in: gvfs (Ubuntu)
Status: New = Triaged
** Also affects: gvfs via
http://bugzilla.gnome.org/show_bug.cgi?id=596176
Importance: Unknown
Status: Unknown
--
gvfs-fuse fails to start on NFS mounted homes
17 matches
Mail list logo
