Bug 603744

Summary:	Only the english keyboard layout is supported for opening encrypted root partitions
Product:	[openSUSE] openSUSE 11.3	Reporter:	Tim - <timshel>
Component:	Kernel	Assignee:	Ludwig Nussel <lnussel>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P2 - High	CC:	richard, robert.schwemlein
Version:	Final
Target Milestone:	Final
Hardware:	i686
OS:	openSUSE 11.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Tim - 2010-05-07 13:46:02 UTC

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en; rv:1.9.2) Gecko/20100115 Firefox/3.6

According to the OpenFate entry https://features.opensuse.org/305633 root encryption is integrated with lvm since 11.2 but it only works with an English keyboard layout or a very basic password which is the same on both layouts.

Reproducible: Always

Steps to Reproduce:
Create an encrypted root file system with lvm and use a password which can't be typed the same way on an English keyboard as on a local one.
Actual Results:  
The password can't be entered correctly and in this succession the system not started without knowing the English keyboard layout.

Expected Results:  
The keyboard should be the same as the one selected during installation so typing the password should be no problem.

Basically the local keyboard layout has to be integrated into the initrd during installation.

I can't test it with 11.3 Milestone 6 since it seems to have some installation problems on encrypted root file system.

Comment 1 Tim - 2010-07-01 21:30:54 UTC

Still an issue in current 11.3 .

Comment 2 Robert Schwemlein 2010-09-22 16:19:54 UTC

I can confirm this bug for final 11.3

Comment 3 Jeff Mahoney 2010-09-22 20:28:20 UTC

This isn't a kernel issue. mkinitrd, perhaps. Michal, can you take a look and if it's not just kick it back for screening?

Comment 4 Michal Marek 2011-03-14 21:24:40 UTC

Custom keyboard layouts in the initrd are not implemented, that's not a bug, but a lack of a feature.

Comment 5 Michal Marek 2011-03-14 21:25:16 UTC

*** Bug 640913 has been marked as a duplicate of this bug. ***

Comment 6 Ludwig Nussel 2011-03-15 08:33:01 UTC

Exactly. The smarty-pants already want to get rid of mkinitrd and switch to something else so I'm not going to waste time here again just to find out that the code gets disabled short before release.