As above, it was a known bug but it’s been 6? weeks, is there some magic chicken sacrifice I can’t find?
It’s pretty bad, login fails, ssh fails, tty fails, goto hard reset. Everything works fine on 42. My usual Fedora just wait pattern should be fine by now, but no.
Anyone else ? I tried discord but that’s a sh*tshow now, yay, that was unexpected /s. AMD system, CPU, GPU… happy to provide specs, some layering that I’d rather not remove (mergerfs and snapraid in particular in the fstab)
Okay if you layered something that is one of the first things you need to remove because layering automatically makes the system different from what baseline people usually have and thus are unable to diagnose correctly
If you’re referring to the SDDM / Plymouth bug ( 2404966 – sddm fails to start with rhgb kernel argument ) the workaround is to simply hit escape when the Plymouth screen starts. There is a race between Plymouth and SDDM both trying to grab the display, so pressing escape to kill Plymouth is the simplest solution for the time being.
You can also modify the kernel args in GRUB to remove the Plymouth karg (rhgb) either manually in the GRUB boot screen or through modifying the GRUB config, but that is a more advanced and cumbersome solution.
Hi! I have an AMD CPU/GPU too. A month ago, I installed Bazzite KDE Desktop, and everything was fine until I updated it. After the update, I started getting a black screen instead of the login screen. Nothing is layered.
What helps is: switch to a TTY (Ctrl+Alt+F2) → enter my login and password →run “startplasma-wayland”. But I have to do this every time after rebooting the PC. Then I simply enabled autologin, and the system started booting normally straight to the desktop.
System Settings → Login Screen (SDDM) → Behavior… → Automatically log in - as user … - with session Plasma (Wayland) → Apply".
So, I have a bit of a lazy attitude to updates breaking stuff after many years on linux, I think ‘this too shall pass’ and rollback to a working version for a week or two. Works 90+% of the time.
I finally got around to doing the basic step of creating a new user, worked fine. Hmm, go su , and it’s borked coz no zsh, I’d failed to layer it on the new version. Did so, now all is fine.
Mark as PEBKAC