After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 678567 - Adding a Language in "Region and Language" does not persist across closing the dialogue in gnome-control-center-3.4.1-2.mga2 on Mageia Linux 2 on x86-64
Adding a Language in "Region and Language" does not persist across closing th...
Status: RESOLVED DUPLICATE of bug 647373
Product: gnome-control-center
Classification: Core
Component: Region & Language
3.4.x
Other Linux
: Normal major
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-06-21 18:27 UTC by Shlomi Fish
Modified: 2012-12-10 14:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Shlomi Fish 2012-06-21 18:27:40 UTC 
Hi all.

On Mageia Linux 2 on x86-64 with a brand new UNIX user account when starting a GNOME 3.4.x environment from KDM, I am unable to add a new language to the languages dialogue in "Region and Language". What happens is:

1. Start gnome-control-center (from the command line or desktop menus - does not matter).

2. Region and Language.

3. Language.

4. Press the + button.

5. Select Hungarian or any other language.

6. Press the icon at the top to return to the main window of the control center.

7. Region and Language -> Language aggain.

8. "Hungarian" does not exist there.

This is a big problem because it makes the dialogue useless.

Regards,

-- Shlomi Fish
Comment 1 Bastien Nocera 2012-06-21 18:45:21 UTC 
Is dconf installed?
Comment 2 Shlomi Fish 2012-06-21 19:46:45 UTC 
> Is dconf installed?
(In reply to comment #1)

shlomif@lap:~$ rpm -q dconf
dconf-0.12.0-1.mga2

Yes, it is installed.
Comment 3 Matthias Clasen 2012-06-22 11:40:08 UTC 
What the panel is trying to do is to show a small fixed list of languages + the current language. When you use the add dialog to add one to the list, it gets selected and that has the effect of making it the current language for the next login. You can see that by looking at /var/lib/AccountService/users/<username>.

What we currently don't handle well enough is the fact that after you've made such a change, there are now two 'current' languages. The one the current session is running in, and the one that is stored in that accountsservice file and will be the current language for the next login.

Nothing we can do here will be ideal, it is all cramped by the misfeature that we have to log out to change language. 

Proposal to make the behaviour more consistent: 

1) Always include both the currently effective language and the language for the next login in the list

2) Always select the language for the next login (ie mark it as 'current')

Alternatively, we could introduce a separate marker for 'will be used for next login', and only move that when a row is activated. Not sure if that would be more or less confusing...
Comment 4 Bastien Nocera 2012-12-10 14:29:23 UTC 
The changes made for bug 647373 fix that problem.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 647373 ***