#566 [anaconda] When running anaconda on Wayland with two keyboard layouts configured, hitting any modifier key with the second layout selected switches to the first layout | rhbz#2016613
Closed 2 years ago by blockerbot. Opened 2 years ago by blockerbot.

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

Current vote summary

Commented but haven't voted yet: catanzaro, lruzicka, kparal, coremodule, mattdm

The votes have been last counted at 2021-10-28 13:30 UTC and the last processed comment was #comment-759418

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

The ability to switch Keyboard layouts correctly is important

Uh, normally I would say "this is obviously a blocker" because not being able to type properly is really game over. If I were to hit this bug, I'm giving up on Fedora, installing something else, and not looking back.

But this is confirmed to affect F34, so it's not an F35 regression. And that's a very important consideration too. It's a very long time for nobody to notice and report the issue.

Uh, normally I would say "this is obviously a blocker" because not being able to type properly is really game over. If I were to hit this bug, I'm giving up on Fedora, installing something else, and not looking back.

There would be workaround to fix it, if someone wanted to use special character but could not during installation and this could be explained in the Docs, so there's no need to leave Fedora for good, imho.

But this is confirmed to affect F34, so it's not an F35 regression. And that's a very important consideration too. It's a very long time for nobody to notice and report the issue.

Which might mean that there are not many new KDE users requiring to use special characters in their name, but I think we should try to fix this as soon as possible before someone else notices it.

Which might mean that there are not many new KDE users requiring to use special characters in their name, but I think we should try to fix this as soon as possible before someone else notices it.

OK, what I missed is that this bug only makes it impossible to use the secondary keyboard layout. The primary keyboard layout still works fine, so you can still type normal capital letters like 'S'. It's only if you need to type 'Š' that you're going to have a problem. Yes? And then you would still be able to work around the issue by swapping your primary and secondary layouts temporarily until the install has been completed... yes? Or would that not work?

Anyway, I won't vote on this one because I cannot decide. Seems real bad, but not a regression from F34.

OK, what I missed is that this bug only makes it impossible to use the secondary keyboard layout. The primary keyboard layout still works fine, so you can still type normal capital letters like 'S'. It's only if you need to type 'Š' that you're going to have a problem. Yes?

Yes and no :) The bug only affects the secondary layout (which constantly switches to the primary one, when modifiers are pressed), yes. But let's not assume the primary layout is US. If I use my local national keymap as primary, and US as secondary, then I might be easily able to type 'Š' or 'Ф' and not so easily 'S' (if the national keymap doesn't allow that).

The problem can be worked around by swapping primary and secondary layouts, but that means a) you need to reorder them back in the installed system, system-wide, which might be difficult (does gnome-control-center support that?) b) it can present big hurdles if you decide to encrypt your drive, because that needs to be done using primary layout only (and if you switch the layouts later in the installed system, that's another pile of mess when dealing with the pre-boot environment).

At the same time, we didn't see these complains before, which suggests people don't hit this problem too often (or they don't report it).

AGREED AcceptedFinalBlocker

Discussed during the 2021-10-25 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates the following criterion:

"If a particular keyboard layout has been configured for the system, that keyboard layout must be used: ..."

"in the installer" is not listed in that criterion, but we agree this is an oversight and it is intended to be covered (we will rectify this later).

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-10-25/f35-blocker-review.2021-10-25-16.02.txt

The following votes have been closed:

I see this has been closed, but given what I understand from the report and comments, and particularly that this is not a regression from F34 and

At the same time, we didn't see these complains before, which suggests people don't hit this problem too often (or they don't report it).

I would like to gently suggest that if this is the sole remaining problem come Thursday, we deal with it in a way that does not slip the release further.

I think this is a good example of a bug to waive at Go/NoGo. It has been present for a long time (partially), and it seems quite difficult to fix.

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

2 years ago

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

Login to comment on this ticket.

Metadata