Description of problem: Version-Release number of selected component (if applicable): 3.13.1-183.fc24 How reproducible: Apply this update from updates testing Steps to Reproduce: 1. 2. 3. Actual results: GDM fails to display login screen Expected results: Login screen should display Additional info: Can downgrade via other console to workaround.
Workaround: downgrade to 3.13.1-182.fc24 I got quite angry about this update leaving me with a system that not only doesn't boot to gdm but also was barely able to even log in as root on any tty due to overloading the system with AVC denials. Don't you have a build/test system that at least tries to install this policy and reboot the system into a desktop? It looks like you don't and I suggest you add one. This report might not be the right place, is there some place where to request this? I know, this was on updates-testing and updates-testing is allowed (or even expected) to break sometimes. But still updates should not get submitted before being tested. This is especially important for updates from "Critical Path". For reference, here is the bodhi page: https://bodhi.fedoraproject.org/updates/selinux-policy-3.13.1-183.fc24
On a side note, you should be able login by passing "selinux=0" in grub2 kernel bootline.
(In reply to Tommy He from comment #2) > On a side note, you should be able login by passing "selinux=0" in grub2 > kernel bootline. Yes, if you use enforcing=0 system will boot in permissive mode. I'm preparing new builds for fedora-rawhide and fedora-24 with fixes.
Thx for this BZ report and confirmation of selinux. I hit this also, and got more experience with dnf history and journalctl in the process. Looking forward to trying new build.
fedora@localhost ~]$ cat /etc/fedora-release Fedora release 24 (Twenty Four) [fedora@localhost ~]$ getenforce Enforcing [fedora@localhost ~]$ rpm -q selinux-policy selinux-policy-3.13.1-184.fc24.noarch [fedora@localhost ~]$ sudo ausearch -m AVC -ts recent <no matches> New selinux-policy builds: http://koji.fedoraproject.org/koji/buildinfo?buildID=758634
I find that booting with enforcing=0 still leads to the problem (GDM does not show a login screen), but that booting with selinux=0 lets everything work.
The new builds resolved the issue for me. Thx! Will report karma on bodhi.
I can confirm this issue. It's very annoying. You can't even properly use your keyboard in the console as Christian Stadelmann wrote. Please fix this ASAP.
Another workaround I found is to set in /etc/gdm/custom.conf WaylandEnable=false
Setting Wayland to false, is not working for me. Only disabling selinux to make gdm run again
The Fedora Rawhide update of yesterday seems to have included the correct fix. No hacks needed now as far as I can see. An excellent May Day surprise :-)
selinux-policy-3.13.1-184.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e163032315
I installed the 3.13.1-184.fc24 from updates testing and all appears to be well. So problem solved.
selinux-policy-3.13.1-184.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.