It does take a *long* time to run, maybe you weren't patient enough.
I just tried it on my (only) Pi 4:-
root@pimedia:~# vi /etc/locale.gen
root@pimedia:~# locale-gen
Generating locales (this might take a while)...
en_GB.UTF-8... done
en_US.UTF-8... done
Generation complete.
root@pimedia:~#
It took a fairly long time, maybe 30 seconds or more.
I've got 8 Pis running. 7 of them SSH or SCP to the other one at
various times. One of them (pi5) is now running Bullseye, and seems to
have the locale set to en_US.UTF8, whereas the other 7 are on older OS versions and have the locale set to en_GB.UTF-8.
When I try to SSH from pi5 to any of the others, I get :
-bash: warning setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
I've tried using locale-gen to change the default on pi5 to the en_GB version, but it seems to hang.
pile of error messages ending "No such file or directory"
Altering $HOME/.profile and adding :
LANG=en_GB.UTF-8
seems to work, to the extend that echo $LANG now gives me the right
value, but the SSH still gives me the same error.
Running locale gives me :
locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or
directory
locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_GB.UTF8
but all other entries are en_US.UTF-8
So what to try next ?
Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.
So what to try next ?
In message <393fdj-dge62.ln1@esprimo.zbmc.eu>, Chris Green <cl@isbd.net> writes
It does take a *long* time to run, maybe you weren't patient enough.
I just tried it on my (only) Pi 4:-
  root@pimedia:~# vi /etc/locale.gen
  root@pimedia:~# locale-gen
  Generating locales (this might take a while)...
    en_GB.UTF-8... done
    en_US.UTF-8... done
    Generation complete.
  root@pimedia:~#
It took a fairly long time, maybe 30 seconds or more.
Thanks. I know a Pi 3 is a bit slower than a Pi 4, but this was still running after ~10 minutes when I killed it. I'll try it again with the
time command, and see what it comes up with. I doubt it makes any difference, but I was running it via sudo rather than from root.
<goes off to play on pi5>
OK, having had another look, what I'd run, that I ended up Crtl-Cing was locale-gen en_GB.UTF-8. Running what you did, it took 20 seconds, but didn't make any difference to the locale settings.
For your reference, records indicate that
Adrian <bulleid@ku.gro.lioff> wrote:
So what to try next ?
dpkg-reconfigure locales
If I had to guess, I would say this is due to missing locale files as
both raspi-config and locale are complaining about "No such file or >directory". I would check the folder where your locale definitions are
stored (on my system /usr/lib/locale) for the en_GB.UTF-8 locale
definition. If it isn't there, that could be your problem.
And that is it. So where have the others gone ?
Adrian <bulleid@ku.gro.lioff> writes:
And that is it. So where have the others gone ?
Looks like they might be in 'locale-archive', possibly compressed. If
so, you should just be able to decompress them, copy them out of >'locale-archive', and reconfigure your locale settings.
(*) Who decided that it was a good idea to separate the year from the
day and month, with the time and timezone in between? It makes no more
sense for UK DD MMM YYYY format than it does for US MMM DD YYYY format.
For countries that use YYYY-MMM-DD format, I wonder how "date" listed it
- maybe "Sun 2023 21:33:49 GMT 5 Mar" ;-)
Having done a bit of research, locale-archive appears to be some sort of >special file. According to 'man localedef' you can list the locales in
said special file and add new locales to it if necessary.
I've got 8 Pis running. 7 of them SSH or SCP to the other one at
various times. One of them (pi5) is now running Bullseye, and seems to
have the locale set to en_US.UTF8, whereas the other 7 are on older OS versions and have the locale set to en_GB.UTF-8.
When I try to SSH from pi5 to any of the others, I get :
-bash: warning setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
I've tried using locale-gen to change the default on pi5 to the en_GB version, but it seems to hang. using raspi-config fails, generating a
pile of error messages ending "No such file or directory"
Altering $HOME/.profile and adding :
LANG=en_GB.UTF-8
seems to work, to the extend that echo $LANG now gives me the right
value, but the SSH still gives me the same error.
Running locale gives me :
locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory LANG=en_GB.UTF8
but all other entries are en_US.UTF-8
So what to try next ?
Adrian
Surely you're supposed to use raspi-config for this.
sudo raspi-config
In message <k6mp0tFc3bmU1@mid.individual.net>, Brian Gregory <void-invalid-dead-dontuse@email.invalid> writes
Surely you're supposed to use raspi-config for this.
sudo raspi-config
I've tried that. I select the locale that I want, and then "OK". It thinks about it for a while, and then comes up with the following in a
grey box :
There was an error running option L1 Locale
                           <Ok>
