No Russian layout during keyboard configuration setup

Whenever Russian–Russian is selected from the menu, setxkbmap sets the layout to us,ru

Keyboard layout can be toggled to en2 with Super+Space and Russian layout will be set

bug #1870219 might be related

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1945848

The same behavior is observed even if the language of Ubiquity is set to Russian.

Status changed to 'Confirmed' because the bug affects multiple users.

To me this looks like bug #1875062.

No. In the description of that bug, the user explicitly states that "selecting Norwegian keyboard is provided and keys are responding correctly at that stage", while in my case, Cyrillic letters are not shown at all. The layout has to be set to en2 for them to appear, which is a bit tricky (for a new user at least) because there are no hints or tips on how to switch layouts whatsoever. Besides, it's counterintuitive. When a layout is selected from the list, it should be set automatically.

Selecting Russian and clicking on "Try Ubuntu" starts a Live session with the correct layout. Russian ЙЦУКЕН is set.

However, as soon as Ubiquity is launched again (i.e. done with testing, I like the system, let's install), "us" is added as the primary layout, which is confirmed by "setxkbmap -query".

The common denominator between this bug and bug #1875062 is that the selected keyboard layout is not reliably effective all through the installation steps in ubiquity. In worst case it leads the user to choose a password in the belief they are using the selected (non-us) layout and then fails to login at first login after the completed installation.

A note to self and anyone else that might be investigating this: I checked our hirsute (21.04) and old focal (20.04.0) images and this is not a regression, the same test case was failing even there. So this basically is a long standing problem in ubiquity. Though I don't think I saw this reported in the past, even though it's really easy to reproduce.

Isn't this the keyboard-configuration feature where if you select a keyboard layout/variant that does not include latin keys, a different layout/variant (usually us/default) that does is also configured, as completely the install may require typing latin characters? In d-i you also get an option to choose the keystroke to toggle between the latin-capable and the selected layout but it doesn't seem ubiquity offers this choice and defaults to "no toggle".

Yeah, that was my understanding when looking at the ubiquity console-setup code as well. And this is basically what console-setup in Debian is doing as well - it detects whether the selected locale has 'latin' characters or not, and if not, it always sets us as the first layout (in this case setting "us, ru").

I agree with Michael that I think the best way to fix this in incoming releases is enabling users to switch the layouts. But certainly this is not something we can change for 21.10 - as it's too close to release. So bumping down the priority and re-targeting for next release.

@Łukasz: Want to mention that bug #1762952 seems to be related. It was the fix of that bug which changed the default to "No toggling". That bug also discusses an issue with the related GNOME controls not playing well with console-setup.

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will not be fixed for that specific release.