Created attachment 4802 [details] journalctl -a after French and Paris were chosen When starting a Live Gnome session from DVD (pre-RC, 8th round of isos, 64bits), the language and location choice are no longer respected once Gnome starts. doing "locale" shows that the setting is "en_US" for everything. This has been tested with French/Paris, Dutch/Amsterdam and one more. The KDE LiveDVD does *not* have this problem.
Whiteboard: (none) => 4RC
Confirmed with en_GB. The Live system is using en_US. ie. Spellcheck in LO, currency, date format etc I'll recheck LiveCD to see if it occurs there too.
CC: (none) => eeeemail
Last night's GNOME 64 LiveDVD, tried with French/Paris Every locale setting is again en_US after having reached the Gnome desktop :-(
LiveCD is also affected, formats for date, measurements, currency etc are en_US in gnome settings and firefox spellcheck is using en_US.
Blocks: (none) => 11704Summary: Gnome LiveDVD doesn't respect chosen locales => Gnome Live ISOs don't respect chosen locales
gnome-session[2426]: ** (gnome-control-center:2866): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did n gnome-session[2426]: (gst-plugin-scanner:2875): GStreamer-CRITICAL **: gst_structure_new_empty: assertion 'gst_structure_validate_name (name)' failed gnome-session[2426]: (gnome-control-center:2866): GnomeDesktop-CRITICAL **: gnome_get_language_from_locale: assertion '*locale != '\0'' failed gnome-session[2426]: (gnome-control-center:2866): GnomeDesktop-CRITICAL **: gnome_get_country_from_locale: assertion '*locale != '\0'' failed
This only seems to affect live mode, marja could you confirm please.
(In reply to claire robinson from comment #5) > This only seems to affect live mode, marja could you confirm please. indeed, after a live install from the boot menu (so not from a live session), this is fine. I did keep unused locales, though, I'll try again to see what happens if I remove the "unused" ones
after installing from a Live session (and removing unused locales), locales are OK, too, even if the install screens are all in English
commit c01b45c78de95b0f9dacf6930c58220280ff168b Author: Colin Guthrie <colin@...> Date: Tue Jan 21 22:07:15 2014 +0000 Ensure that GDM is reloaded on live media. With out this the locale settings are not reread and en_US is used for the whole session. I'm not 100% sure why the previous call now fails, but I suspect it could be due to /usr/sbin not being in the path due to /etc/ profile not being sourced early on (i.e. in the gdm binary) and thus this command fails to run. mga#11582 mga#12328 --- Commit Link: http://gitweb.mageia.org/software/build-system/draklive-config/commit/?id=c01b45c78de95b0f9dacf6930c58220280ff168b Bug links: Mageia https://bugs.mageia.org/show_bug.cgi?id=11582 https://bugs.mageia.org/show_bug.cgi?id=12328
I think the above commit *should* fix this once Thomas rebuilds the Live medias with the updated config.
CC: (none) => mageia
Awsome, thanks. btw, the "RUNNING_UNDER_GDM" is a flag/variable set by gdm itself: https://git.gnome.org/browse/gdm/tree/daemon/gdm-launch-environment.c#n291
Yeah I found the RUNNING_UNDER_GDM env var in GDM after I made a comment about it. There is an alternative to this fix which I've described in the other bug. Let me know if you'd prefer that one or if we should stick with this for now.
Can you push the other fix so we can get a broad test of it. Saving one gdm restart will make boot go faster, and less flickering. Then I'll simply disable the installing of 99-dm-reload.xsetup for next iso build
commit 2fbb89f3fc1b8196f45c6bc02b006e47658f2be1 Author: Colin Guthrie <colin@...> Date: Wed Jan 22 00:51:50 2014 +0000 Drop support for GDM_LANG. This is no longer needed/supported. mga#12328 --- Commit Link: http://gitweb.mageia.org/software/forks/initscripts/commit/?id=2fbb89f3fc1b8196f45c6bc02b006e47658f2be1
(In reply to Thomas Backlund from comment #12) > Saving one gdm restart will make boot go faster, and less flickering. > Then I'll simply disable the installing of 99-dm-reload.xsetup for next iso > build If you push initscripts and gdm they should contain the needed fixes to allow the dropping of 99-dm-reload.xsetup.
Both pushed
This bug is confirmed fixed
Status: NEW => RESOLVEDResolution: (none) => FIXED
looks to come back on the Mga5 alpha2 iso (needs to be confirmed)