Summary: | partitionmanager does not support ntfs3 | ||
---|---|---|---|
Product: | [Applications] partitionmanager | Reporter: | Firestar-Reimu <1900011604> |
Component: | general | Assignee: | Andrius Štikonas <andrius> |
Status: | REPORTED --- | ||
Severity: | normal | ||
Priority: | NOR | ||
Version First Reported In: | 22.08.1 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Firestar-Reimu
2022-10-11 03:30:10 UTC
And I have set this: ``` cat /etc/udisks2/mount_options.conf [defaults] ntfs_defaults=uid=$UID,gid=$GID ``` but still the bug exists. What's the error if you run mount command manually? Partition Manager seems to be running mount --verbose /dev/nvme0n1p3 /home/xxx/C which looks to me like a correct command. https://wiki.archlinux.org/title/NTFS The correct mount should be: ``` # mount -t ntfs3 /dev/nvme0n1p3 /home/xxx/C ``` if there is a mounting bug: https://bugs.kde.org/show_bug.cgi?id=445468 If you have udisks2 2.9.4+, as a temporary fix you can create the file /etc/udisks2/mount_options.conf with the following contents: [defaults] ntfs_defaults=uid=$UID,gid=$GID and you'll be set. Argh, this is a mess on the ntfs side... Partition Manager was indeed relying on mount command to be smart enough to pick file system type. One could add -t ntfs3 but then that would break support for people who have older kernels. Though maybe 5.15 is getting old enough to be in most places. |