After upgrade to bookworm: Keyboard layout

[Hans]

Dear list,

there is a little problem, I am trying to fix.

After upgrade to bookworm the keyboard layout has changed from German to US
(de to us).

I tried debian-reconfigure keyboard-configuration without success, also
deinstalled and reinstalled both without success.

Doing "loadkeys de" is working, but after reboot it is English again.

So I guessed, it is a initramfs issue and tried "setupcon -f -k" and "update-
initramfs -u" - also no success.

Also checked /etc/default/keyboard, the entry is correct (pc-105, de).

Some thing I noticed at bootup: When the kernel is started (or before kernel
starts), I get a message like "/etc/console-setup/cached-utf8.tmp not
correct", however, this message was seen before on bullseye, where everything
was ok.

I suppose, something went wrong during upgrade, or during upgrade I missed
something (as I am running an old NVidia card with unsupported driver by
bookworm) as during upgrade phase the screen went crippy.

Any more ideas, how it get be fixed? Of course I could enter the command
"loadkeys de" as the last line of the startup scripts, but this solution is
not satisfying me.

Thanks for reading it and any help.

Best regards

Hans

[Hans]

Am Mittwoch, 24. Mai 2023, 17:20:26 CEST schrieb Pierre Tomon:
> Le Wed, 24 May 2023 16:53:09 +0200,
>
> Hans <hans.u...@loop.de> a écrit :

> > I tried debian-reconfigure keyboard-configuration without success,
> > also deinstalled and reinstalled both without success.
>

> Try:
> dpkg-reconfigure keyboard-configuration
> dpkg-reconfigure console-setup

Tried before, but no success.

Thanks anyway.

Best

Hans

[Pierre Tomon]

Le Wed, 24 May 2023 16:53:09 +0200,
Hans <hans.u...@loop.de> a écrit :

> I tried debian-reconfigure keyboard-configuration without success,
> also deinstalled and reinstalled both without success.

[Cindy Sue Causey]

On 5/24/23, Hans <hans.u...@loop.de> wrote:
> Dear list,
>
> there is a little problem, I am trying to fix.
>
> After upgrade to bookworm the keyboard layout has changed from German to US
>
> (de to us).
>

< snipped for relevance >

>
> Some thing I noticed at bootup: When the kernel is started (or before kernel
>
> starts), I get a message like "/etc/console-setup/cached-utf8.tmp not
> correct", however, this message was seen before on bullseye, where
> everything
> was ok.

Hi, Hans.. Have you tried renaming cached-utf8.tmp to move it out of
the way to see if the system creates a new one? I rename the "." to
"DOT" when I do that. Other times I'll move my problem files to a
completely new, relatively "safe" directory, e.g. ~/Documents.

The problem with changing that name is it might make the keyboard
instantly useless. If you have the option to do so, maybe playing in
either chroot or a virtual machine is best just in case that file does
a lot despite its harmless looking "tmp" name there.

My setup doesn't have that cached-utf8.tmp file. Does it contain
anything that would be worth sharing in your thread here?

If this was happening to me, I'd go the full reboot after the file
name change just to be confident the kernel was basically in full
control.

Hoping there's an easy solve. You all have already touched on my
favorites, those two "dpkg-reconfigure" ones.

Cindy :)
--
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

[Hans]

Hi Cindy,

> Hi, Hans.. Have you tried renaming cached-utf8.tmp to move it out of
> the way to see if the system creates a new one? I rename the "." to
> "DOT" when I do that. Other times I'll move my problem files to a
> completely new, relatively "safe" directory, e.g. ~/Documents.

Yes, removed - no success.

>
> The problem with changing that name is it might make the keyboard
> instantly useless. If you have the option to do so, maybe playing in
> either chroot or a virtual machine is best just in case that file does
> a lot despite its harmless looking "tmp" name there.
>
> My setup doesn't have that cached-utf8.tmp file. Does it contain
> anything that would be worth sharing in your thread here?
>

No it doesn't.

> If this was happening to me, I'd go the full reboot after the file
> name change just to be confident the kernel was basically in full
> control.
>
> Hoping there's an easy solve. You all have already touched on my
> favorites, those two "dpkg-reconfigure" ones.
>
> Cindy :)

Best

Hans

[Pierre Tomon]

Le Wed, 24 May 2023 17:28:09 +0200,
Hans <hans.u...@loop.de> a écrit :

> Tried before, but no success.

Try this to see if it reports or apply something:
systemctl status keyboard-setup
systemctl restart keyboard-setup

[Michel Verdier]

Le 24 mai 2023 Hans a écrit :

>> > I tried debian-reconfigure keyboard-configuration without success,
>> > also deinstalled and reinstalled both without success.
>>
>> Try:
>> dpkg-reconfigure keyboard-configuration
>> dpkg-reconfigure console-setup
>
> Tried before, but no success.

Can you give us
cat /etc/default/locale
grep -v '#' /etc/locale.gen

[Hans]

I am answering myself. Surprisingly the error is gone. But I do not know why!


These were my last actions:

In my despair I added the repo of bullseye to the sources.list and downgraded

console-setup
console-setup-linux
keyboard-configuration

Those must be all together downgraded. After downloading and install I got a
correct keyboard layout, but after reboot it was still back to "us".

However, I then did "setupcon -k -f" , but got no success.

Then I did "loadkeys de" to get the correct keyboard layout and tried
"setupcon -k -f" again. After reboot it shows no success again.

As these was no success at all, I upgraded the above packages again to
bookworm and rebootet - still keyboard is "us".

But today, after I read the hint "try keyboard-setup.sh" and started my
system, the keyboard layout was ok!

NOTE: I did NOT excute "keyboard-setup.sh", as things were ok!!!

Doi not ask me why, maybe some dwarfs or some goblins did the job - do not
know.

Sadly I have nothing learned with this issue, but I am happy it is working
now.

Thanks for all the help!

Best regards

Hans

[Vincent Lefevre]

On 2023-05-26 11:59:06 +0200, Hans wrote:
[...]

> But today, after I read the hint "try keyboard-setup.sh" and started my
> system, the keyboard layout was ok!
>
> NOTE: I did NOT excute "keyboard-setup.sh", as things were ok!!!
>
> Doi not ask me why, maybe some dwarfs or some goblins did the job - do not
> know.

You should look at the logs whether the messages are the same. In
the past, after wakeup, my laptop keyboard was sometimes seen as
"HID 413c:8157" and the mapping was correct, but most of the time,
it was seen as "AT Translated Set 2 keyboard" and the mapping was
incorrect.

--
Vincent Lefèvre <vin...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

[Jörg-Volker Peetz]

Could you show us the content of your /etc/default/keyboard ?
Regards,
Jörg.

[Hans]

Am Samstag, 27. Mai 2023, 13:26:04 CEST schrieb Jörg-Volker Peetz:

Hi Jörg,

yes, of course, but I guess, it does not content any usefull information, because I checked it before at the time the issue was active.

There is no differnce to the actual state.

But anyway, here it is:

---- snip ----

# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL="acer_laptop"
XKBLAYOUT="de"
XKBVARIANT="nodeadkeys"
XKBOPTIONS="terminate:ctrl_alt_bksp"

BACKSPACE="guess"

--- snap ---

The entry "acer_laptop" worked always well, but I also tried "pc-105" during the time of the issue, which also did NOT work.

Best regards

Hans

[Michel Verdier]

Le 27 mai 2023 Hans a écrit :

> The entry "acer_laptop" worked always well, but I also tried "pc-105" during the time of the
> issue, which also did NOT work.

it's "pc105", but that don't change anything