SUMMARY After upgrading to 18.08.2 I'm getting the same behavior as described in bug 387936 https://bugs.kde.org/show_bug.cgi?id=387936 the root folder of a NFS mount is not writable from Dolphin while I can write to it from the shell Downgrading to 18.08.1 fixes this STEPS TO REPRODUCE 1. Upgrade to 18.08.2 2. Access the root folder of a NFS share your user has RW access to 3. Try to create a folder OBSERVED RESULT Dolphin doesn't give the option to create a folder EXPECTED RESULT Be able to create a folder SOFTWARE VERSIONS (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 dolphin 18.08.2 dolphin-plugins 18.08.2 ADDITIONAL INFORMATION I've first downgraded the kio and kio-extras but that produced no result. Only after downgrading dolphin and dolphin-plugins did it resolve the issue
Moving to kio-extras, the nfs ioslave probably claims the KFileItem is not writable. The bug is probably exposed by https://cgit.kde.org/dolphin.git/commit/?h=Applications/18.08&id=5e8b892a519b8d1fef58a747fafb5846b7fa3492 (It was working in 18.08.1 just by luck, because we were always enabling the create_dir action).
Yep, that makes perfect sense, Elvis.
So is anyone working on this ? Does it make sense to test with 18.12 ?
The issue is still present on version 19.04.1
I can reproduce the issue. However, are you sure that this issue is connected to a KDE component? Testing if the main mounted folder is writable in bash with $ if [ -w `pwd` ]; then echo "WRITABLE"; else echo "NOT WRITABLE"; fi NOT WRITABLE or in Python with $ python3 >>> import os >>> os.access('.', os.W_OK) False indicates that the mounted main folder is not writeable although one can actually write into it. By chance, do you use a Synology device? I do and I found also some other post of Synology users having the same issue. Could be coincidence, though...
*** Bug 429835 has been marked as a duplicate of this bug. ***
In bug 429835 I reported issue with rename of file, which I able to rename in mc but not in Dolphin. And just I would like to add that I also use Synology, which means that my nfs resource is present in Synology server.
Is this actually using the NFS ioslave (via a URL starting "nfs://serverhost/"), or a locally mounted NFS filesystem? If it is the latter then it is handled via the file ioslave in the same way as any other local file, and the appropriate component is either frameworks-kio or dolphin.
(In reply to Jonathan Marten from comment #8) > Is this actually using the NFS ioslave (via a URL starting > "nfs://serverhost/"), or a locally mounted NFS filesystem? If it is the > latter then it is handled via the file ioslave in the same way as any other > local file, and the appropriate component is either frameworks-kio or > dolphin. In my case, so Bug 429835 this was locally mounted NFS filesystem (by "mount -t nfs" command). I open such mounted directory in Dolphin. The issue was that in Dolphin I could not rename file whilst I was able to do it in mc, just because Dolphin says 'no write permission'.
Thanks for the confirmation. If it refers to shell access then it must be an NFS mount, not the ioslave. *** This bug has been marked as a duplicate of bug 387936 ***
*** Bug 436689 has been marked as a duplicate of this bug. ***