On 05/11/2017 04:29 PM, stan wrote:
It is surprising that an update would cause this problem in F24,
since
it is in maintenance mode, and should be receiving only security
updates. If you can get to a console, either by Rick's method or mine,
you could also look at /var/cache/dnf.rpm.log* to see which updates
occurred. Also look at journalctl -b, to see the boot messages from the
unsuccessful boots (probably the same as /var/log/boot.log).
If I'm not mistaken, F24 has passed its End of Life, and receives no
official updates, even for security, although third parties such as
Adobe may ignore this. It might be possible to back out by using this
command as root:
dnf history undo last
After this is finished, reboot and see if it works.