Hide Forgot
Description of problem: ABRT test, please disregard. SELinux is preventing / ***** Plugin catchall (100. confidence) suggests *************************** If you believe that systemd-logind should be allowed setattr access on the sr0 blk_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 systemd-logind /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:systemd_logind_t:s0 Target Context system_u:object_r:virt_content_t:s0 Target Objects sr0 [ blk_file ] Source systemd-logind Source Path /lib/systemd/systemd-logind Port <Unknown> Host (removed) Source RPM Packages systemd-37-3.fc16 Target RPM Packages Policy RPM selinux-policy-3.10.0-64.fc16 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.1.4-1.fc16.x86_64 #1 SMP Tue Nov 29 11:37:53 UTC 2011 x86_64 x86_64 Alert Count 2 First Seen Sat 10 Dec 2011 07:55:31 PM CET Last Seen Sat 10 Dec 2011 11:18:05 PM CET Local ID 14bed772-5cbc-4d21-85ac-4d0e9f2a7eb9 Raw Audit Messages type=AVC msg=audit(1323555485.669:711): avc: denied { setattr } for pid=1119 comm="systemd-logind" name="sr0" dev=devtmpfs ino=8018 scontext=system_u:system_r:systemd_logind_t:s0 tcontext=system_u:object_r:virt_content_t:s0 tclass=blk_file type=SYSCALL msg=audit(1323555485.669:711): arch=x86_64 syscall=setxattr success=yes exit=0 a0=166acb0 a1=7fe0bcb35d2b a2=166da10 a3=24 items=0 ppid=1 pid=1119 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=systemd-logind exe=/lib/systemd/systemd-logind subj=system_u:system_r:systemd_logind_t:s0 key=(null) Hash: systemd-logind,systemd_logind_t,virt_content_t,blk_file,setattr audit2allow #============= systemd_logind_t ============== allow systemd_logind_t virt_content_t:blk_file setattr; audit2allow -R #============= systemd_logind_t ============== allow systemd_logind_t virt_content_t:blk_file setattr; Additional info: executable: /usr/bin/python hashmarkername: setroubleshoot kernel: 3.1.5-1.fc16.x86_64
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.