Hide Forgot
Description of problem: Happened just by testing kmscon in default mode SELinux is preventing kmscon from 'getattr' accesses on the file /proc/meminfo. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that kmscon should be allowed getattr access on the meminfo file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # grep kmscon /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:kmscon_t:s0 Target Context system_u:object_r:proc_t:s0 Target Objects /proc/meminfo [ file ] Source kmscon Source Path kmscon Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-105.6.fc21.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.19.1-201.fc21.x86_64 #1 SMP Wed Mar 18 04:29:24 UTC 2015 x86_64 x86_64 Alert Count 1 First Seen 2015-03-28 23:18:10 PDT Last Seen 2015-03-28 23:18:10 PDT Local ID 802cace7-bcbc-4237-8785-54af1a036b91 Raw Audit Messages type=AVC msg=audit(1427609890.426:1396): avc: denied { getattr } for pid=9950 comm="kmscon" path="/proc/meminfo" dev="proc" ino=4026532000 scontext=system_u:system_r:kmscon_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=file permissive=1 Hash: kmscon,kmscon_t,proc_t,file,getattr Version-Release number of selected component: selinux-policy-3.13.1-105.6.fc21.noarch Additional info: reporter: libreport-2.3.0 hashmarkername: setroubleshoot kernel: 3.19.1-201.fc21.x86_64 type: libreport
commit 6bf454cdb5b223c78b6befe67bff4832c36fdebc Author: Lukas Vrabec <lvrabec@redhat.com> Date: Mon Mar 30 12:41:09 2015 +0200 Allow kmscon to read system state. BZ (1206871)
selinux-policy-3.13.1-105.11.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/selinux-policy-3.13.1-105.11.fc21
Package selinux-policy-3.13.1-105.11.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.13.1-105.11.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-5478/selinux-policy-3.13.1-105.11.fc21 then log in and leave karma (feedback).
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.