Description of problem: "alsactl store" creates /etc/asound.state with the incorrect selinux security context. Version-Release number of selected component (if applicable): alsa-utils-1.0.23-3.fc14.x86_64 How reproducible: Always. Steps to Reproduce: 1. # rm /etc/asound.state 2. # alsactl store Actual results: # ls -Z /etc/asound.* -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/asound.conf -rw-r--r--. root root unconfined_u:object_r:etc_t:s0 /etc/asound.state Expected results: # fixfiles check /etc/asound.* /sbin/restorecon reset /etc/asound.state context unconfined_u:object_r:etc_t:s0->system_u:object_r:alsa_etc_rw_t:s0 Additional info:
When selinux is in enforcing mode, this bug prevents the alsamixer settings from being saved. Setting selinux to permissive mode allows the alsamixer settings to be saved and restored. Also, I can see an avc message about alsactl on the console during reboot, but I cannot find the message in any log file. I'm fairly sure this message was being logged when I encountered this problem in F13. NB: I have removed pulseaudio.
Confirmed that the problem also exists in Rawhide (alsa-utils-1.0.23-3.fc14), F13 (alsa-utils-1.0.23-3.fc13), and F12 (alsa-utils-1.0.23-3.fc12). I still have pulseaudio installed.
(In reply to comment #2) > Confirmed that the problem also exists in Rawhide (alsa-utils-1.0.23-3.fc14), > F13 (alsa-utils-1.0.23-3.fc13), and F12 (alsa-utils-1.0.23-3.fc12). I still > have pulseaudio installed. Thanks for checking these. Are you able to find any avc messages concerning alsactl in any log file?
No, but as far as I can tell, initscripts only attempts to save mixer settings during shutdown, not restore them at boot. I haven't manually edited rc.local to do this, and filed bug 637551. Grepping /var/log/messages* for alsactl shows nothing in F13 (the only version where I've had an /etc/asound.state file before yesterday).
(In reply to comment #4) > No, but as far as I can tell, initscripts only attempts to save mixer settings > during shutdown, not restore them at boot. I haven't manually edited rc.local > to do this, and filed bug 637551. Grepping /var/log/messages* for alsactl shows > nothing in F13 (the only version where I've had an /etc/asound.state file > before yesterday). OK. avcs can also appear in /var/log/dmesg and /var/log/audit/audit.log.
Nothing for F13 in /var/log/dmesg* or /var/log/audit/audit.log*, either (grepping for alsactl).
Dan, could you take a look at this one? It seems to be easy to reproduce, anyway ... :-)
I am going to add a transition from unconfined_t to alsa_t which should correct the labeling. Fixed in selinux-policy-3.9.5-9.fc14
(In reply to comment #8) > I am going to add a transition from unconfined_t to alsa_t which should correct > the labeling. > > Fixed in selinux-policy-3.9.5-9.fc14 Thanks, Dan.
(In reply to comment #2) > Confirmed that the problem also exists in Rawhide (alsa-utils-1.0.23-3.fc14), > F13 (alsa-utils-1.0.23-3.fc13), and F12 (alsa-utils-1.0.23-3.fc12). I still > have pulseaudio installed. F13: [root@walnut etc]# rm asound.state rm: remove regular file `asound.state'? y [root@walnut etc]# alsactl store [root@walnut etc]# ls -Z asound.state -rw-r--r--. root root unconfined_u:object_r:etc_t:s0 asound.state [root@walnut etc]# rpm -qa 'selinux*' | sort selinux-policy-3.7.19-57.fc13.noarch selinux-policy-targeted-3.7.19-57.fc13.noarch [root@walnut etc]#
In F12 with updates-testing enabled, which is also currently broken, I have selinux-policy-3.6.32-121.fc12.noarch selinux-policy-targeted-3.6.32-121.fc12.noarch
Of course this would get a lot easier to maintain if you used /etc/alsa/asound.*
Miroslav can you see about making this change in F12 and F13.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping