Description of problem:
GNOME Initial Setup doesn't run; or it runs and isn't drawing completely on-screen.
Version-Release number of selected component (if applicable):
1 in many, haven't seen it before or since
Steps to Reproduce:
1. Automatic install, reboot
Created attachment 1713518 [details]
screenshot of problem
This is what I see following boot.
Created attachment 1713519 [details]
I've experienced this now three times. Twice with Fedora-Workstation-Live-x86_64-33-20200902.n.0.iso clean installs to qemu-kvm. And once with Fedora-Silverblue-ostree-x86_64-33-20200903.n.0.iso.
Proposed as a Blocker for 33-beta by Fedora user chrismurphy using the blocker tracking app because:
A working mechanism to create a user account must be clearly presented during installation and/or first boot of the installed system.
Created attachment 1713669 [details]
I decided to do a test loop to see how often it happens. Boot, do I get the tiny window (fail) or do I get setup, force power off and reboot. 4 out of 10 fail. No discernible pattern.
Chris: I'd say the summary is still a bit wrong. It doesn't fail to launch, it *does* launch. It just launches in a tiny window. :)
It's not completely visible, but Adam linked his own upstream report here:
Chris, can you double click on that window header, or drag the corner, to enlarge the window?
Yes. And it turns into g-i-s :) Indistinguishable from a normal/expected launch.
I have experienced this, but I am convinced that this behaviour is only limited to virtual machines. I have currently installed Fedora Workstation on my two bare metal machines and the initial setup went correctly, as well as the new overview slideshow.
it's a bit of a small sample size though, doesn't seem enough to say for sure that it's VMs only.
Still, I kinda trend -1 blocker on this for Beta at least, since it's only intermittent and it's not a complete failure, you just need to maximize the window. For Final it would be a closer call as it's pretty awkward.
Criterion: "must be clearly presented"
Is it? I had no idea that window was g-i-s. It didn't occur to me to resize it until Kamil suggested it. The original title of the bug, it's clear I figured g-i-s wasn't launching at all. *shrug*
On the plus side, maybe some non-trivial number of users will pull the power cord as the work around, and we get some extra Btrfs power off tests for free. :D
goddamnit, hoist by my own petard again. i fall back on the 'it doesn't always happen' argument. :P
CommonBugs should solicit reports if it happens on hardware. We know it happens on VMs, but not if or how often it happens on the real deal.
(In reply to Adam Williamson from comment #11)
> Still, I kinda trend -1 blocker on this for Beta at least, since it's only
> intermittent and it's not a complete failure, you just need to maximize the
> window. For Final it would be a closer call as it's pretty awkward.
Hi, can you please vote at https://pagure.io/fedora-qa/blocker-review/issue/61 next time so that we have all votes in one place? Thanks a lot.
Rejecting BetaBlocker and accepting BetaFE based on this discussion:
kamil: that was a trend not a vote. :P
Discussed during the 2020-09-08 blocker review meeting: 
The decision to classify this bug as an "AcceptedBlocker" was made as it violates the following criterion:
"A working mechanism to create a user account must be clearly presented during installation and/or first boot of the installed system".
When the bug happens, g-i-s is not "clearly presented".
so there's some code doing some unnecessary step. for some unknown reason that unnecessary step triggers this bug. but it shouldn't do that step anyway, so I just did a build that gets rid of it.
FEDORA-2020-598a49abc4 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-598a49abc4
FEDORA-2020-598a49abc4 has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-598a49abc4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-598a49abc4
See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-598a49abc4 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.