GNOME Bugzilla – Bug 768247
Starting the system makes group ownership on /var/log/gdm not match what is expected in the RPM database
Last modified: 2018-05-24 11:24:26 UTC
When starting up the RHEL 6.8 OS the /usr/sbin/gdm-binary calls chown and changes the group owner of /var/log/gdm to gdm. When you check against the expected group owner of /var/log/gdm in the RPM database the check fails since root is the expected group owner according to the RPM database. 1. Boot up the operating system 2. Run rpm -Va | grep '^......G' 3. /var/log/gdm will appear as not matching the expected group in the RPM database. 4. Run rpm -qf /var/log/gdm 5. rpm --setugids [output from step 4] 6. Restart operating system 7. Run rpm -Va | grep '^......G' 8. /var/log/gdm will appear as not matching the expected group in the RPM database. The actual result is that gdm is again the group owner after reboot. The expected results are that the group should be root after reboot on the /var/log/gdm directory after running the command to reset to the group owner. Build Wed 15 Oct 2014 05:20:09 PM ED on RHEL 6.8
Has there been any work done, or was this bug even looked at?
So in upstream versions of gdm /var/log/gdm is less important, since log messages go to the journal. We should probably just drop the directory entirely.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/262.