Dear all,
Fuse seems to have stopped working on my computer. I’m not sure when this happened but its must be due to an update.
System Opensuse 13.1
3.11.10-17-desktop #1 SMP PREEMPT Mon Jun 16 15:28:13 UTC 2014 (fba7c1f) x86_64 x86_64 x86_64 GNU/Linux
Error when trying to mount encrypted directory:
encfs /Path/Encrypted /Path/Decrypted
EncFS Password:
fuse: failed to open /dev/fuse: Permission denied
fuse failed. Common problems:
- fuse kernel module not installed (modprobe fuse)
- invalid options -- see usage message
I have tried modprobe fuse. No error, but it doesn’t help. My system has no fuse group to add my user too, should it?
Ideas anyone?
Cheers,
Phil
On Sun, 06 Jul 2014 14:16:02 +0000, prgarnett wrote:
> I have tried modprobe fuse. No error, but it doesn’t help.
When you try to load the fuse module, what shows up in the output of
dmesg?
Does it show in the output for lsmod?
Jim
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Output of dmesg | grep fuse
# dmesg | grep fuse
3.619204] fuse init (API version 7.22)
output of lsmod | grep fuse
lsmod | grep fuse
fuse 95850 1
So it appears to be running.
I just tried it as root and it worked. So it looks like a permissions problem.
I have another computer, pretty much the same set up, this doesn’t happen. So I am trying to figure out if there is a difference somewhere.
This seems to be a permissions issue indeed:
prgarnett:
Error when trying to mount encrypted directory:
encfs /Path/Encrypted /Path/Decrypted
EncFS Password:
fuse: failed to open /dev/fuse: Permission denied
fuse failed. Common problems:
- fuse kernel module not installed (modprobe fuse)
- invalid options -- see usage message
Actually this shouldn’t be possible, see the permissions for /dev/fuse on my system:
:~> ls -l /dev/fuse
crw-rw-rw- 1 root root 10, 229 7. Jul 08:29 /dev/fuse
So “rw” for all users.
What are yours?
AFAICS /dev/fuse is created with those permissions via udev rules.
/usr/lib/udev/rules.d/50-udev-default.rules should contain the following line:
KERNEL=="fuse", MODE="0666", OPTIONS+="static_node=fuse"
Do you have that there?
Maybe you have some custom rule in /etc/udev/rules.d that overrides this?
ls /etc/udev/rules.d/
grep fuse /etc/udev/rules.d/*
On Mon, 07 Jul 2014 11:36:01 +0000, prgarnett wrote:
> I have another computer, pretty much the same set up, this doesn’t
> happen. So I am trying to figure out if there is a difference somewhere.
Sounds like a good approach. I use encfs myself as well on 13.1, and I
don’t see any issues with it, so your supposition and approach is what I
would also be inclined to use.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
I want to add, that a bug was reported against Factory today, that sounds quite similar to your issue:
https://bugzilla.novell.com/show_bug.cgi?id=886032
So check that you don’t have added the Factory repo to your system.
If in doubt, please post your repo list:
zypper lr -d
Hi folks,
I’m back at the miss behaving computer today.
So the permissions are wrong.
# ls -l /dev/fuse
crw------- 1 root root 10, 229 Jul 3 18:51 /dev/fuse
This looks ok
# cat /usr/lib/udev/rules.d/50-udev-default.rules | grep fuse
KERNEL=="fuse", MODE="0666", OPTIONS+="static_node=fuse"
As does this
# ls /etc/udev/rules.d/
55-libsane.rules 56-sane-backends-autoconfig.rules 70-persistent-net.rules 99-iwlwifi-led.rules
56-hpmud.rules 70-kpartx.rules 71-kpartx-compat.rules
# grep fuse /etc/udev/rules.d/*
#
No factory repros:
# zypper lr -d | grep factory
#
So question is… what has changed the fuse permissions. I will change them back reboot and see if it is wrong again.
Rebooted and something has changed them back…
# ls -l /dev/fuse
crw------- 1 root root 10, 229 Jul 8 09:50 /dev/fuse
Repros are below just in case.
# | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
---+--------------------------------------+-----------------------------------------------------+---------+---------+----------+--------+---------------------------------------------------------------------------------------+--------
1 | Documentation:Tools | Documentation:Tools | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/Documentation:/Tools/openSUSE_13.1/ |
2 | GNOME:Apps | GNOME:Apps | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/GNOME:/Apps/openSUSE_13.1/ |
3 | devel:languages:R:patched | devel:languages:R:patched | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/devel:/languages:/R:/patched/openSUSE_13.1/ |
4 | download.nvidia.com-opensuse | nVidia Graphics Drivers | No | No | 99 | rpm-md | http://download.nvidia.com/opensuse/13.1/ |
5 | download.opensuse.org-Extra | openSUSE BuildService - KDE:Extra | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_13.1/ |
6 | download.opensuse.org-Stable | openSUSE BuildService - LibreOffice | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/LibreOffice:/Stable/openSUSE_13.1/ |
7 | download.opensuse.org-Virtualization | openSUSE BuildService - Virtualization (VirtualBox) | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/Virtualization/openSUSE_13.1/ |
8 | download.opensuse.org-database | openSUSE BuildService - Database | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/server:/database/openSUSE_13.1/ |
9 | download.opensuse.org-mozilla | openSUSE BuildService - Mozilla | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/repositories/mozilla/openSUSE_13.1/ |
10 | ftp.gwdg.de-suse | Packman Repository | Yes | Yes | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_13.1/ |
11 | google-earth | google-earth | Yes | Yes | 99 | rpm-md | http://dl.google.com/linux/earth/rpm/stable/x86_64 |
12 | openSUSE-13.1-1.10 | openSUSE-13.1-1.10 | No | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-TSSTcorp_CDDVDW_SH-224BB_R8WS6GAD103RZ2 |
13 | opensuse-guide.org-repo | libdvdcss repository | Yes | Yes | 99 | rpm-md | http://opensuse-guide.org/repo/13.1/ |
14 | repo-debug | openSUSE-13.1-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/13.1/repo/oss/ |
15 | repo-debug-update | openSUSE-13.1-Update-Debug | No | No | 99 | NONE | http://download.opensuse.org/debug/update/13.1/ |
16 | repo-debug-update-non-oss | openSUSE-13.1-Update-Debug-Non-Oss | No | No | 99 | NONE | http://download.opensuse.org/debug/update/13.1-non-oss/ |
17 | repo-non-oss | openSUSE-13.1-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.1/repo/non-oss/ |
18 | repo-oss | openSUSE-13.1-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.1/repo/oss/ |
19 | repo-source | openSUSE-13.1-Source | No | No | 99 | NONE | http://download.opensuse.org/source/distribution/13.1/repo/oss/ |
20 | repo-update | openSUSE-13.1-Update | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.1/ |
21 | repo-update-non-oss | openSUSE-13.1-Update-Non-Oss | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.1-non-oss/ |
Yes.
This looks ok
cat /usr/lib/udev/rules.d/50-udev-default.rules | grep fuse
KERNEL==“fuse”, MODE=“0666”, OPTIONS+=“static_node=fuse”
Yes.
As does this
# ls /etc/udev/rules.d/
55-libsane.rules 56-sane-backends-autoconfig.rules 70-persistent-net.rules 99-iwlwifi-led.rules
56-hpmud.rules 70-kpartx.rules 71-kpartx-compat.rules
# grep fuse /etc/udev/rules.d/*
#
[/QUOTE]
Yes.
No factory repros:
zypper lr -d | grep factory
And what about “Factory”?
grep is case-sensitive by default.
But your repo list shows that you don’t have it. This was just an idea because I saw that bug report.
So question is… what has changed the fuse permissions. I will change them back reboot and see if it is wrong again.
/dev doesn’t really exist on your hard disk.
The device files get created dynamically, so changing the permissions will not persist a reboot.
Hm. Maybe something is wrong with your initrd? Could be that something in there creates the device node already with the wrong permissions.
Try to re-create it with “sudo /sbin/mkinitrd”.
Other than that I have no idea at the moment, why those permissions are wrong.
PS: FS#36259 : [systemd] 206 sets incorrect permissions on static nodes would suggest a wrong tmpfiles configuration.
What do you have in /etc/tmpfiles.d/ and /etc/tmpdirs.d/ ?
Maybe something wrong in there?
Nothing in those dirs. I will try remaking initrd today. See what happens.
Rebuilding initrd didn’t help either. Something I must have either installed or changed must be the cause of this, I can’t think what that would be.
Sorry, I have no idea either.
You could check whether something messes with /dev/fuse in /usr/lib/tmpdirs.d maybe.
But as a workaround you could set the permissions via a file something.conf in /etc/tmpfiles.d/.
Something like this should work I suppose:
c /dev/fuse 666 root root - 10:229