This is working fine in Feisty (reboot needed for permissions to take
root), so I'm closing.
** Changed in: fuse (Ubuntu)
Status: Confirmed = Fix Released
--
fusermount requires fuse module kernel to be loaded, isn't done automagically
https://launchpad.net/bugs/1860
--
ubuntu-bugs
I'm using edgy as well and had the same problem.
Rules existed. I was in fuse group and fuse was the group in /dev/fuse.
Still I got permission denied error.
Anyway, I had just installed ssftp and obligatory packages, so I decided to use
the magical trick;
reboot. Now everything works
do you have the udev rules file in place ?
(ls /etc/udev/rules.d/|grep fuse )
--
fusermount requires fuse module kernel to be loaded, isn't done automagically
https://launchpad.net/bugs/1860
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
// do you have the udev rules file in place ?
// (ls /etc/udev/rules.d/|grep fuse )
The output from that command gets me this:
45-fuse.rules
--
fusermount requires fuse module kernel to be loaded, isn't done automagically
https://launchpad.net/bugs/1860
--
ubuntu-bugs mailing list
In both cases (Dapper and Edgy) the fuse module got loaded
automatically (I did not perform any modprobe) but Edgy got the wrong
permissions to /dev/fuse (Dapper got it right).
I am also on Edgy, and I experience the exact same issue: the fuse module was
loaded automatically, but even users in
Have just installed sshfs (which requires fuse-utils) on a Dapper host
and on an Edgy laptop, so I could mount a directory from host to the
laptop through sshfs.
Tried a few times and it didn't work because I needed to add myself to
fuse group, so I did that. Then, tried again and fusermount said
I thought I unsubscribed from this bug. I'm no longer running Ubuntu,
I've gone back to Debian.
--
fusermount requires fuse module kernel to be loaded, isn't done automagically
https://launchpad.net/bugs/1860
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
