Keyboard selection is ignored in live environment ; in recent noble installations

[corrado venturini]

Installing in English language with Italian keyboard. At Install I selected Italian keyboard but installer keep using English keyboard.
The installed system has Italian keyboard as requested.
attaching screenshot with keyboard test.
entered all keys on keyboard top line without and with uppercase

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.495build1
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 7 16:09:04 2024
LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: subiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[corrado venturini (corradoventu)]

attaching log

[corrado venturini (corradoventu)]

pressing all keys of top row in Italian keyboard i see:
1234567890'ì!"£$%&/()=?^

[Ubuntu QA Website (ubuntuqa)]

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/2060387

[Olivier Gayot (ogayot)]

Hello and thank you for your bug report,

I wasn't able to reproduce the issue. I tried with snap version 75 and 107. Looking at the logs you shared, everything seems correct from the Subiquity standpoint so I'm not sure what's happening. Maybe ubuntu-desktop-provision can provide insight?

2024-04-07 13:58:54,864 DEBUG root:38 start: subiquity/Keyboard/input_source_POST:
2024-04-07 13:58:54,864 DEBUG subiquitycore.utils:119 arun_command called: ['systemd-run', '--wait', '--uid=1000', '--setenv=DISPLAY=:0', '--setenv=XDG_RUNTIME_DIR=/run/user/1000', '--setenv=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus', '--', 'gsettings', 'set', 'org.gnome.desktop.input-sources', 'sources', "[('xkb','us')]"]
2024-04-07 13:58:54,959 DEBUG subiquitycore.utils:133 arun_command ['systemd-run', '--wait', '--uid=1000', '--setenv=DISPLAY=:0', '--setenv=XDG_RUNTIME_DIR=/run/user/1000', '--setenv=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus', '--', 'gsettings', 'set', 'org.gnome.desktop.input-sources', 'sources', "[('xkb','us')]"] exited with code 0
2024-04-07 13:58:54,960 DEBUG root:38 finish: subiquity/Keyboard/input_source_POST: SUCCESS: 200 null
2024-04-07 13:59:03,187 DEBUG root:38 start: subiquity/Keyboard/input_source_POST:
2024-04-07 13:59:03,187 DEBUG subiquitycore.utils:119 arun_command called: ['systemd-run', '--wait', '--uid=1000', '--setenv=DISPLAY=:0', '--setenv=XDG_RUNTIME_DIR=/run/user/1000', '--setenv=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus', '--', 'gsettings', 'set', 'org.gnome.desktop.input-sources', 'sources', "[('xkb','it')]"]
2024-04-07 13:59:03,208 DEBUG subiquitycore.utils:133 arun_command ['systemd-run', '--wait', '--uid=1000', '--setenv=DISPLAY=:0', '--setenv=XDG_RUNTIME_DIR=/run/user/1000', '--setenv=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus', '--', 'gsettings', 'set', 'org.gnome.desktop.input-sources', 'sources', "[('xkb','it')]"] exited with code 0
2024-04-07 13:59:03,208 DEBUG root:38 finish: subiquity/Keyboard/input_source_POST: SUCCESS: 200 null
2024-04-07 13:59:09,294 DEBUG subiquitycore.utils:77 run_command called: ['udevadm', 'settle', '-t', '0']
2024-04-07 13:59:09,296 DEBUG subiquitycore.utils:96 run_command ['udevadm', 'settle', '-t', '0'] exited with code 0
2024-04-07 13:59:09,296 DEBUG probert.network:741 wlan_event {'cmd': 'TRIGGER_SCAN', 'ifindex': 3}
2024-04-07 13:59:10,367 DEBUG subiquitycore.utils:77 run_command called: ['udevadm', 'settle', '-t', '0']
2024-04-07 13:59:10,369 DEBUG subiquitycore.utils:96 run_command ['udevadm', 'settle', '-t', '0'] exited with code 0
2024-04-07 13:59:10,369 DEBUG probert.network:741 wlan_event {'cmd': 'NEW_SCAN_RESULTS', 'ifindex': 3, 'ssids': [(b'EOLO_181782', 'no status')]}
2024-04-07 13:59:10,369 DEBUG subiquitycore.utils:77 run_command called: ['udevadm', 'settle', '-t', '0']
2024-04-07 13:59:10,371 DEBUG subiquitycore.utils:96 run_command ['udevadm', 'settle', '-t', '0'] exited with code 0
2024-04-07 13:59:14,321 DEBUG root:38 start: subiquity/Keyboard/input_source_POST:
2024-04-07 13:59:14,330 DEBUG subiquitycore.utils:119 arun_command called: ['systemd-run', '--wait', '--uid=1000', '--setenv=DISPLAY=:0', '--setenv=XDG_RUNTIME_DIR=/run...

[corrado venturini (corradoventu)]

Found same problem today with ISO Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)

[Alan Pope 🍺🐧🐱 🦄 (popey)]

I'm able to produce a similar result with 107.

If I choose English (UK) at the keyboard layout screen of the installer, then "Test" the keyboard, I am unable to type # or £ from their expected locations on the UK keyboard layout. Whatever keyboard layout I choose, it uses English (US).

[Alan Pope 🍺🐧🐱 🦄 (popey)]

Further, confirmed still broken in revision 111 which I just got updated to.

[corrado venturini (corradoventu)]

