Bug#903393: [initramfs-tools] update-initramfs -u warns: Unknown X keysym "dead_belowmacron"
Dear Maintainer,
On Debian 9 (with console-setup 1.164) running "sudo update-initramfs
-u" produces:
update-initramfs: Generating /boot/initrd.img-4.9.0-12-amd64
WARNING: Unknown X keysym "dead_belowbreve"
WARNING: Unknown X keysym "dead_belowbreve"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowring"
WARNING: Unknown X keysym "dead_belowring"
WARNING: Unknown X keysym "dead_belowcircumflex"
WARNING: Unknown X keysym "dead_belowcircumflex"
WARNING: Unknown X keysym "dead_greek"
WARNING: Unknown X keysym "dead_greek"
WARNING: Unknown X keysym "dead_greek"
WARNING: Unknown X keysym "dead_greek"
WARNING: Unknown X keysym "dead_belowdiaeresis"
WARNING: Unknown X keysym "dead_belowdiaeresis"
WARNING: Unknown X keysym "dead_belowtilde"
WARNING: Unknown X keysym "dead_belowtilde"
WARNING: Unknown X keysym "dead_belowtilde"
WARNING: Unknown X keysym "dead_belowtilde"
On Debian 10 (with console-setup 1.193~deb10u1) running "sudo
update-initramfs -u" produces:
update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64
This is with my custom XKB keyboard layout where I included the quite a
few "dead_*" X keysyms.
The problem is indeed caused by the Perl script "/usr/bin/ckbcomp" because:
- The script does not support all X keysyms.
- Despite not supporting all X keysyms the supported X keysyms are used
as if the remaining unknown X keysyms are potentially invaild X keysyms.
- On Debian 9 the "/usr/share/initramfs-tools/hooks/keymap" script calls
"/bin/setupcon" via "setupcon --save-keyboard ..." which causes it to
call "/usr/bin/ckbcomp".
- On Debian 10 the "/usr/share/initramfs-tools/hooks/keymap" script
calls "/bin/setupcon" via "setupcon --setup-dir ..." which causes it to
not call "/usr/bin/ckbcomp".
Perhaps the Perl script "/usr/bin/ckbcomp" should be updated to support
all X keysyms or the current supported X keysyms should be used as just
an incomplete whitelist, where the remaining unknown X keysyms are also
potentially vaild keysyms. In other words an info or warning about
unsupported X keysym could be printed only in verbose or debug mode or
not at all.
Regards,
Bakhelit
Reply to: