Package: fuse3
Version: 3.14.0-10
Severity: normal
Dear Maintainer,
Not sure if this a bug in the fuse3 package or in the mount package.
The problem is that mount passes the arguments of mount.fuse3 in the wrong
order.
Found by strace that this is what is passed:
/sbin/mount.fuse3 -o rw,users,nosuid,nodev,exec sshfs#user@machine:space/
/home/user/mnt/space
This is what mount.fuse3 expects:
$ /sbin/mount.fuse3 --help
usage: /sbin/mount.fuse3 type#[source] destination [-t type] [-o
opt[,opts...]]
In the command line if I move the -o options at the end the mount works.
* What led up to the situation?
I have an entry in my fstab for a sshfs mount and I was trying to mount
* What exactly did you do (or not do) that was effective (or
ineffective)?
I gave the following command which was for several years before
mount ~/mnt/space
* What was the outcome of this action?
It said:
/bin/sh: 1: -o: not found
* What outcome did you expect instead?
I was expecting to actually mount the specified remote folder.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.12.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fuse3 depends on:
ii adduser 3.137
ii libc6 2.40-5
ii libfuse3-3 3.14.0-10
ii mount 2.40.3-1
ii sed 4.9-2
fuse3 recommends no packages.
fuse3 suggests no packages.
-- Configuration Files:
/etc/fuse.conf [file not found]
-- no debconf information
--
Vassilis Virvilis
