Set up keeps crashing - Fedora Silverblue

Hello!
Now with the release of fedora 42 I wanted to try out Silverblue for the first time. But every time in the initial set up when it asks me to set my time zone (which doesn’t make any sense imo because I already set it up in the installer but Gnome things ig) it freezes the app and I can’t continue.

The only option I have available is to suspend the devices which doesn’t help.
GPU: Nvidia
CPU: Intel

The signing of the ISO and gpg key were correct

Process:

  1. Start the installer
  2. Encrypt the disk (not sure if this changes anything when setting up the OS)
  3. Install
  4. Enter password
  5. Go through the installer as normal
  6. Set time zone
  7. Freeze
  8. The end

Expected situation: I can use the OS

Any solutions? I’m kinda desperate tbh.

Rant moment - skip if u want: Things like this shouldn’t make the cut. There’s a reason why the beta releases exist, and I don’t think that they worked as intended if you can’t even use the OS after a fresh install. Fedora is supposed to be a serious project and I like it, but when situations like this happen is just sad. Before when I tried sb 42 on a vm it also used to freeze when enabling the 3rd party repos, but there was a way to skip that so it wasn’t that bad. However there’s now no way to skip the time zone and it’s frustrating to say the least.

What am I even supposed if nothing work? I don’t have other usb stick, and even if I had, how am I supposed to flash a new ISO if my desktop machine doesn’t work because of this untested release?
Thank you and sorry for the rant.

PD: Sorry for any grammatical mistakes

IT FINALLY WORKED

I had to reboot the system like 5+ times and do some reinstalls of the OS but it finally worked. I also set on my bios the optimus mode instead of the only dgpu mode.

Still, I think my point remains. This situations shouldn’t make the cut

Hello. Your issue is related to this one here.

The problem you had is that using the search bar in the time zone section breaks the setup process. If you select your time zone on the map directly (by clicking on it), it shouldn’t happen. The bug has been reported here.

1 Like