Description of problem:
Even with 'SELINUX=disabled' in /etc/sysconfig/selinux,
and 'selinux=0' in a boot command for a good measure, if
selinux-policy-strict was installed then updating the package
seems to affect the system. The most visible to me result is
that after such update one cannot open a new shell either
locally or via ssh. A reboot clears that condition
(together with everything else, unfortunately).
This is only a guess as nothing gets logged anywhere, AFAICT,
but selinux support seems to be the most likely candidate.
I noticed that effect only recently (last two rawhide updates?).
Version-Release number of selected component (if applicable):
Are you still seeing this?
Can you run selinuxconfig when it is happening?
I am no longer sure that I attributed that correctly. See bug #127048.
It seemed at the time that selinux was the most likely candidate but
possibly this was a coincidence. OTOH I cannot exclude that connection
Yes, this is still happening, although I cannot really predict when.
I will try selinuxconfig when this will strike again.
I got stuck again after the latest round of updates but this does
not seem to a selinux fault because this time around no
selinux-policy packages are installed.
selinuxconfig just prints
but otherwise does not have any effect. More details in comments
to bug #127048.
Ok I am going to close this bug and allow the other to move forward.