Live images built with libxcrypt 4.4.21 do not reach a login screen on boot. This affects at least KDE and Workstation live images. It's happening on today's Rawhide compose, and also on the libxcrypt 4.4.21 updates for F33 and F34 in openQA testing. Booting an affected Workstation live with `systemd.debug-shell=1` so you can get a shell on tty9 and examining the journal shows these errors from gdm: May 27 01:00:04 localhost-live systemd[1]: Starting GNOME Display Manager... May 27 01:00:04 localhost-live systemd[1]: Started GNOME Display Manager. May 27 01:00:05 localhost-live gdm-autologin][1422]: pam_unix(gdm-autologin:account): expired password for user liveuser (root enforced) May 27 01:00:05 localhost-live gdm[1403]: Gdm: gdm_session_handle_secret_info_query: assertion 'self->user_verifier_interface != NULL' failed May 27 01:00:05 localhost-live gdm-autologin][1422]: pam_pwquality(gdm-autologin:chauthtok): conversation failed May 27 01:00:05 localhost-live gdm-autologin][1422]: pam_pwquality(gdm-autologin:chauthtok): user aborted password change indicating some kind of issue between libxcrypt and pam, I think. Non-live images seem to be working OK - we can run an install from the netinst or Server DVD and log in as a user created during install, for instance - so this is probably somehow specific to the 'liveuser' account created during boot of live images by the `livesys` initscript. Affected image for testing: https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20210526.n.0/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-Rawhide-20210526.n.0.iso
Marking as an automatic F35 Beta blocker per "Complete failure of any release-blocking image to boot at all under any circumstance - "DOA" image (conditional failure is not an automatic blocker)" - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process#Automatic_blockers .
Thanks for the quick report. A fixed release of libxcrypt is currently building and will be available soon.
FEDORA-2021-e6916d6758 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e6916d6758
FEDORA-2021-fed63bd217 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-fed63bd217
Thanks! The openQA failure that happened on the updated f34 update was not a real bug, this time, but me not quite getting the version numbers right in a test for handling a difference in Cockpit behaviour across versions. I've fixed that (hopefully) and rerun the test.
FEDORA-2021-fed63bd217 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-fed63bd217` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-fed63bd217 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-e6916d6758 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-e6916d6758` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e6916d6758 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
*** Bug 1965345 has been marked as a duplicate of this bug. ***
FEDORA-2021-e6916d6758 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-fed63bd217 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.