On Kubuntu 18.04 beta 1 release.
My .profile define : UMASK=002
In a terminal, a new file is created as wanted : -rw-rw-r--
Using dolphin, create a new file (txt for example), my file is -rw-r--r--
I also try to change /etc/profile. Dolphin does not use the UMASK.
Please, be helpfull, english is not my native langage and may be the package is not the correct one.
Dolphin informations are :
KDE frameworks 5.44.0
Re-assigning to KIO where the KNewFileMenu lives
It doesn't seem to be a KDE bug :
I am having the same issue.
On Xubuntu 18.04, i have installed Dolphin. I tried putting umask 077 in /etc/profile and in ~/.bashrc, with folders it correctly creates them with permissons 700, but creating files it gives them permissions 644 instead of 600 like it should.
I tried with Krusader and with Thunar, none of these file managers have these issues.
Please reproduce with Xubuntu and dolphin and see what i mean.
I can also reprat this issue. 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). Unti 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.
I didn't see that this bug was for kubuntu. I will report if for Fedora.