|
Bugzilla – Full Text Bug Listing |
| Summary: | fuse module not loaded on boot | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Stanislav Brabec <sbrabec> |
| Component: | Basesystem | Assignee: | Forgotten User sLJ7K2dvxj <forgotten_sLJ7K2dvxj> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | forgotten_sLJ7K2dvxj |
| Version: | 13.1 Milestone 4 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Stanislav Brabec
2013-08-20 16:26:37 UTC
FUSE doesn't seem to be loaded by default on 12.3 either. My headless 12.3 systems don't have it loaded. I suspect it may be autoloaded by GNOME for gvfs, but I don't think it would be loaded automatically otherwise. Confirming that even on 12.3 fuse is not autoloaded. Trying to use encfs command as non-root fails before login to GNOME. But maybe the user-level fuse autoload could be ported (from GVFS) to other applications, so one could use encfs and other fuse based utilities without root privileges. It *should* autoload for all cases. The fuse device is set up by udev or whatever and autoloading the fuse module is done when the device is accessed. Do you have /dev/fuse after boot? Yes, I have. But in 12.3 it was world writable, in Factory it is root-only. I see this after login to GNOME: openSUSE 12.3: utx:~ # ls -al /dev/fuse crw-rw-rw- 1 root root 10, 229 Sep 5 13:18 /dev/fuse utx:~ # lsmod | grep fuse fuse 87139 3 utx:~ # openSUSE Factory: oct:~ # ls -al /dev/fuse crw------- 1 root root 10, 229 Sep 5 15:26 /dev/fuse oct:~ # lsmod | grep fuse oct:~ # Okay, so this is a dup of 835813. I have no idea about this one. It certainly doesn't look like anything in the fuse package. Who would know why permissions on a device changed in Factory? *** This bug has been marked as a duplicate of bug 835813 *** |