RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Depending on how it is started (via either GUI or command line), GNOME applications such as nautilus and gedit assign a different umask to files and directories created via them. If started via command line, these applications follow the configured umask settings of a system for new files/directories. If started from GUI, this configuration is ignored.

Version-Release number of selected component (if applicable):
nautilus-40.2-9.el9_1.x86_64
gnome-desktop3-40.4-1.el9.x86_64

How reproducible:
If started via the GUI, issue appears to be consistent. Behavior does not occur if application is started via command line.

Steps to Reproduce:
1. In two tests, start a instance of gedit via GUI and a instance via commandline.
2. Create and save a unique test file in each.
3. Check umask of each file.

Actual results:
Applications started via GUI assign different umask to new files/directories than what is configured.

Expected results:
Applications started via GUI assign correct configured umask value.

NOTE: This looks to be a regression of the behavior that was resolved in listing 1778579. As such, I have set the product as the same as this bug. Please change if necessary.

See also https://bugzilla.redhat.com/show_bug.cgi?id=2125184. How the umask is configured? The umask cmd doesn't change that system-wide, just for the concrete terminal session. I suppose that this is perhaps needed here: https://github.com/systemd/systemd/pull/15318.

GNOME starts GUI applications as systemd user services and it seems that systemd --user manager doesn't respect the setting from /etc/login.defs. The problem is that pam_umask.so module is not invoked when starting --user manager. Adding following line to /etc/pam.d/systemd-user config file should fix the issue,

session  optional   pam_umask.so silent

Hello!

Customer wants to know if this issue will be solved in later releases of RHEL or through any other means. As they state that the deployments of RHEL on other machines is on hold currently for this issue.

Hello, We are planning to include the fix in the upcoming RHEL 9.3.0.

fix merged to github main branch -> https://github.com/redhat-plumbers/systemd-rhel9/pull/178

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 (systemd 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/RHBA-2023:6640