Hi,
Not sure if anyone else is seeing this, but saw that there were new 42-based ISOs made yesterday and decided to give them a go. My system is 5800x3d + 7900xtx (no Windows) and the installer fails to start wayland after testing the media. This happens in both Ventoy (normal & grub modes; my usual way of installing) and directly written to a different USB with Fedora Media Writer. Could this be an AMD-only issue, or is there something else working against me here? I’m going to try Kinoite to see if I see the same issue and report back.
Didn’t see anyone else reporting this, so wanted to drop something here in case anyone else comes looking.
Kinoite does install. I was then able to rebase to Bazzite, but I suspect this isn’t just a me issue with the new ISOs? Would love another confirmation one way or another.
I downloaded their KDE version and I am stuck on gray screen when trying to install.
AMD CPU, Nvidia GPU.
Also a Reddit thread with several people having this problem:
The annoying part is that I had a working KDE install but I really wanted to try Gnome and the Gnome install worked but the computer kept crashing and freezing, and my Steam games would no longer launch.
Now due to the gray screen I can’t go back.
I also grabbed the gnome iso at the same time and had time to go back and write/test that one, and it works! Unsure what the differences are but that one seems alright.
You could do what I did in the short term—use Kinoite installer and rebase to KDE version of Bazzite
1 Like
I shall try it tomorrow, thanks for the tip. 
I had the same problem as well. I typed CTRL+ALT+F1 and got this screen:
I tried the text mode, but there were no advanced option for full disk encryption with LUKS so I cancelled. I’m going to try the RDP option.
No luck. Anaconda fails. I tried installing in a basic display under the Troubleshooting menu, I had the same error.
My PC is custom-made with Asus ROG Strix B550-F Gaming motherboard, AMD Ryzen 7 5700X, NVIDIA GeForce RTX 3060 12GB.
I noticed the torrent links to the 2025-04-30 version… I’m going to try that one as soon as the download is finished.
1 Like
How did it go? Did you manage to install it? I just woke up so I might try the Kinoite route.
So the torrent one is installing for me, thank you.
Yeah, I did succeed in installing it on my PC. Bazzite 2025-04-30 available on the torrent link is Bazzite 41, not 42. The problem must be with 42. It did install, and it booted to the session manager (SDDM).
But I found a bug, and could not use Bazzite. The username and password I configured did not work. On first boot, no user was selected and I had to type my username. It didn’t work. It was like my user account wasn’t added. (See below for the reason.)
So I downloaded the stable version of Aurora (which I knew I could rebase to Bazzite), wrote it to my USB key using Fedora Media Writer, and found yet another bug: the key written by Fedora Media Writer wasn’t recognized by my UEFI/BIOS as a bootable media. Maybe it didn’t erase everything on it. Previously I had used balenaEtcher on Ubuntu on my PC to write Aurora on that key (in order to install it on my laptop).
So I installed balenaEtcher on my spare laptop with Aurora 41 (downloaded the zip, extracted it and launched the executable) to write Aurora to my USB key.
And I had the same bug with Aurora 41 on my PC. Could not log in. Then it hit me.
I had specified a supplementary group to add my user to during the installation. Both times. users. Which doesn’t exist, but I specified the group ID (GID) 100, just like in Ubuntu. Adding groups is supposed to be supported, but it make the installation fail.
I’m going to file a bug. I’m writing this on Aurora 41 on my PC. Good enough, going to sleep. 
I have logged in with the torrent version now and I am reinstalling my usual software without issue.
I don’t know how to set up groups (still a newbie!) so I guess that’s why.
I take it that upgrading to 42 will be possible just by hitting update (eventually when they fix it)?
I think we have a few different issues being mentioned here.
One major change this cycle is that anaconda now run in Xwayland instead of X11. I’m guessing this is causing issues for you all.
The group bug doesn’t super surprise me. A lot of configuration like this is more geared towards first boot configuration but I am surprised that this fails to create a missing group. Or maybe it’s a bug trying to add the user to a group only defined in /usr/lib/groups.
