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 part of the fuse group. I added myself, then logged out and back in. I still got the error listed at the top. Certain that I had found a bug, I googled and got this page. After reading through all the comments, I checked the udev rules, and they were right. Then I looked again at the file permissions again on /dev/fuse, and noticed the time and date stamp were from last time I rebooted. Apparently the fuse module was already getting loaded before the installation of fuse-utils, but with root:root ownership. I did "sudo modprobe -r fuse" followed by "sudo modprobe fuse" and everything worked. I only relate this in case the same thing happens to someone else.
-- 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 member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
