Bug 1817229

Summary:	Crypt password input in US, after default layout changed.
Product:	[Fedora] Fedora	Reporter:	jtagcat <redhat>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	32	CC:	anaconda-maint-list, jkonecny, jonathan, kellin, vanmeeuwen+fedora, vponcova, wwoods
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-26 08:21:26 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 jtagcat 2020-03-25 21:07:27 UTC

Description of problem:

Anacoda doesn't change keyboard layout for encrypting the drive. This could result in setting a password unknowingly with US layout and after reboot, fail to decrypt the drive (while using the chosen layout).

Version-Release number of selected component (if applicable): (downloaded iso around 20:00 UTC Mar 24)


How reproducible: 100%

Steps to Reproduce:
1. Start installer
2. Switch main keyboard layout
(kb layout displayed in the top right corner changes to the chosen one)
3. Disks setup -> Check 'Encrypt my data'
4. Click done, dialog asking for a new password

Actual results:
5. (kb layout displayed here is the chosen one) Trying to type a password I recognized, that it was still the US layout.

Expected results:
5. Keyboard layout actually changes to the chosen default one while in the live session, as the 2 indicators (top right and next to the passwd input) indicate.

Additional info:
A workaround is to go to the live session's gnome-settings and change the keyboard layout from there as well.

Comment 1 Jiri Konecny 2020-03-26 08:21:26 UTC

Keyboard switching in Live environment does not work. That is known issue and unfortunately not that trivial to fix.

We are sorry for inconveniences.

*** This bug has been marked as a duplicate of bug 1389959 ***