Bug 436689 - Dolphin Can't Edit NFS Folders Despite Permissions
Summary: Dolphin Can't Edit NFS Folders Despite Permissions
Status: REPORTED
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: Open/save dialogs (show other bugs)
Version: 5.18.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KIO Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-06 15:27 UTC by afkingz1373
Modified: 2021-05-07 19:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description afkingz1373 2021-05-06 15:27:21 UTC
SUMMARY
Dolphin is unable to create new folders/download-files-to/delete files off a Synology NFS mounted folder, despite the same user being able to, in the console.

STEPS TO REPRODUCE
1. NFS Mount Options in /etc/fstab are:
XXX.XXX.X.XXX:/volume1/XXXXX /XXXX/XXX nfs rsize=8192,wsize=8192,timeo=14,intr
2. Go to folder and try to create new folder, option is grayed out.
3. Try to create a folder in console, it works. But trying to delete it shows the prompt that the folder is "write-protected".

OBSERVED RESULT
Unable to download files to the folder or to do much of anything when using Dolphin.

EXPECTED RESULT
Able to download files to the folder, create new folders, etc.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.8.0-50-generic
OS Type: 64-bit



ADDITIONAL INFORMATION
Able to access the files in the folder and to run them, just unable to edit.
Also Mentioned here:

https://www.reddit.com/r/kde/comments/n55jp9/dolphin_cant_edit_synology_nfs_folders_even_when/

https://www.reddit.com/r/kde/comments/7e1el9/cant_write_to_nfs_share_with_dolphin_but_can_with/

https://www.reddit.com/r/linuxquestions/comments/gttpyz/dolphin_cant_pasterenamecreate_new_directory_in/
Comment 1 Nate Graham 2021-05-07 19:46:01 UTC

*** This bug has been marked as a duplicate of bug 400293 ***