rmfuse
rmfuse copied to clipboard
rmfuse does not mount after mounting as sudo
Dear community,
I have applied rmfuse to one of my folders named 'remarkable' as admin with the command
sudo rmfuse ~/remarkable.
With this I can mount but not access the files via Nautilus. Therefore I would like to use rmfuse without sudo. Unfortunately my rmfuse does not mount anymore after having mounted once using sudo.
I have installed rmfuse
from the AUR, in the current version with python-pyfuse3
. As operating system I have Archlinux.
When I run rmfuse -vvv remarkable
the following output comes:
DEBUG:pyfuse3:Initializing pyfuse3
DEBUG:pyfuse3:Calling fuse_session_new
FUSE library version: 3.10.5
DEBUG:pyfuse3:Calling fuse_session_mount
INFO:rmfuse.fuse:Mounting on remarkable
DEBUG:pyfuse3:pyfuse-02: No tasks waiting, starting another worker (now 2 total).
unique: 2, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.34
flags=0x33fffffb
max_readahead=0x00020000
INIT: 7.31
flags=0x0040b039
max_readahead=0x00020000
max_write=0x00100000
max_background=0
congestion_threshold=0
time_gran=1
unique: 2, success, outsize: 80
unique: 4, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 16273
DEBUG:pyfuse3:pyfuse-03: No tasks waiting, starting another worker (now 3 total).
unique: 6, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 1509
DEBUG:rmcl.api:Renewing user token
DEBUG:pyfuse3:pyfuse-04: No tasks waiting, starting another worker (now 4 total).
unique: 8, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 720
DEBUG:pyfuse3:pyfuse-05: No tasks waiting, starting another worker (now 5 total).
unique: 10, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 16274
DEBUG:pyfuse3:pyfuse-06: No tasks waiting, starting another worker (now 6 total).
unique: 12, opcode: GETATTR (3), nodeid: 1, insize: 56, pid: 16275
DEBUG:rmcl.api:Renewing user token
DEBUG:pyfuse3:Calling fuse_session_unmount
DEBUG:pyfuse3:Calling fuse_session_destroy
I would appreciate any suggestions.
With best regards
Are you sure your user has write access to ~/remarkable
?
Are you sure your user has write access to
~/remarkable
?
Yes, I am.