Additional info: hashmarkername: setroubleshoot kernel: 3.6.7-5.fc18.x86_64 type: libreport Potential duplicate: bug 714136
Created attachment 654521 [details] File: description
This looks like you are attempting to put down labels that the kernel does not understand. For example # chcon -t abc_t /var/log/ConsoleKit
(In reply to comment #2) > This looks like you are attempting to put down labels that the kernel does > not understand. > > For example > > # chcon -t abc_t /var/log/ConsoleKit These errors were generated on a default system by updating to the latest policy. I didn't run chcon -t abc_t /var/log/ConsoleKit
It was just example. What does # rpm -qa --scripts |grep chcon
other than generating a couple of local policies I haven't altered anything. $ rpm -qa --scripts |grep chcon /usr/bin/chcon "$SECXT" /var/log/lastlog >/dev/null 2>&1 || :
I guess you should reopen this if it happens again. This could have been something that happened during the upgrade where the upgrade mechanism attempted to put a label down before the policy was updated. Basically mac_admin means something tried to put a label on the disk that the kernel did not understand.
I was running yum update on a fairly fresh installation of Fedora 18 and I got this. Let me know what info you need to fix this problem. Thanks!
Figure out what package has chcon in a script, maybe lastlog?
rpm -qa --scripts | grep chcon /usr/bin/chcon "$SECXT" /var/log/lastlog >/dev/null 2>&1 || : On F19. Now if the kernel would tell us what context was attempted to be set, it would make this easier.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.