[pkg-cryptsetup-devel] Bug#903641: Preserve numlock state during cryptdisk boot password prompt in plymouth

[Pascal Vibet - ADACIS]

Hi,

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. 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||.

But you are right, 'setleds'  is not the goods choice to keep numlock state.
I will search a better program.

Regards

Le 12/07/2018 à 15:48, Guilhem Moulin a écrit :
> Control: severity -1 minor
>
> Hi,
>
> On Thu, 12 Jul 2018 at 15:02:20 +0200, Pascal Vibet - ADACIS wrote:
>> So, i apply modifications like this:
>> in /usr/share/initramfs-tools/hooks/cryptopensc:
>> […]
>> in /usr/share/initramfs-tools/scripts/local-top/cryptopensc:
> 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.
>
>>> INITTY=/dev/tty[1-8]
>>> for tty in $INITTY ; do
>>>      setleds -D +num < $tty
>>> done
> Does that really *preserve* the numlock state?  I'm not familiar with
> setleds(1), but according to the manpage it *sets* numlock and changes
> the default settings.
>
> Cheers,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20180712/4851c4b3/attachment.html>