Bug 1718785
| Summary: | Failed to set locale, defaulting to C.UTF-8 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Lukas Slebodnik <lslebodn> |
| Component: | glibc | Assignee: | Carlos O'Donell <codonell> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | aoliva, arjun, codonell, dj, fweimer, law, mfabian, pfrankli, rth, siddhesh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-10 11:53:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Lukas Slebodnik
2019-06-10 08:20:43 UTC
sh# rpm -qa | grep lang | sort clang-8.0.0-2.fc31.x86_64 clang-analyzer-8.0.0-2.fc31.noarch clang-libs-8.0.0-2.fc31.x86_64 glibc-all-langpacks-2.29.9000-24.fc31.x86_64 liblangtag-0.6.2-7.fc30.x86_64 liblangtag-data-0.6.2-7.fc30.noarch libreoffice-langpack-en-6.2.3.2-5.fc31.x86_64 slang-2.3.2-5.fc30.x86_64 And there is another issue with utf8 locale sh-5.0$ locale LANG=C.utf8 LC_CTYPE="C.utf8" LC_NUMERIC="C.utf8" LC_TIME="C.utf8" LC_COLLATE="C.utf8" LC_MONETARY="C.utf8" LC_MESSAGES="C.utf8" LC_PAPER="C.utf8" LC_NAME="C.utf8" LC_ADDRESS="C.utf8" LC_TELEPHONE="C.utf8" LC_MEASUREMENT="C.utf8" LC_IDENTIFICATION="C.utf8" LC_ALL=C.utf8 sh-5.0$ rpm -q --changelog openssl | head * Mon Jun 03 2019 Tomáš Mráz <tmraz> 1.1.1c-3 - add upstream patch to defer sending KeyUpdate after pending writes are complete * Thu May 30 2019 Tomáš Mráz <tmraz> 1.1.1c-2 - fix use of uninitialized memory * Wed May 29 2019 Tomáš Mráz <tmraz> 1.1.1c-1 - update to the 1.1.1c release I would expect that C.utf8 should be reasonable falback. I do not really care about wrong utf8 characters in changelog but it is simpler reproducer that sharing broken ncurses output from mutt (In reply to Lukas Slebodnik from comment #1) > sh# rpm -qa | grep lang | sort > clang-8.0.0-2.fc31.x86_64 > clang-analyzer-8.0.0-2.fc31.noarch > clang-libs-8.0.0-2.fc31.x86_64 > glibc-all-langpacks-2.29.9000-24.fc31.x86_64 > liblangtag-0.6.2-7.fc30.x86_64 > liblangtag-data-0.6.2-7.fc30.noarch > libreoffice-langpack-en-6.2.3.2-5.fc31.x86_64 > slang-2.3.2-5.fc30.x86_64 This is fixed -25. *** This bug has been marked as a duplicate of bug 1716710 *** (In reply to Lukas Slebodnik from comment #2) > And there is another issue with utf8 locale > > sh-5.0$ locale > LANG=C.utf8 > LC_CTYPE="C.utf8" > LC_NUMERIC="C.utf8" > LC_TIME="C.utf8" > LC_COLLATE="C.utf8" > LC_MONETARY="C.utf8" > LC_MESSAGES="C.utf8" > LC_PAPER="C.utf8" > LC_NAME="C.utf8" > LC_ADDRESS="C.utf8" > LC_TELEPHONE="C.utf8" > LC_MEASUREMENT="C.utf8" > LC_IDENTIFICATION="C.utf8" > LC_ALL=C.utf8 > sh-5.0$ rpm -q --changelog openssl | head > * Mon Jun 03 2019 Tomáš Mráz <tmraz> 1.1.1c-3 > - add upstream patch to defer sending KeyUpdate after > pending writes are complete > > * Thu May 30 2019 Tomáš Mráz <tmraz> 1.1.1c-2 > - fix use of uninitialized memory > > * Wed May 29 2019 Tomáš Mráz <tmraz> 1.1.1c-1 > - update to the 1.1.1c release > > > I would expect that C.utf8 should be reasonable falback. It is. LANG=C.UTF-8 rpm -q --changelog openssl | head * Tue Apr 16 2019 Tomáš Mráz <tmraz> 1.1.1b-5 - fix for BIO_get_mem_ptr() regression in 1.1.1b (#1691853) I don't see anything broken. Please verify you have: /usr/lib/locale/C.utf8 present on your system. It is installed by glibc-common and cannot be removed with dnf/rpm. So you should always have it as a fallback. > I do not really care about wrong utf8 characters in changelog but it is > simpler reproducer that > sharing broken ncurses output from mutt Please file a new issue if you can reproduce the problem. |