Definitely
BetaFE +1
And I think I'm currently also leaning towards
FinalBlocker +1
because it's easy to click outside of the window, and then not being able to go back. And clicking Quit in anaconda reboots the machine, so you can't even restart the whole installation easily. If people are against, I'm fine with just documenting this, but it bothers me how inconvenient this is and it can be probably very simply fixed just by launching blivet-gui maximized.

BetaFE +1

BetaFE +1
FinalBlocker +1

Though everything will be fine after a reboot in most of the cases,and as a
user who are easily distracted^^,I don't even run into this issue
once,with several days's heavy testing of blivet-gui,
but yes,it's inconvenient,plus good app should be robust,so
BetaFE +1

On Mon, Sep 11, 2023 at 10:26=E2=80=AFPM Luk=C3=A1=C5=A1 R=C5=AF=C5=BEi=C4=
=8Dka pagure@pagure.io wrote:

lruzicka added a new comment to an issue you are following:
BetaFE +1 FinalBlocker +1

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-qa/blocker-review/issue/1297

AGREED AcceptedBetaFE

The following votes have been closed:

• Accepted BetaFreezeException (+4, 0, -0)
  • +1 by kparal, frantisekz, lruzicka, lnie

AGREED AcceptedFinalBlocker

Discussed during the 2023-09-11 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates all of the disk management criteria, in the case you manage to trigger this by clicking outside of the blivet-gui window.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2023-09-11/f39-blocker-review.2023-09-11-16.00.txt

The following votes have been closed:

• Accepted FinalBlocker (+2, 0, -0)
  • +1 by kparal, lruzicka

Release F39 is no longer tracked by BlockerBugs, closing this ticket.