Bug 1701605
Summary: | glibc: The locale command returns a vague error message if the LOCPATH environment variable is defined. | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Greg Scott <gscott> | |
Component: | glibc | Assignee: | Arjun Shankar <ashankar> | |
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-tools-bugs | |
Severity: | medium | Docs Contact: | Abhimanyu Jamaiyar <ajamaiya> | |
Priority: | unspecified | |||
Version: | 8.1 | CC: | ashankar, codonell, dj, fweimer, kdudka, lmanasko, mnewsome, pfrankli, skolosov, vslavik | |
Target Milestone: | rc | Keywords: | Patch | |
Target Release: | 8.1 | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glibc-2.28-57.el8 | Doc Type: | Bug Fix | |
Doc Text: |
.The `locale` command now warns about `LOCPATH` being set whenever it encounters an error during execution
Previously, the `locale` command did not provide any diagnostics for the `LOCPATH` environment variable when it encountered errors due to an invalid `LOCPATH`.
The `locale` command is now set to warn that `LOCPATH` has been set any time it encounters an error during execution. As a result, `locale` now reports `LOCPATH` along with any underlying errors that it encounters.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1717492 (view as bug list) | Environment: | ||
Last Closed: | 2019-11-05 21:29:04 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: | ||||
Bug Depends On: | 1717492 | |||
Bug Blocks: | 1684553 | |||
Deadline: | 2019-05-22 |
Description
Greg Scott
2019-04-19 20:30:02 UTC
The locale command is provided by glibc, not bash. The customer who reported this wanted me to add this comments: "Could you please also indicate in the Bugzilla that this problem also exists in RHEL6 ? Or at least mention that it goes back to at least glibc-common-2.12-1.212. I'm sure this problem is much, much older, but that's the oldest one I have." I reproduced the problem myself with RHEL 6.10. - Greg Note to anyone trying to reproduce this on current glibc versions: If LOCPATH is a non-existing path, the locale archive is ignored, but not split-out locale files from the glibc-langpack-* packages. Perhaps the search order should be LOCPATH, archive, split-out locale files? I'm not sure we can do much about detecting invalid LOCPATH settings in the locale tool. If we change the search order, the error message would be gone in many cases, even if with an invalid LOCPATH setting. I posted a patch upstream with additional diagnostics: https://sourceware.org/ml/libc-alpha/2019-04/msg00502.html New diagnostics are now upstream: commit e485b2b6e006a7efa5d73e6be7e357a395c77fe3 Author: Florian Weimer <fweimer> Date: Tue Apr 23 18:16:26 2019 +0200 locale: Add LOCPATH diagnostics to the locale program The implementation of quote_string is based on support_quote_blob. Reviewed-by: Carlos O'Donell <carlos> We do not plan to address issue in Red Hat Enterprise Linux 7, but will consider backporting the upstream diagnostic into Red Hat Enterprise Linux 8. The test case was fixed upstream with: commit 439bf53496d6ed5fcef1d2e71793b46369f8205f Author: Florian Weimer <fweimer> Date: Wed Apr 24 07:31:29 2019 +0200 locale/tst-locale-locpath: Run test only for $(run-built-tests) == yes Also included: commit 439bf53496d6ed5fcef1d2e71793b46369f8205f Author: Florian Weimer <fweimer> Date: Wed Apr 24 07:31:29 2019 +0200 locale/tst-locale-locpath: Run test only for $(run-built-tests) == yes thanks to Florian's review. Verified with locale/tst-locale-locpath Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:3513 |