Hide Forgot
Description of problem: Nautilus does not respect umask settings. Version-Release number of selected component (if applicable): nautilus-3.26.3.1-7.el7.x86_64 How reproducible: Not always reproducible, is reproducible on few systems and not on few. Steps to Reproduce: === $ umask 0002 $ touch a $ ls -l total 1 -rw-rw-r--. 1 user user 0 Sep 27 10:26 a $ nautilus <------ created a empty file here in same directory and nautilus started from same cli. $ ls -l total 11 -rw-rw-r--. 1 user user 0 Sep 27 10:26 a -rw-r--r--. 1 user user 8295 Apr 30 2018 New Document.odt === Actual results: Permissions of both the files generated from cli and from nautilus are not same. Expected results: Permissions of both the files generated from cli and from nautilus should be same, as set by umask setting. Additional info: The reason why it seemingly works in some cases is maybe because the new files are just copies of ~/Templates files and it is possible that those template files have different permissions on different systems for some reason.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: GNOME security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:4451