Sometimes (but not always) when the keyboard page shows up in gnome-initial-setup, the Next button shows up as grayed out. If the user picks a different keyboard (or even the already selected one) the button springs to life. This is fixed by https://bodhi.fedoraproject.org/updates/FEDORA-2023-daa37520a8 It would be good to get in the beta (though not critical) Reproducible: Sometimes
FEDORA-2023-daa37520a8 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-daa37520a8
+3 in https://pagure.io/fedora-qa/blocker-review/issue/1292 , marking accepted FE.
FEDORA-2023-daa37520a8 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-daa37520a8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-daa37520a8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-6c61180a28 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-6c61180a28` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-6c61180a28 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-cace02f5f0 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-cace02f5f0` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-cace02f5f0 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
As webUI has been deferred to F40 and this bug is webUI-specific, deferring blocker/FE status for this bug.
this fix was definitely pushed out, and I haven't seen this problem in openQA lately.