Bug 706750
| Summary: | selinux is preventing gdm from starting and user's login | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | cornel panceac <cpanceac> | ||||
| Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | dominick.grift, dwalsh, mgrepl | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-05-22 18:12:38 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
You could try re-installing the policy, If that works then we know that something in the upgrade path f13 -> f14 may be broken in selinux-policy package. (Other packages could also e responsible i imagine) Try this at you own risk though: 1. setenforce 0 (i know it is probably already permissive since it wouldnt let you boot otherwise) 2. yum erase selinux-policy selinux-policy-targeted (only proceed if it does not try to erase any other alleged dependencies) 3. mv /etc/selinux/targeted /etc/selinux/targeted.backup 4. yum install selinux-policy selinux-policy-targeted 5. touch /.autorelabel && reboot (this step may not be needed since you relabeled just recently. Actually before "touch /.autorelabel && reboot" edit /etc/selinux/config and set SELINUX=enforcing. Because if you de-install then it will edit the config file to set it to disabled. *** This bug has been marked as a duplicate of bug 702865 *** (In reply to comment #1) > You could try re-installing the policy, If that works then we know that > something in the upgrade path f13 -> f14 may be broken in selinux-policy > package. (Other packages could also e responsible i imagine) > > Try this at you own risk though: > > 1. setenforce 0 (i know it is probably already permissive since it wouldnt let > you boot otherwise) > 2. yum erase selinux-policy selinux-policy-targeted (only proceed if it does > not try to erase any other alleged dependencies) > 3. mv /etc/selinux/targeted /etc/selinux/targeted.backup > 4. yum install selinux-policy selinux-policy-targeted > 5. touch /.autorelabel && reboot (this step may not be needed since you > relabeled just recently. thank you very much dominick, that fixed it. |
Created attachment 500290 [details] the log file Description of problem: if selinux is set to enforcing in /etc/selinux/config , i can not login with root or any other user, and gdm is not starting. Version-Release number of selected component (if applicable): # rpm -q selinux-policy selinux-policy-3.9.7-40.fc14.noarch How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: the system was upgraded from f13. adding setenforce=0 in kernel line is useless. touch /.autorelabel (fixfiles onboot) is useless. creating and applying a custom policy is useless. the only way to use this system is setting selinux to permissive in config file. any help is greately appreciated.