plymouth should warn when caps lock is set with "ask-for-password" command

[Claudio Moretti]

Binary package hint: plymouth

If one inadvertently presses the "Caps Lock" button and tries to enter his password, cryptsetup does not (obviously) accept it, but the user is not aware he's trying to enter a password that's different from his real one.

I flagged it as a plymouth bug, as it is responsible for cryptsetup user interface.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: plymouth 0.8.2-2ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-9.14-generic 2.6.35-rc5
Uname: Linux 2.6.35-9-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Fri Jul 23 00:37:32 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
MachineType: Dell Inc. Vostro 1500
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-9-generic root=/dev/mapper/sda6_crypt ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=it_IT.utf8
 SHELL=/bin/bash
ProcFB:
 0 VESA VGA
 1 VGA16 VGA
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
dmi.bios.date: 04/21/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0WY040
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd04/21/2008:svnDellInc.:pnVostro1500:pvr:rvnDellInc.:rn0WY040:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Vostro 1500
dmi.sys.vendor: Dell Inc.

[Dimitri John Ledkov (xnox)]

How can one query the status of capslock from console which works in UTF-8 and non-UTF-8 locales that may or may not use ShiftLock/CapsLock?

[Margarita Manterola (marga-9)]

Something important to notice is that not even the caps lock key light is turned on while plymouth is in charge of the screen.

[Margarita Manterola (marga-9)]

BTW, this is still the case on Trusty with the latest plymouth version (0.8.8-0ubuntu17.1)

[Margarita Manterola (marga-9)]

This was also reported to plymouth in Fedora [1], but it got no attention there and the bug was closed as a result of Fedora 20 reaching EOL.
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=1053167