Control: severity -1 wishlist Control: reassign -1 initramfs-tools-core Control: retitle -1 initramfs-tools-core: 'keymap' scripts don't preserve numlock state
On Thu, 12 Jul 2018 at 19:46:02 +0200, Pascal Vibet - ADACIS wrote: > Le 12/07/2018 à 15:48, Guilhem Moulin a écrit : >> Why only in cryptopensc and not in cryptroot? Also /usr/bin/setleds >> comes from the ‘kbd’ package which cryptsetup-initramfs doesn't depend >> on (it's only a Recommends, not a hard Depends), so `copy_exec` needs to >> wrapped to check for the program's existence. > > Because i don't test with cryptroot. You are, it's the hook that copies the cryptsetup binaries to the initramfs… And /scripts/local-top/cryptroot is run whenever you have encrypted devices that need to be unlocked at initramfs stage (whether or not some of these devices are using ‘keyscript=decrypt_opensct’). > For package depends or Recommends, the > /usr/share/initramfs-tools/hooks/cryptopensc script need > 'dpkg-architecture' program to work and it is in 'dpkg-dev' package||. No need, it's enough to check whether ‘/usr/bin/setleds’ exists, like we're doing for ‘/usr/bin/gpg’ and some other binaries. That being said I don't think restoring the numlock state is the job of cryptsetup's initramfs hook & boot scripts, just like it's not its job to install the right keyboard layout. I'm therefore reassigning this to ‘initramfs-tools-core’, which is the package shipping the keymap hook. > But you are right, 'setleds' is not the goods choice to keep numlock state. > I will search a better program. An option would be to store the state when generating the initramfs image, but that doesn't seem to be exactly what you want. With full disk encryption I don't know where else to store the state at shutdown stage. -- Guilhem.
Description: PGP signature