Can't Finish First Boot Setup (or let's say OOBE) - Gets Frozen / Stuck in The Middle of The Process

I’m sure it did scare away a ton of users considering how easy it is to trigger. And it STILL isn’t being addressed.

I had this happen on a Silverblue install when I tried to enable 3rd party repos. I had to do a hard shutdown. I switched to Cosmic Atomic and it did not have any issues during the install process.

Imagine my surprise when I found out that this problem had been known since April, but no one had done anything about it yet. And this is the “most stable” silverblue version of Fedora.

Is this looked at? how can I generate log files for the devs to solve this?

I signed up to say that this was my first experience with Fedora. I find it unlikely that I will try this OS again because of this installer issue. The fact that its been a problem for 6 months and this is still the featured installer on the front page, is baffling.

1 Like

I’ve pushed a workaround in https://pagure.io/workstation-ostree-config/pull-request/682. Tomorrow’s ISOs (Fedora nightly compose finder) should include it. Testing welcomed.

2 Likes

This should now have landed in the latest F43 ISO from Fedora nightly compose finder for testing.

1 Like

Still an issue on Fedora 43 as of today. I cant even get past the Privacy screen on first boot. Literally my first experience with Fedora coming from Arch haha… What a face plant!

Update: Working after re-installing, clicking the map and avoiding entering the city for time zone

The same issue on Fedora 43 Silverblue. I’m not sure if this is a Gnome or Fedora issue. But it is very disappointing that the issue exist since Fedora 42.

Thanks! I can confirm it works, you should push it as the main ISO. Although consider the fact that it removes the ability to live boot iso before installing it, but that’s meh, and especially since it’s a preview.

If it’s possible, making a live boot iso would be better, and then just when you want to install the distro, it will open that full screen install menu. Because like, changing mouse sensitivity before installing the distro is important, default high sens is a bit annoying.

Oh maybe live boot is available if I use the Workstation ISO instead of All boot ISO right?

I can confirm that this is still an issue. I run an old machine, no issue with Debian, the welcome screen got stuck at reboot after install on the second ssd. Fedora 43. Unable to enter timezone neither by typing nor by clicking. Broken rectangles at the bottom of the window.
Very disappointing from a trusted distro like Fedora.

The issue is in the search bar. It sometimes immediately bugs when you open the window, so I found out that disconnecting your keyboard before the time-zone setup works the best, then just click on the map to select your city (you might have to click around the middle black box for it to register). After that just connect your keyboard again and you should be fine. This bug has been on this version for a long time now.

If you get stuck, press Ctrl+Alt+F2, then Ctrl+Alt+Delete, which should restart everything.

For folks reporting issues when setting the timezone, this is a different issue than the one that got fixed. Please report it to the Anaconda developers.

Did it get fixed on Workstation, or just on Silverblue?

I did not know that this was impacting Workstation. I only fixed it for Silverblue. You need to report this to the Workstation folks then.

1 Like

Thanks. I think it’s tracked under this ticket:

Original ticket (marked as dupe, but useful to read as it’s more informative of the user-facing behaviour):

hi folks.
I worked around the bug by installing Fedora 42 and then upgrading it to the newer version by command line. I don’t know if there are ways to make the installer work as it should. Funny enough it works fine on the KVM virtual machine hosted by the same old pc.
Thanks
Alberto

I think I’m the one confusing this issue then with another one. I fixed the Third Party Page hang. The timezone one, which this thread seems to be about, I did not fix.

This could be the issue, as i recently installed the same ISO on a AMD/AMD machine and it worked flawlessly. Perhaps, adding nouveau.config=NvGspRm=0 as a boot parameter could work around this bug. Hmmmm, isn’t it time to wipe my Lenovo X1 Extreme Gen5? :thinking: :smiley:

Edit: Doesn’t work for me. But modprobe.blacklist=nouveau did help because of fallback to Software Rendering. Not a Solution, but usable as a workaround.