Bug#834951: gnome-shell: Mixed localizations

[Simon McVittie]

On Tue, 13 Sep 2016 at 18:31:27 +0200, Michael Biebl wrote:
> In any case, that isn't really a gnome-shell issue, but deeper down the
> stack. Not sure if it's systemd, dbus-user-session or gnome-session.

I think this might actually be a distinction between things that are
localized by the user session (which work) and things that are localized
by the system (which fail because your systemd-localed is failing
to start). However, to rule out issues with systemd --user and
dbus-user-session, please run systemd-cgls and look for:

* a dbus.service that is a child of user@$(id -u).service
  - the dbus-daemon in that service
  - any other process in that service (if you are a GNOME user,
    goa-daemon and goa-identity-service are a good example of D-Bus
    session services that haven't been turned into systemd user
    services yet)

* some random other service that is a child of user@$(id -u).service
  (telepathy-mission-control-5.service or gvfs-daemon.service are
  good examples)
  - the main process in that service

* a child of the same session-whatever.scope below user@$(id -u).service
  that contains your gnome-shell, for example the gnome-shell itself,
  or (on my system) evolution-alarm-notify and several Tracker processes

and look at their environment with a command like this:

    perl -0 -p -e 'print qq{\n}' /proc/2393/environ | LC_ALL=C sort -u

(where 2393 is the pid of one of the processes of interest). You should
hopefully find that their LANG and LANGUAGE environment variables are
as expected.

    S