Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-1568.html
Description of problem: Version-Release number of selected component (if applicable): gdm-2.30.4-63.el6.x86_64 gdm-libs-2.30.4-63.el6.x86_64 plymouth-0.8.3-27.el6_5.1.x86_64 plymouth-core-libs-0.8.3-27.el6_5.1.x86_64 plymouth-gdm-hooks-0.8.3-27.el6_5.1.x86_64 plymouth-graphics-libs-0.8.3-27.el6_5.1.x86_64 plymouth-plugin-label-0.8.3-27.el6_5.1.x86_64 plymouth-plugin-two-step-0.8.3-27.el6_5.1.x86_64 plymouth-scripts-0.8.3-27.el6_5.1.x86_64 plymouth-system-theme-0.8.3-27.el6_5.1.noarch plymouth-theme-rings-0.8.3-27.el6_5.1.noarch plymouth-utils-0.8.3-27.el6_5.1.x86_64 selinux-policy-3.7.19-250.el6.noarch selinux-policy-mls-3.7.19-250.el6.noarch selinux-policy-targeted-3.7.19-250.el6.noarch How reproducible: everytime GDM is restarted (after logout, after unsuccessful login) Steps to Reproduce: 1. get a RHEL-6.6 machine with active targeted policy 2. log in as common user via GDM (does not matter if the login attempt was successful) 3. search for AVCs Actual results: ---- type=PATH msg=audit(08/18/2014 18:05:23.203:421) : item=0 name=/var/spool/plymouth/boot.log inode=32 dev=fc:03 mode=file,644 ouid=root ogid=root rdev=00:00 obj=system_u:object_r:plymouthd_spool_t:s0 nametype=NORMAL type=CWD msg=audit(08/18/2014 18:05:23.203:421) : cwd=/var/gdm type=SYSCALL msg=audit(08/18/2014 18:05:23.203:421) : arch=x86_64 syscall=stat success=no exit=-13(Permission denied) a0=0x402ab8 a1=0x7fff97e6f8e0 a2=0x7fff97e6f8e0 a3=0x7fff97e6f660 items=1 ppid=23808 pid=23833 auid=unset uid=gdm gid=gdm euid=gdm suid=gdm fsuid=gdm egid=gdm sgid=gdm fsgid=gdm tty=(none) ses=unset comm=plymouth-log-vi exe=/usr/bin/plymouth-log-viewer subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 key=(null) type=AVC msg=audit(08/18/2014 18:05:23.203:421) : avc: denied { getattr } for pid=23833 comm=plymouth-log-vi path=/var/spool/plymouth/boot.log dev=vda3 ino=32 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:plymouthd_spool_t:s0 tclass=file ---- Expected results: * no AVCs