← Back to team overview

lightdm-gtk-greeter-team team mailing list archive

[Bug 957431] Re: Encrypted HOME should be 'unlocked' at login before calling SetLanguage

 

Now when bug 952185 is being fixed, it's high time to fix this issue as
well. Even if it is a lightdm bug, it's the usability of lightdm-gtk-
greeter that is affected adversely. If you log in to an account with an
eCryptfs protected HOME, any attempt to set the language from the
language chooser on the greeter fails.

-- 
You received this bug notification because you are a member of LightDM
Gtk+ Greeter Development Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/957431

Title:
  Encrypted HOME should be 'unlocked' at login before calling
  SetLanguage

Status in Light Display Manager:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged

Bug description:
  Apart from bug #952185, the language chooser on the lightdm-gtk-
  greeter does not work if you log in to a user with an encrypted HOME.
  The call for accountsservice's SetLanguage method happens before HOME
  is available, so it's rejected by SetLanguage.

  It seems like HOME needs to be 'unlocked' earlier and/or the
  SetLanguage call postponed. That way the language chooser would work
  also with an encrypted HOME, and without a need to e.g. mess with a
  cache file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/957431/+subscriptions