Bug 1957055

Summary:	User setup uses ircorrect keyboard
Product:	[Fedora] Fedora	Reporter:	Seth Kenlon <skenlon>
Component:	gnome-initial-setup	Assignee:	Rui Matos <tiagomatos>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	34	CC:	anaconda-maint-list, gnome-sig, jonathan, jstpierr, kellin, klaatu, tiagomatos, vanmeeuwen+fedora, vponcova, w
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-08 00:58:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Seth Kenlon 2021-05-04 23:16:07 UTC

Description of problem:
After choosing Dvorak keyboard layout during installation of Fedora Silverblue 34, the user setup uses the standard US keyboard layout.

Version-Release number of selected component (if applicable):
34 Silverblue

How reproducible:
100%

Steps to Reproduce:
1. Boot to Fedora Workstation install media.
2. Choose English (Dvorak) as input method (promote it to the top of the list to set it as default)
3. Install Fedora Silverblue to harddrive
4. Reboot upon success
5. Once booted, you're greeted with a user setup window, where you click through choices such as "Use location services" and "Connect online accounts" and then "User setup". 

Actual results:
User setup uses US Keyboard


Expected results:
User setup should use the keyboard layout I set as default during install.

Additional info:
The User Setup window is the only component using US Keyboard. After I've completed it and started using Gnome, the keyboard layout is correct.

Comment 1 Vendula Poncova 2022-04-21 11:08:42 UTC

Reassigning to the GNOME Initial Setup.

Comment 2 Ben Cotton 2022-05-12 16:39:00 UTC

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ben Cotton 2022-06-08 00:58:55 UTC

Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 klaatu 2022-06-08 02:40:47 UTC

This should be closed as FIXED.

I don't know who fixed it, but I just tested this on Fedora Silverblue VERSION="36.1.5 (Silverblue)" and can no longer reproduce.