oops, ignore this.
** Also affects: udev-extras (Ubuntu)
Importance: Undecided
Status: New
** Changed in: udev-extras (Ubuntu)
Status: New = Invalid
--
fusermount: failed to open /dev/fuse: Permission denied
https://bugs.launchpad.net/bugs/114212
You received this bug
The problem reappeared in jaunty.
Although fuse.conf has correct permissions, it still cannot be read:
$ python /usr/share/doc/python-fuse/examples/hello.py -s -f -o allow_other ~/tmp
fusermount: failed to open /etc/fuse.conf: Permission denied
fusermount: option allow_other only allowed if
This was fixed in intrepid:
fuse (2.7.3-4ubuntu2) intrepid; urgency=low
* debian/fuse-utils.postinst: Install /bin/fusermount as world executable.
it already bails out correctly if the user does not have access to
/dev/fuse; no reason to control access to it in two different places
After adding the user to the fuse group, I had to reboot. Even
restarting the terminal and then the Xserver was not enough. Why?
Thanks!
--
fusermount: failed to open /dev/fuse: Permission denied
https://bugs.launchpad.net/bugs/114212
You received this bug notification because you are a member
When you add yourself to the fuse group, this takes effect at the *next*
login.
--
fusermount: failed to open /dev/fuse: Permission denied
https://bugs.launchpad.net/bugs/114212
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
@notelopuedesimaginar:
You have a good point about group fuse.
Having to add yourself to group fuse is a security feature (permissions should
only be given to processes which need them).
However, the trendy young things with their shiny shiny eeepcs can't be
expected to understand such things,
first of all. let me say it is buggy.
i had to add my user to the groupe fuse, then make mount point writable by the
fuse groupe !
and you would use -o idmap=user option to translate the id ...
--
fusermount: failed to open /dev/fuse: Permission denied
https://bugs.launchpad.net/bugs/114212
same problem on gusty!
** Changed in: fuse (Ubuntu)
Status: New = Confirmed
--
fusermount: failed to open /dev/fuse: Permission denied
https://bugs.launchpad.net/bugs/114212
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
@gagarine:
I haven't had the problem with gusty beta. Other problems aplenty (not yet
nailed down), but not this one.
I installed the recent 7.10 beta. Booted with some issues.
installed sshfs
added myself to the fuse group
sudo addgroup terry fuse
logged out back in
sshfs was fine. No
Oups... I'm just forgot to logout :/ sorry for the spam.
But why don't put directly the all desktop user in the fuse group? Or
an option in the System - Administration - user and group - user x
- user privilege (graphical)?
--
fusermount: failed to open /dev/fuse: Permission denied
I've had exactly the same problem. I have 3 PCs running 7.04. One of
them has the default installed kernel 2.6.20-15 and is fine, the other 2
have been updated immediately on being installed to 2.6.20-16 and both
have the problem with fusermount. The fix outlined above does work but
it is not
I've just got the same problem on my Feisty install on my laptop. But
I'm pretty certain I didn't have to do the chgrp on other Feisty or Edgy
installs I've done recently, which is strange.
--
fusermount: failed to open /dev/fuse: Permission denied
https://bugs.launchpad.net/bugs/114212
You
I checked the launchpad site for the same symptoms and found them on reports
for Dapper and Edgy. I only started a new bug when I didn't find a report
specifically for Feisty.
I suspect group root is reintroduced, probably from upstream, and then gets
patched shortly after the stable release.
** Changed in: fuse (Ubuntu)
Sourcepackagename: None = fuse
--
fusermount: failed to open /dev/fuse: Permission denied
https://bugs.launchpad.net/bugs/114212
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
14 matches
Mail list logo
