← Back to team overview

dx-packages team mailing list archive

[Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property

 

@Sebastien: The new "Languages" property is described as an optional
one, but it still looks like language changes are now stored in the
"Languages" property instead of "Language".

The backend patches in accountsservice, g-c-c, etc. (which I'm guilty
of)

1. serve the purpose of keeping language-selector-gnome useful for both
Ubuntu and all the flavors (except for Kubuntu, which relies on KDE
stuff), and

2. make the language selection control in language-selector-gnome play
well with the equivalent in Region & Language.

I'll try to find out if GetLanguage and SetLanguage still works as
intended for us at this point.

If a UI control for maintaining "Languages" directly is added to g-c-c,
I imagine that we need to re-evaluate our approch more thoroghly. Do you
know if there is such a plan?

As regards disabling of that test, I wouldn't worry too much. Our code
does the right thing when a string like "fr_FR:en" is passed to
SetLanguage, and makes sure that only a valid locale name of a locale
which has actually been generated on the system is assigned to LANG via
~/.pam_environment.

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/2024560

Title:
  Check if 0010-set-language needs to be update for the new languages
  property

Status in accountsservice package in Ubuntu:
  New

Bug description:
  Upstream did changes to add a languages properties

  https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7

  I've rebased 0010-set-language to apply correctly but we should review
  if we need to adapt the patch to apply a similar logic to the new
  languages property that it's doing for old language one

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024560/+subscriptions



References