[dolphin] [Bug 483313] New: Dolphin not allowing creation of files in NFS share
Ben
bugzilla_noreply at kde.org
Tue Mar 12 05:05:15 GMT 2024
https://bugs.kde.org/show_bug.cgi?id=483313
Bug ID: 483313
Summary: Dolphin not allowing creation of files in NFS share
Classification: Applications
Product: dolphin
Version: 24.02.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: dolphin-bugs-null at kde.org
Reporter: ben-public at bensuniverse.com
CC: kfm-devel at kde.org
Target Milestone: ---
SUMMARY
I have an NFS share in /etc/fstab that has the 'user' option to allow non-root
mounting. Before Plasma 6.0, I had full edit access in these mounted shares,
as I have the share configured in TrueNAS to map user and group to 'root,'
allowing anyone who mounts to have full permissions. However, something has
changed with the update to Plasma 6.0, and Dolphin is not giving me the option
to create folders, files, copy/paste, etc. However, if I open split view and
drag files into the folder, it will throw an error but then successfully copy
the files, proving that this is not a permissions issue.
I suspect this problem has something to do with the way Dolphin checks if a
user should have permission in a share. In another of my shares, all the files
are owned by my local user, and I still have edit access. The problem only
occurs in shares owned by root.
STEPS TO REPRODUCE
1. Create NFS share with mapall user and mapall group to 'root'
2. Mount NFS share as local (non-root) user
3. If folders contained inside the share are created server-side (owned by
root), local user will not have edit permissions
OBSERVED RESULT
I am not able to edit in these types of shares.
EXPECTED RESULT
I should have full edit access since I should have root permissions from the
perspective of the server.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux 6.7.9-arch1-1
(available in About System)
KDE Plasma Version: 6.0.1
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list