Hi all,
Recently I bought a RPI 5 for my kid to have a mini PC ( and for me, for a few experiments).
I did not use a SD card to install the os, but I booted with from USB atick and then called the RPI image installer, to download the image and install it directly to a SSD.
Unfortunately I encountered the 'stuck GB keyboard layout' for my kid account ( not mine). The weirdest beeing, when I su myself within my kid terminal, I have the same issue.
I checked many solutions, nothing worked (even adding his account in the sudoers groups, which I did not want).
On the GitHub of the rpi-imager, my understanding is that issue is fixed for a further version. But there is no indication on how to fix the current one.
So I guess the 'easy' way to fix this is to reinstall the OS, not using the rpi-imager for a network install. What do you think?
If it is the case, is it possible to install the OS without a SD card?
Many thanks,
Nolwenn
Recently I bought a RPI 5 for my kid to have a mini PC ( and for me, for a few experiments).
I did not use a SD card to install the os, but I booted with from USB atick and then called the RPI image installer, to download the image and install it directly to a SSD.
Unfortunately I encountered the 'stuck GB keyboard layout' for my kid account ( not mine). The weirdest beeing, when I su myself within my kid terminal, I have the same issue.
I checked many solutions, nothing worked (even adding his account in the sudoers groups, which I did not want).
On the GitHub of the rpi-imager, my understanding is that issue is fixed for a further version. But there is no indication on how to fix the current one.
So I guess the 'easy' way to fix this is to reinstall the OS, not using the rpi-imager for a network install. What do you think?
If it is the case, is it possible to install the OS without a SD card?
Many thanks,
Nolwenn
Statistics: Posted by Nolwenn — Sun Aug 24, 2025 6:19 pm