Bug 20250

Summary: On LUKS password entry backspace is handled as a character
Product: Mageia Reporter: Tamás Hajdu <fathom>
Component: RPM PackagesAssignee: Base system maintainers <basesystem>
Status: NEW --- QA Contact:
Severity: normal    
Priority: Normal CC: marja11, thierry.vignaud
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard: MGA6TOO
Source RPM: cryptsetup CVE:
Status comment:

Description Tamás Hajdu 2017-02-06 21:57:41 CET
Description of problem:
On LUKS encryption, on boot when it asks for a password, the backspace is not working as supposed, it produces a character instead.

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


How reproducible:
always

Steps to Reproduce:
1. encrypt root
2. boot up
3. try to use backspace on password entry.
Comment 1 Marja Van Waes 2017-02-10 18:17:50 CET
I've seen this, too, both when booting with "splash quiet" and when booting with verbose splash.

Tamás said on IRC that backspace works as expected in other Linux distributions.

Btw, behaviour is the same when opening & mounting a still closed LUKS encrypted partition from a VT. However there's nothing indicating then how many characters have been entered. 
The same is true when trying to log in in a VT: the user's password must be typed correctly, using backspace to delete a wrong character, and then typing the correct character, never leads to the password being accepted.

The only time I've opened an encrypted partition under X, with dolphin, backspace did work.

Wildly guessing it's something low level that decides that backspace cannot be used for passwords and the like during boot-up and in VTs, so assigning to the base system maintainers.

Please reassign if I'm wrong.

CC: (none) => marja11
Assignee: bugsquad => basesystem

Comment 2 Marja Van Waes 2017-08-27 21:19:09 CEST
*** Bug 21612 has been marked as a duplicate of this bug. ***
Marja Van Waes 2017-08-27 21:19:21 CEST

Whiteboard: (none) => MGA6TOO

Comment 3 Tamás Hajdu 2017-08-29 17:29:36 CEST
I have compared the dracut config on mageia and fedora. On fedora by default there is no config at all. In mageia there are some settings added, also it refers to the file /etc/sysconfic/keyboard. In my case these are set:

/etc/dracut.conf.d/50-mageia.conf:
# Configuration for 10i18n module. See /usr/share/dracut/10i18n/README
i18n_vars="/etc/sysconfig/i18n:SYSFONT-FONT,SYSFONTACM-FONT_MAP,UNIMAP-FONT_UNIMAP,LANG,LC_ALL /etc/sysconfig/keyboard:KEYTABLE,KEYMAP,GRP_TOGGLE"

# build initrd only to boot current hardware
hostonly="yes"

# always include ahci driver (mga#4364)
add_drivers+=" ahci "

# Do not include the network module by default which saves about 10megs
# Users can still generate a network friendly initrd by editing this file
# or overriding omit_dracutmodules from another config file
omit_dracutmodules+=" network systemd "

/etc/sysconfig/keyboard:
KEYBOARD=hu
KEYTABLE=hu-latin2
XkbLayout=hu
XkbModel=pc105
XkbOptions=compose:rwin

I haven't yet tried to use different keyboard layout, maybe that (on the fedora I have tried the owner prefers English layout).
Thierry Vignaud 2020-05-02 13:49:28 CEST

CC: (none) => thierry.vignaud
Source RPM: (none) => cryptsetup