[pkg-cryptsetup-devel] Cryptsetup

[Thomas Balthazar]

Hi Jonas,

Thanks a lot for your answer.
I noticed that if I revert to an older kernel, the problem doesn't occur
anymore. I posted a message with some details on the kernel
mailing-list, hoping to get some help/advices there :
https://lists.debian.org/debian-kernel/2014/12/msg00356.html

Best,
Thomas.

On 12/27/2014 11:56 AM, Jonas Meurer wrote:
> Hi Thomas,
> 
> Am 26.12.2014 um 23:32 schrieb Thomas Balthazar:
>> Today, after a reboot, I noticed that the cryptsetup password prompt
>> that asks for the password to decrypt my disk was using a Qwerty layout
>> (my password was setup weeks ago with an Azerty layout, and I typed my
>> password at every boot with the Azerty layout successfully, until today).
>>
>> I tried to type my password as if my keyboard was a Qwerty keyboard, and
>> it worked.
>>
>> I see in the apt history log that cryptsetup was updated today on my
>> system (see below), and that's why I'm posting here.
> 
> Nothing in cryptsetup package changed recently that affects the keymap
> handling. More likely is that the cryptsetup upgrade updated your
> initramfs and the keymap configuration changed there for some (unknown)
> reason.
> 
> cryptsetup itself doesn't require/configure/expect any keymap layout. It
> just takes the input as is.
> 
>> My questions :
>> - why cryptsetup is now expecting a Qwerty keyboard?
>> - how can I fix this?
> 
> I would start by looking at the keymap configuration. IIRC, the packages
> kbd and keyboard-configuration are responsible. You should check that
> both packages are installed and try to configure the latter one properly
> by running 'dpkg-reconfigure keyboard-configuration'.
> 
> Cheers,
>  jonas
> 
>>
>> I don't know if I'm posting to the appropriate mailing-list.
>> Any help would be appreciated.
>>
>> Thanks a lot!
>>
>> Best,
>> Thomas.
>>
>>
>> Some system info :
>> ---
>> tail /var/log/apt/history.log :
>> Start-Date: 2014-12-26  15:03:58
>> Upgrade: libefivar0:amd64 (0.15-2, 0.15-3), libsane-common:amd64
>> (1.0.24-4, 1.0.24-7), debconf:amd64 (1.5.54, 1.5.55), libllvm3.5:amd64
>> (3.5-8, 3.5-9), cpio:amd64 (2.11+dfsg-2+b1, 2.11+dfsg-4),
>> cryptsetup-bin:amd64 (1.6.6-3, 1.6.6-4), tzdata-java:amd64 (2014i-1,
>> 2014j-1), ifupdown:amd64 (0.7.50, 0.7.51), libcryptsetup4:amd64
>> (1.6.6-3, 1.6.6-4), debconf-i18n:amd64 (1.5.54, 1.5.55), libsane:amd64
>> (1.0.24-4, 1.0.24-7), efibootmgr:amd64 (0.9.0-2, 0.11.0-3),
>> libhogweed2:amd64 (2.7.1-3+b1, 2.7.1-4), sane-utils:amd64 (1.0.24-4,
>> 1.0.24-7), libjasper1:amd64 (1.900.1-debian1-2.2, 1.900.1-debian1-2.3),
>> libpq-dev:amd64 (9.4~rc1-1, 9.4.0-1), git-man:amd64 (2.1.3-1, 2.1.4-2),
>> git:amd64 (2.1.3-1, 2.1.4-2), fonts-droid:amd64 (4.4.4r2-4, 4.4.4r2-5),
>> libnettle4:amd64 (2.7.1-3+b1, 2.7.1-4), transmission-gtk:amd64
>> (2.84-0.1+b1, 2.84-0.2), cryptsetup:amd64 (1.6.6-3, 1.6.6-4),
>> tzdata:amd64 (2014i-1, 2014j-1), transmission-common:amd64 (2.84-0.1,
>> 2.84-0.2), libpq5:amd64 (9.4~rc1-1, 9.4.0-1)
>> End-Date: 2014-12-26  15:04:25
>> ---
>> uname -a :
>> Linux xxx 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08)
>> x86_64 GNU/Linux
>> ---
>>
>> _______________________________________________
>> pkg-cryptsetup-devel mailing list
>> pkg-cryptsetup-devel at lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-cryptsetup-devel
>>
>