On 02/23/2011 01:54 PM, Anton Zinoviev wrote:
On Wed, Feb 23, 2011 at 01:16:01PM +0100, Eric Valette wrote:
I did a copy of the new ckbcomp to /usr/bin/ and then dpkg-reconfigure
keyboard-configuration. Rebooted. Problem seems to be gone.
Note: all machine that have the problem are 64 bits machine.
I don't know about the problem with console-data, but the change of
ckbcomp is not related to the bits. The experimental version of
xkb-data uses _ (underscore) in some names and console-setup didn't
allow this because there wasn't any formal description of the files in
/usr/share/X11/xkb and I didn't know _ was permited. Simple changes
like the following fixed the problem:
- if ($pattern =~ /^\$([a-zA-Z0-9]+)$/) {
+ if ($pattern =~ /^\$([a-zA-Z0-9_]+)$/) {
The problem has been reported to console-data because prior to the new
console-setup src package (that provides keyboard-configuration), the
package console-data was the one used to reconfigure the keyboard via
dpkg-reconfigure .
We all agree that this bug may have been reported to the wrong package
and should be moved to keyboard-configuration at least as using the
dpkg-reconfigure on keyboard-configuration as suggested does not fix the
problem an exibit the bug for this package (or at least one of
console-setup src package).
I just wonder why the upgrade did not remove console-data but that's
another story.
Thanks for your support.
I will test at home and report anyway.
-- eric
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
