ubiquity-dm (maybe-ubiquity/only-ubiquity) missing keyboard indicator, when booted into Esc, Russian locale by default from isolinux BIOS boot

I'm seeing a similar issue on 19.10 doing a french install on an uefi machine
- boot from the usb stick with Ubuntu Desktop 19.10
- select the 'install' item from the text-mode-menu
- in ubiquity select french
- keep the default selected keyboard (french - alternative)
-> typing on that screen the layout is azerty
- using custom partitioning (in case that makes a difference)
- on the user creation page, the layout is english/qwerty

Thinking about it, it's probably wrong on the partionner step as well since for entering digit I had to not-use-shift where you need to do that with the french layout

Check that this is not a duplicate of the keyboard bug https://wiki.ubuntu.com/Ubiquity/KeyboardBug

I can't remember, but i think one only gets the full localised keyboard if one uses 1) bios boot 2) picks language at isolinux time

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

I can't reproduce this with the latest focal daily -- I followed the instructions from comment #2 as closely as I could UEFI, selecting install from boot menu, french language, french keyboard, custom partitioning, and the layout was still active in the user creation screen. It was a VM rather than real hardware but if that matters I'm going to cry :)

Let me know if there is a way to reproduce and I'll look into it.

PS: I tested the ISO with serial 20200413

I used BIOS boot, and preseed Esc at the burning-person screen, and selected Russian option from the language selection.

This way, russian locale is appended to the kernel commandline and upon live session boot, I expect Russian locale to be selected for everything, and Russian/English keyboards available.

Booting into "only-ubiquity" mode, keyboard selection indicator is missing and pressing "super+space" doesn't change keyboard layout either.

If on the other hand I boot into full live session, I see that there is keyboard selection indicator and I can change keyboard layouts with "super+space".

It seems like "keyboard-indicator" is missing from the "maybe-ubiquity/only-ubiquity" ubiquity-dm session.

However, ubiquity.json gnome-shell mode does have:

"right": ["a11y", "keyboard", "aggregateMenu"]

i wonder why it doesn't show up.....

Oooh, gsd-keyboard is missing

This bug was fixed in the package ubiquity - 20.10.4

---------------
ubiquity (20.10.4) groovy; urgency=medium

  [ Dimitri John Ledkov ]
  * d-i: drop distro patch of partman-swapfile, included in v2
  * d-i: vendorize archdetect binary, to remove hw-detect
  * Do not vendorize shim-signed scripts, simply use shim-signed scripts
    that are installed in live session already anyway.
  * ubiquity-dm: start gsd-keyboard for keyboard indicator (LP: #1847307)
  * autopilot: pacify new pyflakes

  [ Jean-Baptiste Lallement ]
  * Calculate partition number instead of reusing swap
  * Add partition for key store.
  * Add creation of the key store
  * Key store on ZVol
  * Encryption is enabled with --encrypt|-e
  * Added encrypted swap on ZFS systems
  * Use env instead argument to enable encryption
  * Properly calculate position of extended partition
  * force key when zfs encryption is activated.
  * Properly unmount target and its friends on zfs installation.
  * Add ZFS encryption UI
  * partition table is always GPT
  * Various fixes in zsys-setup
  * Moved keystore to /run/

 -- Dimitri John Ledkov <email address hidden> Mon, 15 Jun 2020 18:18:40 +0100

Hello corrado, or anyone else affected,

Accepted ubiquity into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubiquity/20.04.15.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

SRU verification for Focal:
I have reproduced the problem with ubiquity 20.04.15 in focal and have verified that the version of ubiquity 20.04.15.1 in -proposed fixes the issue.

Marking as verification-done

This bug was fixed in the package ubiquity - 20.04.15.1

---------------
ubiquity (20.04.15.1) focal; urgency=medium

  [ Sebastien Bacher ]
  * debian/real-po: updated translations from launchpad, including strings
    from the new subpage for RST (LP: #1874103)

  [ Michael Hudson-Doyle ]
  * make grub_default consider the boot argument in the non-removable case
    (LP: #1847898)

  [ Jean-Baptiste Lallement ]
  * Enable ZFS autotrim (LP: #1883686)
  * Use persistent path for pool's vdevs (LP: #1880869)
  * Do not export all pools (LP: #1875045)

  [ Dimitri John Ledkov ]
  * ubiquity-dm: start gsd-keyboard for keyboard indicator (LP: #1847307)

 -- Dimitri John Ledkov <email address hidden> Tue, 16 Jun 2020 11:17:42 +0100

The verification of the Stable Release Update for ubiquity has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.