Search Issue Tracker
Fixed
Fixed in 6000.0.32f1, 6000.1.0a8, 7000.0.0a7
Votes
7
Found in
6000.0.7f1
6000.1.0a7
Issue ID
UUM-74127
Regression
Yes
[Linux] AutoLocale: current locale expects 'C' but got error is thrown when starting a project
*Steps to reproduce:*
1. Create a new URP 3D template project
2. Open the Console window
*Actual results:* AutoLocale: current locale expects 'C' but got 'lt_LT.UTF-8' error is thrown
*Expected results:* AutoLocale does not produce any errors on Project launch
*Reproducible with versions:* 6000.0.7f1
*Not reproducible with versions:* 2021.3.39f1, 2022.3.34f1, 2023.2.20f1, 6000.0.6f1
*Reproducible* *on (OS):* Ubuntu 20, Ubuntu 22, Ubuntu 24
*Not reproducible* *on (OS):* macOS 14.5
Comments (6)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assembly definition "Any Platform" checkbox is useless and does not follow nested checkbox rules
- Input from the "Backslash" key is not detected in the Web Player when using the Japanese 106/109 key keyboard
- High "Total" value of the "TerrainManager.CullAllTerrains" when generating terrain
- UI Layout rebuild triggered by a rounding error when using TextMesh Pro
- Sprite Shape Corners and Edges are invisible when a closed Sprite Shape is used
Tumbleweed64
Jan 25, 2025 00:45
I'm on Unity 6000.0.23f1 on Linux Mint and this issue is still not resolved. It isn't a warning as it once was but every time I start up the editor it appears.
CrogUk
Nov 15, 2024 13:48
Hi. The locale not conforming to the C standard (ISO C says that all programs start by default in the standard ‘C’ locale) which seems to be a linux specific issue on some users systems.
The assert and now log was added to determine the prevelance of the issue, it being recorded in the editor.log shouldn't affect your work. If you experience a bug/crash please report it and this extra information will be present and may aid us in resolving your issue faster.
We appreciate your feedback, and please provide details if you have any concerns.
ElryDev
Nov 14, 2024 10:45
How is this still not fixed ? Marking it as a log IS NOT A FIX
MostHated
Oct 05, 2024 00:41
That's the thing, though. Why/where is it set that it's expecting that? It's not like I don't have one set. It just doesn't like the one I have. So if it's 'auto', shouldn't it just detect and use what I have set? If not, it's not very 'auto'. How can I get rid of the message in general?
zsh ❯ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8
pulzefx
Jul 31, 2024 13:01
This is not fixed or a regression in 0.12f1
huulong
Jul 31, 2024 11:56
Looks like it's now a log, instead of a warning (tested on 6000.0.12f1). But I'd like to now how to completely remove it (although it's ok as it only appears once after startup). I mean, you can *expect* the user to run Unity on a machine with some locale, after all.