Bug 5529 - My locales are a mix of French and Japanese while no Japanese locale installed.
Summary: My locales are a mix of French and Japanese while no Japanese locale installed.
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-04-21 11:36 CEST by Jehan Hysseo
Modified: 2012-05-27 05:03 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Jehan Hysseo 2012-04-21 11:36:22 CEST
Description of problem:

On various places, I see locales error. For instance on the terminale, when I shuts the computer down, or after various unrelated command lines, etc.
For instance, I just had this one:

----------------

# /etc/init.d/sshd start
/etc/sysconfig/i18n: ligne9: avertissement :setlocale : LC_NUMERIC : impossible de changer le paramètre de langue (ja_JP.UTF-8) : Aucun fichier ou dossier de ce type
Starting sshd (via systemctl):                                   [  OK  ]
-----------------

Sorry that's French version. It says basically it cannot load the Japanese locale for LC_NUMERIC. So let's have a look at this i18n file at the start of the warning message:

-----------------
# cat /etc/sysconfig/i18n 
LC_TELEPHONE=ja_JP.UTF-8
LC_CTYPE=fr_FR.UTF-8
LANGUAGE=fr_FR.UTF-8:fr
LC_MONETARY=ja_JP.UTF-8
LC_ADDRESS=ja_JP.UTF-8
LC_COLLATE=fr_FR.UTF-8
LC_PAPER=ja_JP.UTF-8
LC_NAME=ja_JP.UTF-8
LC_NUMERIC=ja_JP.UTF-8
SYSFONT=lat0-16
LC_MEASUREMENT=ja_JP.UTF-8
LC_TIME=fr_FR.UTF-8
LANG=fr_FR.UTF-8
LC_IDENTIFICATION=ja_JP.UTF-8
LC_MESSAGES=fr_FR.UTF-8
-----------------

So I can see I have a mix of French and Japanese locales there!
French is normal. I installed from the Europe1 64 bits liveCD and set the installation and OS in French from the start.
But I never set anything in Japanese as a default language (and I indeed don't even have the "locales-ja" package). Also I never touched by hand any locale-related configuration file. I did only basic installations, all from the Package Manager.

I guess that's not fully random though. I indeed read and write some Japanese, so I installed Japanese fonts and ibus-anthy. So my guess is that there is something in one of the Japanese packages which tried to set some locales and left a mess there.

Below is a list of Japanese-related packages I installed (hopefully exhaustive):

- fonts-ttf-japanese 0.20110512 (noarch)
- fonts-ttf-japanese-extra 0.20040217 (noarch)
- anthy 9100h (x86_64)
- ibus-anthy 1.2.6 (x86_64)
- lib64-anthy0 9100h (x86_64)

I guess the problem is from one of these.
Comment 1 Manuel Hiebel 2012-04-22 00:30:32 CEST
Funda, maybe you have an idea ?

CC: (none) => fundawang

Comment 2 Funda Wang 2012-04-22 03:37:29 CEST
Did you use localedrake to set ibus?
Comment 3 Jehan Hysseo 2012-04-22 12:34:06 CEST
I did.
Comment 4 Jehan Hysseo 2012-05-20 06:55:19 CEST
Hello,

I installed Mageia 2 RC. That's another computer, but basically same kind of configuration (French desktop, but some Japanese input through ibus-anthy). On this computer with RC version (previous installation was one of the beta), I did not encounter this bug.

Maybe the issue has been fixed since the beta versions (or else it was a bug which happens only on very particular and difficult to reproduce cases). I'd say that when I will install released version on the previous computer and if the problem does not happen again, I will close this ticket. Unless someone else encounters the same problem of course.

Hardware: i586 => x86_64

Comment 5 Marja Van Waes 2012-05-26 13:02:45 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 6 Jehan Hysseo 2012-05-27 05:03:12 CEST
Did not try with Mageia 2 yet, but as I said in previous message, it did not happen in RC (only in Beta).

I close the ticket. I am not really aware of procedures and if that's totally OK that I close the ticket myself, as the reporter. If this is not, please tell me so that I do well next time. :-)

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.