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:
gdm creates /var/run/gdm/ directory within tmpfs. When the system reboots, this directory is removed and re-created. The second time it is created it is affected by umask which doesn't match what the rpm set for the directory permission.

This matters for openscap profiles, such as STIG (which we ship), that look into "rpm -Va" output and will FAIL due to incorrect mode. 

   # rpm --setperms gdm
   # rpm -V gdm
       <No results>
   # reboot
   # rpm -V gdm
       .M.......    /var/run/gdm


How reproducible:
 Easily

Steps to Reproduce:
1. Install gdm
2. Restart the system
3. rpm -V gdm

Actual results:
 # rpm -V gdm
    .M.......    /var/run/gdm

Expected results:
 # rpm -V gdm  #Nothing returned

Additional info:
   This is the same scenario as https://bugzilla.redhat.com/show_bug.cgi?id=1462802

   I would worry this may continue to happen with every package that sets files in /var/run with permissions that do not match default umask

** Correction **

Actual results:
 # rpm -V gdm
    .M....G..    /var/log/gdm

*** This bug has been marked as a duplicate of bug 1275532 ***