NB that the group fuse isn't created until you install the "right"
package
$ sudo apt-get install sshfs # possibly just installing fuse-utils would do the
trick.
--i.e. Installing fuse2 and libfuse-dev apparently is enough to create
/dev/fuse but not create its group (?)
Even after that, you
Appears to work in Gutsy now.
I didn't check if a fuse group existed before adding my user to it, but
I did have to manually put my user in the group.
In addition, the permissions on /dev/fuse did not take effect until I
rebooted my computer,
--
dapper: /dev/fuse not owned by group set in packa
lets try that then :)
fuse (2.6.5-1ubuntu2) gutsy; urgency=low
.
* drop postinst code for MAKEDEV and udevcontrol reload_rules we dont need
either in ubuntu and it most likely fixes the /dev/fuse ownership problems
from launchpad bug 5105.
couls someone test this on gutsy i assume
In Feisty, /dev/fuse is initially owned by root/root. After doing sudo
modprobe -r fuse ; sudo modprobe fuse, the owner changes to root/fuse.
--
dapper: /dev/fuse not owned by group set in package config
https://bugs.launchpad.net/bugs/5105
You received this bug notification because you are a mem
Maybe Philip's case was like mine. I did a fresh install of Feisty,
keeping only my home directory from Edgy, last week, and have kept it
updated. Today I added the sshfs package, which also added a fuse
related package. When I first ran sshfs, I deduced from the error
message that I needed to be p
did you use feisty from any herd CD to install ? there was a bug in an
early release of this package where the wrong (debians udev file) file
was installed as /etc/udev/rules.d/40-fuse.rules. the correctd package
in feisty (2.6.3-1ubuntu2) should supply this file corerected with a
sequence number o
I can confirm this bug on Feisty. Luckily it seems I don't have to make
this change every boot. Regardless, it causes Fuse to not simply "just
work" out of the box.
--
dapper: /dev/fuse not owned by group set in package config
https://bugs.launchpad.net/bugs/5105
You received this bug notificatio
I just ran into the /dev/fuse permissions problem on Edgy (upgraded from
Dapper, upgraded from Breezy I think).
The problem was a mistake in the file /etc/udev/rules.d/40-fuse.rules.
It is supposed to contain:
KERNEL=="fuse", NAME="%k", MODE="0666"
but it actually contains
KERNEL="fuse", NAME="
