Created attachment 1004329 [details] DNF update log Description of problem: (Using systemd component, feel free to reassign it if that's not the right one) Recently I upgraded my machine (Lenovo T430s) from Fedora 21 to 22 using fedup (after adding patch from https://bugzilla.redhat.com/show_bug.cgi?id=1185604 and recompiling F21's systemd). The upgrade process went smooth and I was able to boot my machine. Later I updated all packages on my system using DNF (see update.log) and rebooted the system. It became unbootable. So I added a few kernel parameters (like systemd.log_level=debug systemd.log_target=kmsg). After adding the debug statements, system booted which was weird. Later the day rebooted and it failed to boot again. No new updates were installed or kernel parameters were changed in the meantime. When I rebooted it again - it worked again :| I tried also to boot it in the multi-user target, worked fine every time. Only graphical target is failing randomly. For me it seems that there is some race condition somewhere in systemd. I'll attach all logs shortly, maybe you can get something useful from it, since this is a bit outside of my comfort zone :) Version-Release number of selected component (if applicable): kernel-4.0.0-0.rc3.git0.1.fc22.x86_64 How reproducible: Randomly. Steps to Reproduce: 1. Reboot Actual results: Sometimes boots, sometimes fails. Expected results: Normal boot :)
Created attachment 1004330 [details] Boot log with debug
Created attachment 1004331 [details] Screenshot of the console from a failed boot
Seems to be the same as bug 1201964
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.