Red Hat Bugzilla – Bug 197642
user interface couldn't change to other language
Last modified: 2008-08-02 19:40:36 EDT
Description of problem:
change language and content packs, but user interface couldn't change to
selected languages even after uninstalling English
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. select 'Preferences...' from the Edit menu, in the preferences window, expand
the 'Appearance' category and open the 'Languages/Content' panel
2. click 'Download More...' and on pop up web page
(http://www.mozilla.org/projects/seamonkey/releases/#|10n) and click
'installable language pack' link after a language such as 'French'
3. on pop up dialog click 'Install' and 'OK' (it prompt 'Download and install
French SeaMonkey Language Pack Success)
5. re-open 'Languages/Content' panel by click Edit menu -> Preferences... ->
Appearance -> Languages/Content
6. select the new installed language and content packs and click 'OK'
7. close all SeaMonkey windows
8. start SeaMonkey again
user interface is still English
after SeaMonkey is started again, the user interface should be in your favourite
I can reproduce it on RHEL-4/FC-5.
Is your $LANG set properly? For instance LANG=cs_CZ.UTF-8 for Czech.
Martin, I have locale cs_CZ.UTF-8 and I can very well reproduce it. When I go
back to the Appearance/Language settings, English environment is always
selected, although I have selected the Czech before restarting mozilla.
Also, does it matter whether I have installed language pack into profile or into
chrome (I did former)?
Since this bugzilla report was filed, we have seriously upgraded Gecko-related
packages, which may have resolved this issue. Users who have experienced this
problem are encouraged to upgrade their system to the latest version of their
Please, confirm to us that this bug is reproducible on the latest upgrade of the
supported distribution (that's RHEL, or Fedora 7, 8, and Rawhide).
Setting the bug to NEEDINFO. If I won't get confirmation of reproducability in
30 days, the bug will be closed as INSUFFICIENT_DATA.
[This is mass-changing of bugs which seem to be too old and irrelevant anymore;
we are sorry, if this bug should not be incldued.]
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.