Red Hat Bugzilla – Bug 706756
gnome-control-center's Region and Language seems incapable of setting (or correctly reading) the system language
Last modified: 2012-10-26 00:01:23 EDT
Description of problem:
There is no translation on Login-Page of the reboot-menu.
Version-Release number of selected component (if applicable):
Fedora 15 Beta, Gnome 3
Steps to Reproduce:
1. boot fedora
2. change the language to german
3. goto the login-page
4. select in the upper right corner the menu and see the entries
5. all entries are in english not in german
all entries are in english "shutdown", ...
all entries should be in german "ausschalten", ...
current GDM version:
The clock on login-page is also not translated. It is presented in english.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
To help us in assessing the blocker status of this bug, please cite the release criterion - https://fedoraproject.org/wiki/Fedora_Release_Criteria - you think it infringes. Thanks!
Fedora Bugzappers volunteer triage team
Fedora Bugzappers volunteer triage team
assuming that this should meets to """
All release-blocking desktops' offered mechanisms (if any) for shutting down, logging out and rebooting must work
""" in Beta Release Criteria. there are no way to see "that is it" if no translations. we shouldn't assume all of users can read English.
it is 16blocker, so moving
Discussed at 2011-09-30 blocker review meeting. We felt this merits blocker consideration, but we do not have criteria for translations at present. We decided to accept it as NTH and table blocker status until next week; we will aim to propose a criterion for translations this week.
Discussed again at 2011-10-07 blocker review meeting. We didn't manage to propose the i18n criteria yet, so we're punting on this for another week. We'll definitely evaluate it next week.
Discussed at 2011-10-14 blocker review meeting. Accepted as a blocker under newly minted criterion "The installer, bootup and login processes should correctly display all sufficiently complete translations available for use." (will be added to the criteria page soon).
I can see German on the menu with gdm-3.2.0-2.fc16.x86_64.
So what languages we should actually cover with that criterion?
I saw your mail on the list that says "popular languages". how can I measure which one is really popular?
with a hand-wave and some IRC arguing - that's usually how we do it. ;)
but the initial report was about German, so maybe this is fixed now? Rolle, can you confirm?
It doesn't work for me. Sorry.
I downloaded the nightly build desktop-cd-image from 2011-10-19. Installed Fedora 16 Prerelease. Made all updates. Switched the language to german. After reboot and logout the Login-Screen is still presented in english.
Ah - well that may actually be as intended. What did you 'switch language to German' with exactly? Did you use GNOME's 'Region and Language' or the Fedora 'system-config-language' tool?
If you use 'Region and Language' note that the setting on the Language tab is *your personal* setting. If you then go to the System tab you will see this:
"The login screen, system accounts and new user accounts use the system-wide Region and Language settings. You may change the system settings to match yours."
Can you run that tool, go to that tab, and see what it says your personal settings vs. the system settings are? If the system's still set to English, does using the 'Copy Settings...' button in that dialog help? Thanks!
I switched the language always with "Region and Language" of the system settings collection from the upper right menu. Then I go to the system tab (which is new in Gnome 3.2, In Fedora 15 Gnome 3.0 there isn't such a tab):
It shows that my personal settings are set to german and the system is set to english. The Button "Copy settings ..." doesn't change anything. Then I logout and the login screens remains in english. (Nightly Buid 2011-10-19: gdm-3.2.0-2.fc16.x86_64)
Now I tried your hint with "system-config-language" and switch the language to german, but the login-screen remains in english.
I had a installed Fedora 16 system, tried for German (de_DE.UTF-8) locale. If selected Language German with System-config-language, then GDM shows all entries in non-English (I hope following is German):
1 - Bereitschaft
2 - Neu starten
3 - Ausschalten
Calendar has following:
Samstag, 22. Oktober
for system-config-language need to reboot to take effect, so may not work on live image.
Also I tried following command on fedora 16 (which shows translated message from installed system in selected langauge):
[aalam@yuri ~]$ LANG=de_DE.UTF-8 gettext -d gdm "Shut Down"
[aalam@yuri ~]$ LANG=de_DE.UTF-8 gettext -d gdm "Restart"
[aalam@yuri ~]$ LANG=de_DE.UTF-8 gettext -d gdm "Suspend"
I can confirm Rolle's experience that the "Copy Configuration" button in the GNOME Control Center appears to do nothing. But I can also confirm A. S. Alam's report that system-config-language works, if you reboot.
Given this, I'm revising my vote to -1 blocker, -1 nth: it doesn't look like there's a bug in gdm preventing translations from being displayed, or anything, the problem if any is a problem in one specific mechanism for changing the system language, which is a less serious issue.
Any other vote changes?
re-assigning to control-center, there does not appear to be a gdm bug here.
hum, system-config-language changes gdm, but not the user's desktop. seems like you need to change both to get everything switched.
Confirmed, system-config-language changes only GDM (translated text is displayed properly after reboot), and control center changes only user session, "copy settings" doesn't work.
-1 to blocker, -1 to nth
Sure, know that we know the full impact, I'm happy to go with -1 to blocker, 0 to NTH
You all are right. It worked for me.
This was my fault. A S Alam your comment 24 is correct: thats the german strings.
1. I didn't know that I must use "system-config-language".
2. After that I MUST reboot in F16. I understood "system-config-language" that a simple logout is enough (so I hadn't problems to check this with live cd).
In F15 was the logout enough to change the Login-translations.
And in my many tries I realized, that this language-switch is a complex thing. Is this really needed?
a: On a live cd or a fresh install I need Internet-connection to get the tool "system-config-language". But I don't have an internet-connection everywhere.
Then the language-portion which is loaded from internet depends from the installed applications. On that fresh install the switch to german is very quick done. But on my horsepower-PC with F15 installation is LibreOffice, GCompris, ... and I switched already to german. But the "system-config-language" told me that no german support is installed and then it loaded many files which took an era on my one pc that has a very very small and very very instable internet connection.
Some files are checked that these are already on my pc but I believe that some other files downloaded for a second time. Are there unneeded dependencies? But this is a subjective feeling.
b: The tool "Region and Language" should give a hint that "system-config-language" is needed for the system-wide settings.
c: Is it possible to do on the loginscreen an easy language switcher for everyone? The menu could show all installed languages for the login-screen and should be presented like this: first the english name and in braces the native name) like many installers do.
Thanks for all which helped me. For me this bug is closed, because this was not really a bug. I didn't know it better.
All you guys which are envolved in the translation-system, thank you for all your hard work until now and keep your motivation for another long time.
Rolle: in previous Fedoras, GDM had a little dialog which let you pick the language before you logged in.
In GNOME 3.2 that's been dropped on the basis that you can just pick the language after you log in, but that leads to this little problem. :/
It should be less of a problem if control-center is fixed so it can actually set the system-wide language.
I confirmed that you can at least change the language for the desktop in the live image by using the GNOME tool and logging out / back in after you change it. Which is a bit clunky, but at least works.
So, adjusting for the re-vote: now not a blocker or NTH, now we understand it better. But control-center needs fixing so it can set the system language.
There are two bugs here.
1) The assorted setup scripts (lang.sh, etc.) don't read /etc/locale.conf that is being written here. This is fixed in http://git.fedorahosted.org/git/?p=initscripts.git;a=commitdiff;h=d088bd27ef9fac2695c9769b4fbb230e32d93b31, which will go out shortly in an initscripts update.
2) The SELinux policy is squashing the communication between policykit and the assorted systemd mechanisms. I believe this can be fixed by:
diff --git a/policy-F16.patch b/policy-F16.patch
index 60b7398..61effe4 100644
@@ -48354,6 +48354,7 @@ index 1e7169d..05409ab 100644
+ dbus_system_domain(policykit_t, policykit_exec_t)
un-setting AcceptedBlocker, as we don't have votes on the revised problem, here.
i'm still not entirely sure this is a blocker, if s-c-language works, and you can set language during install on the DVD path...how is fixing this on the images significantly better than fixing it with an update? what criteria are we breaking?
if the fixes can make it work with just a log out / log in on the live image i guess i'd be +1 nth at least...
notting's changes to the blocker status were apparently just a mistake, so reverting.
initscripts-9.34-2.fc16 has been submitted as an update for Fedora 16.
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing initscripts-9.34-2.fc16'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
initscripts-9.34-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 712981 has been marked as a duplicate of this bug. ***