https://bugs.kde.org/show_bug.cgi?id=451408
--- Comment #10 from Méven Car <meve...@gmail.com> --- > /dev/sda3 on /mnt/DADOS type fuseblk > (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096) > /dev/sdc1 on /commonDisks/F type fuseblk > (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) > /dev/sdb1 on /commonDisks/G type fuseblk > (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) Indeed that's because your mounts are actually using fuseblk. The bug is due to fact fuse mounts are assimilated to nfs filesystem, here wrongfully in kcoreaddons: https://invent.kde.org/frameworks/kcoreaddons/-/blob/master/src/lib/io/kfilesystemtype.cpp#L129 The way to fix it, is not clear to me, we need to determine "real" filesystem for the fuse block but I don't know exactly how to do it. Probably using fuse API statfs, http://libfuse.github.io/doxygen/structfuse__operations.html#a4e765e29122e7b6b533dc99849a52655 -- You are receiving this mail because: You are watching all bug changes.
