lightdm-gtk-greeter-team team mailing list archive

Thread
Date

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

To: lightdm-gtk-greeter-team@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <957431@xxxxxxxxxxxxxxxxxx>
Date: Fri, 08 Feb 2013 13:52:14 -0000
Reply-to: Bug 957431 <957431@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

You have been subscribed to a public bug by Gunnar Hjalmarsson (gunnarhj):

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.

** Affects: lightdm
     Importance: Low
         Status: Triaged

** Affects: lightdm (Ubuntu)
     Importance: Low
         Status: Triaged

-- 
Encrypted HOME should be 'unlocked' at login before calling SetLanguage
https://bugs.launchpad.net/bugs/957431
You received this bug notification because you are a member of LightDM Gtk+ Greeter Development Team, which is subscribed to the bug report.