SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Set user umask to 0002 in either /etc/bashrc or ~/.bashrc. 2. Open dolphin or konqueror and create a directory in any local or remote filesystem 3. Note that prems are set to drwxr-sr-x OBSERVED RESULT Dolphin ignores umask set to 002 I first discoverd it when a user complained she coud not access a file I created on an NFS4 share. I don't see this issue if I use fish:// to access any directory, local or remote. We are on fully updated fedora 34 and 35 systems, and this has been a problem for quite awhile, through many Fedora updates, possibly as far back as fedora 18 (arbitrary number). Until now I've usually just run chmod -R g+w on the share on the file server, then went about my business. I have put it off too long and so did a bit of investigation. This happens on both Konqueror and Dolphin. It never happens in Konsole. Meaning that if I open Konsole and cd to /fs1/work (the nfs share), and create a file or directory, the permissions are set to 664 and 2775 (SGID is set for all directories) as expected with a umask of 002 for all users. Note that the umask on both servers and clients are set to 002. So only Dolphin and Konqueror ignore the umask=0002 setting, and only when not accessing a file system via fish. EXPECTED RESULT drwxrwsr-x permissions when creating a directory and rwxrwxr-x when creating a file. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Linux/KDE Plasma (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Fedora 34 and other versions of Fedora
This Bug hits also, if the umask was set in global Xsession, or xprofile. Testet on current Arch Linux. This bug seems to be critc to us, beacuse the company shares it's documents classical using NFS. Not all employees are able to set the right permissions during the work. So this bug makes a lot of trouble.
I fixed this issue by adding ",,,,umask=002" to users in /etc/pasawd. Like so: jdoe:x:1001:1001:jon doe,,,,umask=0002:/home/jdoe:/bin/bash Thanks to response on the kde@lists.fedoraproject.org list server.