On Mon, 23 Jul 2012 10:33:32 +0200
Yves-Alexis Perez <cor...@debian.org> wrote:
>> One might ask why a Pluggable Authentication Module ought to be
>> responsible for things which clearly have nothing to do with
>> authentication, such as locale selection, especially when they are
>> liable to change at every login.
>
> PAM is more than authentication, it handles quite some login-related
> stuff. And maybe it makes sense to store login-specific settings like
> locales into PAM. But my feeling is that it's not the case. It seems
> that PAM (through pam_env module) only handles /default/ environment,
> taken from /etc/environment. So while it might be useful to have a
> default setting for the box, it's plain useless for user-specific
> settings. So if my analysis is right, I'm a bit puzzled about the
> change.
This.
Not just user-specific settings, but session-specific settings.
> Note that you might try with accountsservice installed, it might help.
Doesn't seem to, and I don't see why it would. According to the README:
The AccountsService project provides
- A set of D-Bus interfaces for querying and manipulating user
account information.
- An implementation of these interfaces based on the usermod(8),
useradd(8) and userdel(8) commands.
There's nothing session-specific about that.
-- Ian Bruce
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
