A couple of days ago, I ran ujust update and rebooted, only to find that I was stuck at boot. More precisely:
- I see the “Booting Aurora (FROM Kinoite 41)” on the upper left screen, which then disappears to the Lenovo screen with Aurora on the bottom.
- The “Booting Aurora (FROM Kinoite 41)” message shows up a second time before disappearing and seeing my mouse cursor.
- My mouse cursor disappears after 1 second and then “Booting Aurora (FROM Kinoite 41)” shows up a third time and gets stuck there.
Rebasing to bluefin-dx latest will give me a functional desktop and the gdm manager displays just fine. but if I rebase to aurora or even kinoite, I receive the same issue.
Incidentally, an issue was created in Fedora Silverblue where someone rebased from silverblue 41 to kinoite 41 and experienced the same issue that I did: Rebasing from Silverblue 41 to Kinoite 41 leaves you with a broken SDDM · Issue #597 · fedora-silverblue/issue-tracker · GitHub
the interesting bit of info:
" Apparently this is caused by sddm not having an entry inside the /etc/shadow file. I tried to fo into /sysroot/ostree/deploy/fedora/deploy/609cb8e6313871180f6f98b1a84f0a2b83b97e7a3703d4aeab569223125b9a4e.0/etc (I know it is the Kinoite deployment because sddm.conf is there) and the shadow file indeed has no entry for sddm."
The upstream issue is still open. Technically, it’s not Aurora-specific or Universal Blue-specific, but it’s a serious bug in terms of functionality. It might be rebase-specific and normally, I would test a fresh reinstall of Aurora stable iso on the same machine but this low-end laptop I am using also has the unfortunate circumstance of USB drive boot option mysteriously disappearing from the boot menu, so I’ve been relying solely on rebasing and ujust updates.