Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2121110 - GNOME Initial Setup uses the English keyboard, instead of the default keyboard
Summary: GNOME Initial Setup uses the English keyboard, instead of the default keyboard
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 37
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: AcceptedFreezeException AcceptedBlocker
Depends On:
Blocks: F37BetaFreezeException F37FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2022-08-24 13:39 UTC by Kamil Páral
Modified: 2022-09-25 00:17 UTC (History)
15 users (show)

Fixed In Version: gnome-shell-43~rc-3.fc37 gnome-shell-43.0-2.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-25 00:17:58 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-shell issues 5873 0 None opened GNOME Initial Setup uses the English keyboard, instead of the default keyboard 2022-09-21 06:31:04 UTC

Description Kamil Páral 2022-08-24 13:39:14 UTC
Description of problem:
Please see this upstream report:
https://gitlab.gnome.org/GNOME/gnome-initial-setup/-/issues/151

How reproducible:
always

Comment 1 Kamil Páral 2022-08-24 13:40:32 UTC
Proposing as a Final blocker:

> If a particular keyboard layout has been configured for the system, that keyboard layout must be used:
>    In the "initial setup" utility (if applicable)

https://fedoraproject.org/wiki/Fedora_37_Final_Release_Criteria#Keyboard_layout_configuration

Comment 2 Geoffrey Marr 2022-08-29 21:36:11 UTC
Discussed during the 2022-08-29 blocker review meeting: [0]

The decision to classify this bug as both an "AcceptedBlocker (Final)" and an "AcceptedFreezeException (Final)" was made as it's a clear violation of the Final criteria, and since it affects the install process so can't be fixed with an update and would be annoying for non-US English 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

Comment 3 Geoffrey Marr 2022-08-29 21:39:02 UTC
Edit to comment 2: "AcceptedFreezeException (Beta)"

Comment 4 Kalev Lember 2022-09-13 13:31:09 UTC
Looks like this is an issue with gnome-shell getting the keyboard layout somehow wrong during the initial setup session. Not really sure what's going on here, but pretty sure it's not an issue with gnome-initial-setup itself at least.

Comment 5 Carlos Garnacho 2022-09-14 19:00:35 UTC
There's FTR a fix at https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2487.

Comment 6 Kalev Lember 2022-09-15 15:54:38 UTC
Thanks Carlos! I went ahead and backported that in https://src.fedoraproject.org/rpms/gnome-shell/c/8c7cf467da8b4ba5fbfece71e971beeda18af4fc?branch=f37

Comment 7 Fedora Update System 2022-09-15 20:22:04 UTC
FEDORA-2022-52cdfc7920 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-52cdfc7920

Comment 8 Fedora Update System 2022-09-16 02:01:10 UTC
FEDORA-2022-52cdfc7920 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-52cdfc7920`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-52cdfc7920

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Kamil Páral 2022-09-16 11:19:22 UTC
Hmm, it doesn't seem to work for me. I took F37 Workstation Live Beta, installed it, then rebooted into the rescue environment available from Server DVD, updated gnome-shell, and rebooted into the system. The initial setup still selected US keymap by default, even though the default keymap was CZ. The user then had CZ by default in his session.

Quite interestingly, if I create another user and log in, the second user has also US keymap selected, even though CZ is still marked as default in Settings. Probably the same bug, and probably not fixed.

Comment 10 Fedora Update System 2022-09-21 01:40:28 UTC
FEDORA-2022-52cdfc7920 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Kamil Páral 2022-09-21 12:05:08 UTC
There's a new MR and I confirmed that it fixes this problem:
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2495

Comment 12 Fedora Update System 2022-09-22 10:59:04 UTC
FEDORA-2022-b14944cb83 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-b14944cb83

Comment 13 Kamil Páral 2022-09-22 12:39:04 UTC
(In reply to Fedora Update System from comment #12)
> FEDORA-2022-b14944cb83 has been submitted as an update to Fedora 37.
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-b14944cb83

Fixes the problem, thanks.

Comment 14 Fedora Update System 2022-09-23 01:48:53 UTC
FEDORA-2022-b14944cb83 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-b14944cb83`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-b14944cb83

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 15 Fedora Update System 2022-09-25 00:17:58 UTC
FEDORA-2022-b14944cb83 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.