-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 08/10/2012 17:06, Anton Zinoviev a écrit :
> On Mon, Oct 08, 2012 at 02:59:17PM +0200, Michael Prokop wrote:
>> [Cc-ing Anton as being maintainer of setupcon]
>>
>>> Calling hook keymap
>>> Adding binary /bin/loadkeys
>>> Adding library /lib/libcfont.so.0
>>> Adding library /lib/libctutils.so.0
>>> Adding library /lib/libconsole.so.0
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>>> WARNING: Unknown X keysym "XF86Messenger"
>> [...]
>>
>> This looks like the culprit.
>>
>> Anton, what do you think about this issue?
>
> Unfortunately, no. These warnings should be harmless (X recognises many
> keysyms that can be ignored on the console).
>
> Here is some questionary to the bug reporter that may help us to debug
> the problem:
>
> 1. What is the contents of /etc/default/keyboard?
# If you change any of the following variables and HAL and X are
# configured to use this file, then the changes will become visible to
# X only if HAL is restarted. In Debian you need to run
# /etc/init.d/hal restart
# The following variables describe your keyboard and can have the same
# values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
# in /etc/X11/xorg.conf.
XKBMODEL="microsoftmult"
XKBLAYOUT="fr"
XKBVARIANT="oss"
XKBOPTIONS="compose:lwin,terminate:ctrl_alt_bksp"
>
> 2. Is the file /etc/default/keyboard correct? Can the symbols of the
> password be typed properly on the text console after the system has
> booted completely?
Everything is fine whent booted.
The system asks for the passphrase.
Then it gives up (because of the "wrong" passphrase.
Then the system asks to press ENTER to continue the boot process.
It asks then again the passphrase.
When I enter the passphrase, it boots normally.
>
> 3. Does the password contain some non-ASCII symbols?
Ascii both uppercase and lowercase and semi-columns (";")
>
> 4. Does your keymap layout contain dead symbols or other "surprises"?
It is a French keymap (basically azerty) so it has dead keys but not
used for the password. An other features on the upper row is that
numéric keys are shifted (the opposite of us keyboards)
> 5. I suppose the initrd-image can be extracted in the following way:
>
> mkdir /tmp/i
> cd /tmp/i
> zcat /boot/_initrd_image_ | cpio -i
>
> Please send us the file /tmp/i/etc/boottime.kmap.gz
Attached
Thanks
Jean-Luc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFQcvuyUdGGXzzGnNARAgWQAJwMCmW0btZNGz4TEvMbNR919ZFDpwCfeKmy
FCJot1NDiCdNpAPLG2+7Rg4=
=glwf
-----END PGP SIGNATURE-----
Attachment:
boottime.kmap.gz
Description: GNU Zip compressed data