Bug 2210145

Summary:	[spec] [RHEL-9]GNOME applications started via GUI have different umask than ones started via command line
Product:	Red Hat Enterprise Linux 9	Reporter:	Brandon Clark <brclark>
Component:	systemd	Assignee:	Jan Macku <jamacku>
Status:	CLOSED ERRATA	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	9.1	CC:	dtardon, jamacku, mijjapur, oholy, qguo, systemd-maint-list
Target Milestone:	rc	Keywords:	Bugfix, Reproducer, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	systemd-252-16.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-07 08:54:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Brandon Clark 2023-05-25 21:51:26 UTC

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.

Comment 1 Ondrej Holy 2023-05-26 09:31:16 UTC

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.

Comment 2 Michal Sekletar 2023-05-31 17:00:32 UTC

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

Comment 3 Murali Prudhvi Ijjapureddi 2023-06-23 17:26:43 UTC

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.

Comment 4 Jan Macku 2023-06-28 10:38:10 UTC

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

Comment 5 Plumber Bot 2023-07-13 08:59:44 UTC

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

Comment 10 errata-xmlrpc 2023-11-07 08:54:03 UTC

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