Duncan <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Sat, 20 Oct 2007 11:04:42 +0000:
> widyachacra <[EMAIL PROTECTED]> posted > [EMAIL PROTECTED], excerpted > below, on Sat, 20 Oct 2007 13:19:25 +0530: > >> I get below notice when i open the K3B. >> >> System locale charset is ANSI_X3.4-1968 Your system's locale charset >> (i.e. the charset used to encode filenames) is set to ANSI_X3.4-1968. >> It is highly unlikely that this has been done intentionally. Most >> likely the locale is not set at all. An invalid setting will result in >> problems when creating data projects. Solution: To properly set the >> locale charset make sure the LC_* environment variables are set. >> Normally the distribution setup tools take care of this. >> >> I tried to write more ISO distros but all are failed. Please help me. >> How to change LC_* details. > > FWIW, I have the same problem here, but it hasn't seemed to actually > affect anything operationally. [If] anyone has a solution, I too could > use it, as the warnings do get old after awhile, even if they don't > seem to actually matter much if at all. Fixed it here. All it took was running "locale-gen" to fix my locales. I read something recently about a bug (since fixed) in IIRC util-linux that caused locale issues, but didn't worry much about it since I only read English anyway. However, I think what must have happened is that glibc was upgraded while this bug was active, and the locale-gen that glibc ebuilds normally run as part of the upgrade failed. I'd known about the problem for awhile, but it wasn't anything high priority as everything seemed to continue to work despite the k3b warning and a few similar warnings compiling things. However, after writing the above, I decided to look into it a bit, and sure enough quick-fix. /etc/ locales.gen was still set correctly, but for whatever reason, probably the above bug, it hadn't run properly the last time it had been run, so I didn't have a valid locale. Rerunning locales-gen manually was a simple enough fix, once I figured out that was the problem. So run locales-gen and see if that fixes it. I didn't even have to update my environment as that was right, it was simply pointing to a locale config that didn't exist where it was supposed to, and locales-gen was all it took to fix it. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [EMAIL PROTECTED] mailing list
