ask-for-password does not allow to toggle num-lock state

Bug #1974461 reported by lirel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
New
Low
Unassigned

Bug Description

(low prio inconvenience)

The pinentry field for my cryptsetup luks encrypted disk won't allow to toggle the num lock state during boot.
When pressing the num-lock key on my usb keyboard, the according LED won't light up during entering my cryptsetup password.
plymouthd seems to capture all key presses of my keyboard instead of registering for input events.

the following line seems to tell plymouthd to ask for the password during boot:
/lib/cryptsetup/scripts/decrypt_opensc:41: --pin "$(plymouth ask-for-password --prompt "Enter pin for $CRYPTTAB_NAME: ")"

It would be better for the pinentry to behave more like a normal "read" command but without compromising security.

I am using cryptsetup 2.4.3 fwiw.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: plymouth 0.9.5+git20211018-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri May 20 17:22:25 2022
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
InstallationDate: Installed on 2022-04-14 (36 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: Micro-Star International Co., Ltd. MS-7B79
ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/10/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.K5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X470 GAMING PLUS (MS-7B79)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.K5:bd01/10/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B79:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPLUS(MS-7B79):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B79
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

Revision history for this message
lirel (m8r-lcodw5) wrote :
Changed in plymouth (Ubuntu):
importance: Undecided → Low
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, that's an upstream issue to report on https://gitlab.freedesktop.org/plymouth/plymouth/-/issues

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.