On today's Rawhide, if you install KDE and create a user during installation, the installed system boots not to SDDM (as expected) but to initial-setup, showing an "Installation Destination" spoke: https://openqa.fedoraproject.org/tests/758401#step/_graphical_wait_login/7 I haven't looked yet what happens if you fill that spoke out, but I can't imagine anyone would want to do that... Proposing as a Beta blocker as a violation of "A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility" - https://fedoraproject.org/wiki/Basic_Release_Criteria#Expected_installed_system_boot_behavior .
On an install with no user account, initial-setup runs - this is expected - but as well as the normal User Creation spoke, it also shows the "Installation Destination" spoke, and you can't exit initial-setup with it "incomplete". So this is a problem there too. https://openqa.fedoraproject.org/tests/758398#step/_graphical_wait_login/6
Fixed in a pull request https://github.com/rhinstaller/anaconda/pull/3105.
If you could run a build with the fix soon it'd be great, as several openQA tests are blocked on this. Thanks!
...well in fact it would be good if we could also fix https://bugzilla.redhat.com/show_bug.cgi?id=1918940 , as *Workstation* openQA tests are blocked on that :)
Anaconda build with fix for this bug: anaconda-34.19-1.fc34
(In reply to Martin Kolman from comment #5) > Anaconda build with fix for this bug: anaconda-34.19-1.fc34 Forgot the koji build link: https://koji.fedoraproject.org/koji/taskinfo?taskID=60163166 (In reply to Adam Williamson from comment #4) > ...well in fact it would be good if we could also fix > https://bugzilla.redhat.com/show_bug.cgi?id=1918940 , as *Workstation* > openQA tests are blocked on that :) Let's get this one out of the door first & I can do another build with that one tomorrow. :)
This bug got fixed already. KDE installs are broken ATM, but the fix was confirmed in a few composes before that bug appeared.