Description of problem: SELinux is preventing /usr/bin/bash from 'getattr' accesses on the file /proc/meminfo. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that bash 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 lsb_release /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:ladvd_t:s0 Target Context system_u:object_r:proc_t:s0 Target Objects /proc/meminfo [ file ] Source lsb_release Source Path /usr/bin/bash Port <Unknown> Host (removed) Source RPM Packages bash-4.2.45-1.fc19.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-74.9.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 3.11.4-201.fc19.x86_64 #1 SMP Thu Oct 10 14:11:18 UTC 2013 x86_64 x86_64 Alert Count 1 First Seen 2013-10-12 17:01:27 BST Last Seen 2013-10-12 17:01:27 BST Local ID d5078121-cd63-4fad-b4fc-1ff1e3b0f328 Raw Audit Messages type=AVC msg=audit(1381593687.672:12): avc: denied { getattr } for pid=525 comm="lsb_release" path="/proc/meminfo" dev="proc" ino=4026532027 scontext=system_u:system_r:ladvd_t:s0 tcontext=system_u:object_r:proc_t:s0 tclass=file type=SYSCALL msg=audit(1381593687.672:12): arch=x86_64 syscall=fstat success=yes exit=0 a0=3 a1=7ffff47c78c0 a2=7ffff47c78c0 a3=0 items=0 ppid=508 pid=525 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=lsb_release exe=/usr/bin/bash subj=system_u:system_r:ladvd_t:s0 key=(null) Hash: lsb_release,ladvd_t,proc_t,file,getattr Additional info: reporter: libreport-2.1.7 hashmarkername: setroubleshoot kernel: 3.11.4-201.fc19.x86_64 type: libreport
ladvd-1.0.4-11.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/ladvd-1.0.4-11.fc20
Package ladvd-1.0.4-11.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ladvd-1.0.4-11.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-19079/ladvd-1.0.4-11.fc20 then log in and leave karma (feedback).
ladvd-1.0.4-11.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
After I upgraded Fedora 19 to 20 and ladvd from 1.0.4-4 to 1.0.4-11, the problem still persists. Also, ladvd-1.0.4-4 to ladvd-1.0.4-11 seems like minor version upgrade so it should be pushed to Fedora 19 repository (maybe as well as the fix for this bug).
This has nothing to do with the shell you use.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.