[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1117928: locales: transient fallback to C.UTF-8 causes locale warnings even when en_US.UTF-8 is generated



Hi,

On 2025-10-12 17:37, Peter Banik wrote:
> Package: locales
> Version: 2.39-1
> Severity: normal
> Tags: upstream
>  
> 3. SSH in or run some `apt upgrade` or `dpkg` ⇒ observe locale warnings about fallback to `C.UTF-8`.

Could you please actually provide error message from you apt upgrade 
commands?
  
> **Expected Behavior:**
> Once `en_US.UTF-8` is generated and configured, subsystems should uniformly use it, with no fallback warnings or temporary use of `C.UTF-8`.

I am not able to reproduce this issue, the expected behavior is the one 
I observe here.
  
> **Actual Behavior:**
> Early in the boot, glibc (or subsystems) temporarily fall back to `C.UTF-8`, causing warnings even though the correct locale is already configured.

Could you also please provide the error message that you are seeing 
during boot?

> When connecting to the host via SSH:
> -bash: warning: setlocale: LC_CTYPE: cannot change locale (UTF-8): No such file or directory

This error message doesn't correspond what you describe. It seems that 
LC_CTYPE (or LC_ALL) is set to UTF-8, not en_US.UTF-8. Are you sure your 
ssh client is asking for the en_US.UTF-8 locale?

Regards
Aurelien 

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                     http://aurel32.net


Reply to: