#867 [systemd] Czech qwerty layout configured in anaconda, but qwertz layout used in disk unlock and in VT console | rhbz#2121106
Closed a year ago by blockerbot. Opened 2 years ago by blockerbot.

Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2121106
Information from BlockerBugs App:
2121106

Current vote summary

  • Rejected FinalBlocker (+0, 0, -1)
  • Accepted BetaFreezeException (+0, 0, -0)
  • Accepted FinalFreezeException (+0, 0, -1)

Commented but haven't voted yet: geraldosimiao, jonathanspw, coremodule, gui1ty, kparal

The votes have been last counted at 2022-09-19 18:17 UTC and the last processed comment was #comment-817154

To learn how to vote, see:
https://pagure.io/fedora-qa/blocker-review
A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)


FinalBlocker +1
As described by Kamil in the ticket

AGREED AcceptedFinalBlocker
AGREED AcceptedBetaFE

Discussed during the 2022-08-29 blocker review meeting: [0]

The decision to classify this bug as both an "AcceptedBlocker (Final)" and an "AcceptedFreezeException (Beta)" was made as it is a clear violation of the Final criteria, and since it affects the install process so can't be fixed with aupdate and would be annoying for Czech users, we also grant it Beta FE status.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-08-29/f37-blocker-review.2022-08-29-16.01.txt

The following votes have been closed:

BetaFE +1 FinalBlocker +1

I think we should re-evaluate this blocker. Turned out that:
1. This only affects Czech, it's not a generic issue.
2. This only affects system which you install with Czech (qwerty) + US keymaps. If you install just using Czech (qwerty), it works fine. If you install using Czech (the default = qwertz) + US, it works fine. If you install using US + Czech (any variant), it works fine.
3. This bug has been present for a long time, at least from Fedora 30 (tested), but probably much longer.

REVOTE FinalBlocker

I really don't like picking and choosing which layouts are popular enough to be blockers and which aren't. But reading the bug report, the comment above, and the "There may be times where a requirement is unmet only in a particular configuration, such as with some keyboard layouts but not others, or if a particular character is used in a username, password or passphrase. In such cases, the release team should use their judgement and refer to precedent to determine whether or not the issue should be considered to block the release" part of the release critera, I will sleep just fine voting this down.

FinalBlocker -1
FinalFE -1

AGREED RejectedFinalBlocker
AGREED AcceptedFinalFE

Discussed during the 2022-09-19 blocker review meeting: [0]

The decision to classify this bug as a "RejectedBlocker (Final)" and an "AcceptedFreezeException (Final)" was made as the new details about how specific this bug is (you have to manually choose this exact combination of X layouts to trigger it), and the difficulty of fixing it fully, we agreed this is too conditional of a violation to count as a blocker. However, we grant it a freeze exception so we have time to land at least the moderate improvement that should be possible.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-09-19/f37-blocker-review.2022-09-19-16.00.txt

The following votes have been closed:

  • Rejected FinalBlocker (+0, 0, -1)
  • Accepted FinalFreezeException (+0, 0, -1)

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

a year ago

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

Login to comment on this ticket.

Metadata