That was my first option, when that failed, I started exploring the
other options, which whilst failing, at least give some more helpful
error messages.
Adrian
I would say that probably means your Raspberry Pi OS installation has
been customised in some way or is corrupt.
On 06/03/2023 16:32, Charlie Gibbs wrote:
On 2023-03-05, NY <me@privacy.net> wrote:
(*) Who decided that it was a good idea to separate the year from theThe year being tacked onto the end looks like an afterthought.
day and month, with the time and timezone in between? It makes no more
sense for UK DD MMM YYYY format than it does for US MMM DD YYYY format.
For countries that use YYYY-MMM-DD format, I wonder how "date" listed it >>> - maybe "Sun 2023 21:33:49 GMT 5 Mar" ;-)
"Oh, I guess some people do need the year after all..."
I've converted all my stuff to ISO 8601, and preach its virtues
at every opportunity (like now :-).
I certainly use ISO 8601 (YYYY-MM-DD) when including a date in a
filename, so the files sort by name into date order.
And in newsgroup postings which might be seen outside the UK, I tend
to write dates as 06 Mar 2023 rather than 06/03/2023 to avoid any
confusion with June 3 2023 in US format: 6 Mar 2023 is understandable "everywhere" (even in France and Germany which abbreviate Mars or Marz
to Mar) even if American might write it Mar 6 2023.
On 2023-03-05, NY <me@privacy.net> wrote:
(*) Who decided that it was a good idea to separate the year from the
day and month, with the time and timezone in between? It makes no more
sense for UK DD MMM YYYY format than it does for US MMM DD YYYY format.
For countries that use YYYY-MMM-DD format, I wonder how "date" listed it
- maybe "Sun 2023 21:33:49 GMT 5 Mar" ;-)
The year being tacked onto the end looks like an afterthought.
"Oh, I guess some people do need the year after all..."
I've converted all my stuff to ISO 8601, and preach its virtues
at every opportunity (like now :-).
copied (is that the right word)
On 06/03/2023 16:32, Charlie Gibbs wrote:
On 2023-03-05, NY <me@privacy.net> wrote:
(*) Who decided that it was a good idea to separate the year from theThe year being tacked onto the end looks like an afterthought.
day and month, with the time and timezone in between? It makes no more
sense for UK DD MMM YYYY format than it does for US MMM DD YYYY format.
For countries that use YYYY-MMM-DD format, I wonder how "date" listed it >>> - maybe "Sun 2023 21:33:49 GMT 5 Mar" ;-)
"Oh, I guess some people do need the year after all..."
I've converted all my stuff to ISO 8601, and preach its virtues
at every opportunity (like now :-).
I certainly use ISO 8601 (YYYY-MM-DD) when including a date in a
filename, so the files sort by name into date order.
And in newsgroup postings which might be seen outside the UK, I tend
to write dates as 06 Mar 2023 rather than 06/03/2023 to avoid any
confusion with June 3 2023 in US format: 6 Mar 2023 is understandable "everywhere" (even in France and Germany which abbreviate Mars or Marz
to Mar) even if American might write it Mar 6 2023.
Adrian <bulleid@ku.gro.lioff> writes:
copied (is that the right word)
dd'd?
On 06/03/2023 19:10, Adrian wrote:
In message <k6mp0tFc3bmU1@mid.individual.net>, Brian Gregory >><void-invalid-dead-dontuse@email.invalid> writes
Surely you're supposed to use raspi-config for this.I've tried that. I select the locale that I want, and then "OK".
sudo raspi-config
It thinks about it for a while, and then comes up with the following
in a grey box :
There was an error running option L1 Locale
<Ok>
That was my first option, when that failed, I started exploring the
other options, which whilst failing, at least give some more helpful
error messages.
Adrian
I would say that probably means your Raspberry Pi OS installation has
been customised in some way or is corrupt.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 300 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 71:29:04 |
| Calls: | 6,712 |
| Files: | 12,244 |
| Messages: | 5,356,970 |