Same problem installing Ubuntu from ISO dated 20240407 and 20240408
Same problem also installing Xubuntu from Iso 20240409 attaching screenshot

[David White (cppege-david-9ei9ny)]

Tried with daily build 2024-04-09 and issue is still present. Selecting a English UK keyboard doesn't change it from the default English US setting.

This because a particular problem later on when entering passwords because you may be unaware that you are entering different punctuation characters than you think, rendering your installed system inaccessible.

You can mitigate this by additionally changing the keyboard in system settings.

[Dennis Loose (dloose)]

It seems to me like this is an issue with the snap environment.
Subiquity runs
systemd-run --wait --uid=1000 --setenv=DISPLAY=:0 --setenv=XDG_RUNTIME_DIR=/run/user/1000 --setenv=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus -- gsettings set org.gnome.desktop.input-sources sources "[('xkb','it')]"
which has the desired effect when I run it as root from a terminal in a live session with the latest iso (20240409). However, if I enter subiquity's snap environment via
snap run --shell ubuntu-desktop-bootstrap.subiquity-server
first, the input sources aren't updated in the live session.

[corrado venturini (corradoventu)]

Note: problem comes with recent ISOs, I don't had the problem with the Ubuntu ISO dated 20240324
with snap:ubuntu-desktop-bootstrap stable/ubuntu-24.04 75

[Martin Wimpress  (flexiondotorg)]

I'm able to reproduce this issue with ubuntu-desktop-bootstrap revision 113.

If I choose English (UK) at the keyboard layout screen of the installer on Ubuntu MATE 24.04 beta image, then "Test" the keyboard, I am unable to type # or £ from their expected locations on the UK keyboard layout, just as Alan Pope reported. Whatever keyboard layout I choose, it uses English (US).

[Dennis Loose (dloose)]

Update: the underlying issue is yet another glibc version mismatch in the classic snap

[Sebastien Bacher (seb128)]

The recent regression on the Ubuntu Desktop ISO is because the GIO path isn't set for the subiquity process and it tries to load the dconf component from the system which is now incompatible with the snap glib since GNOME 46 landed, https://github.com/canonical/ubuntu-desktop-provision/pull/616 should resolve that issue

There is another problem that the way the keyboard is currently changed (calling to `gsettings set org.gnome.desktop.input-sources sources`) is probably going to work only for GNOME, that's bug #2058503 which has been now undupped from this one

[Dennis Loose (dloose)]

Since subiquity explicitly passes a custom environment to the gsettings command, setting GIO_MODULE_DIR at this level doesn't work. Instead we decided to move this into the front-end.

Fixed by https://github.com/canonical/ubuntu-desktop-provision/pull/627

[Sa Mo (samopedia)]

2024-04-15
This problem is still in /daily-live/current/noble-desktop-amd64.iso from 2024-04-15 06:41
(Swedish keyboard does not have any effect and "Detect" process does no help either)

Thank you all for your hard work.

[geole0 (geole0)]

Hello.
It is the same thing Language French keyboard frabch.
In the live USB, it is now nécessarry to do this command setkkbnq fr to write AZERTY otherwhise it is QWERTY.

[geole0 (geole0)]

Hello
The problem is same when choosing french language and french keyboard
in live USB, if we want to use keyboard or freefox , it s necessary to do this command
  "setxknqp fr"
to write in AZERTY otherwise it write in QWERTY.

[Sa Mo (samopedia)]

Tested /daily-live/current/ ISO from 2024-04-17 07:21
Problem with selected Swedish keyboard not working and "Detect" does not help, is still out there.

Many "warning", "failed" and "error" lines in log files.

[Dan Bungert (dbungert)]

Marking invalid for Subiquity as we aren't planning to address it there for 24.04. If it makes sense to revisit that for a future release, that should be discussed.

[corrado venturini (corradoventu)]

I don't understand, does this mean the bug won't be fixed for 24.04?

[Olivier Gayot (ogayot)]

Hello corradoventu,

No no, this should be fixed for 24.04. But the fix landed on https://github.com/canonical/ubuntu-desktop-provision and not https://github.com/canonical/subiquity .

It seems a new snap was promoted yesterday so the new daily should have the fix hopefully.

Thanks,
Olivier

[corrado venturini (corradoventu)]

Problem solved for me with ISO Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240418)

[Sa Mo (samopedia)]

Testing daily-live ISO from 2024-04-17 15:21

Selecting Swedish keyboard during the install works now.

Thank you all for your hard work

[Sa Mo (samopedia)]

@corradoventu
The last beta iso in https://releases.ubuntu.com/24.04/ubuntu-24.04-beta-desktop-amd64.iso
is from 2024-04-10 20:10

Did you mean this ISO or is there a newer beta?
noble-desktop-amd64.iso 2024-04-18 06:12

[corrado venturini (corradoventu)]

After the beta you have the daily: https://cdimages.ubuntu.com/daily-live/pending/

[Sa Mo (samopedia)]

I thought so ;)

The ISO that is called "beta" and was published on distrowatch.com as first "beta" is from 2024-04-10.

Until RC1 we continue testing from either:
https://cdimage.ubuntu.com/ubuntu/daily-live/current/noble-desktop-amd64.iso which has passed autotest
or
https://cdimage.ubuntu.com/ubuntu/daily-live/pending/noble-desktop-amd64.iso awaiting autotest (or might be the same as the one passed autotest)

So calling the latest ISO from /pending as "beta" makes me confused ;)