This bug was fixed in the package accountsservice - 0.6.42-0ubuntu3.1
---
accountsservice (0.6.42-0ubuntu3.1) artful-proposed; urgency=medium
* debian/patches/0009-language-tools.patch:
- Modification of the update-langlist script due to new
~/.pam_environment syntax (LP:
This bug was fixed in the package language-selector - 0.180.1
---
language-selector (0.180.1) artful-proposed; urgency=medium
* LanguageSelector/LocaleInfo.py:
Adapt to changed syntax in ~/.pam_environment (LP: #1722151).
-- Gunnar Hjalmarsson Fri, 27
I installed the language-selector-{gnome,common} 0.180.1 and
accountsservice 0.6.42-0ubuntu3.1 packages from artful-proposed.
As regards language-selector I verified the test case in the bug
description.
As regards accountsservice, these steps show that it now works as
expected:
1.
$ cat
Hello Olivier, or anyone else affected,
Accepted accountsservice into artful-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/accountsservice/0.6.42-0ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
This bug was fixed in the package accountsservice - 0.6.42-0ubuntu4
---
accountsservice (0.6.42-0ubuntu4) bionic; urgency=medium
* debian/patches/0009-language-tools.patch:
- Modification of the update-langlist script due to new
~/.pam_environment syntax (LP: #1722151).
This bug was fixed in the package language-selector - 0.181
---
language-selector (0.181) bionic; urgency=medium
* LanguageSelector/LocaleInfo.py:
Adapt to changed syntax in ~/.pam_environment (LP: #1722151).
* LanguageSelector/ImConfig.py:
Prevent crash if LC_CTYPE is
This triggers another change to accountsservice...
** No longer affects: language-selector (Ubuntu Artful)
** Also affects: language-selector (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: accountsservice (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: language-selector (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: language-selector (Ubuntu Artful)
Status: Triaged => In Progress
** Changed in: language-selector (Ubuntu Artful)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
You
** Description changed:
+ [Impact]
+
+ When the syntax for the entries in ~/.pam_environment was changed, the
+ GUI in language-selector-gnome for maintaining the language priority
+ list was broken since language-selector-gnome reads from
+ ~/.pam_environment. The language-selector upload to
** Also affects: language-selector (Ubuntu)
Importance: Undecided
Status: New
** Also affects: language-selector (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: accountsservice (Ubuntu Artful)
Importance: Undecided
Status: New
** No longer
This bug was fixed in the package accountsservice - 0.6.42-0ubuntu3
---
accountsservice (0.6.42-0ubuntu3) artful; urgency=medium
* debian/patches/0009-language-tools.patch:
- Use correct syntax when writing to ~/.pam_environment
(LP: #1722151).
-- Gunnar Hjalmarsson
Thanks for clarifying, Olivier. Fix uploaded to the artful queue.
** Changed in: accountsservice (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
This is misleading. The syntax for envfile is "VARIABLE=value" pairs,
whereas the syntax for user_envfile is that of pam_env.conf ("VARIABLE
[DEFAULT=[value]] [OVERRIDE=[value]]"). The documentation leaves to be
desired in that regard, but reading the code confirms that the two files
are parsed
Hmm.. I just noticed this in "man pam_env":
"By default rules for (un)setting of variables is taken from the config
file /etc/security/pam_env.conf if no other file is specified.
This module can also parse a file with simple KEY=VAL pairs on separate
lines (/etc/environment by default)."
When adding the "debug" parameter to the invokation of pam_env in
/etc/pam.d/gdm-password, I'm seeing the following in journalctl:
oct 09 09:52:59 artfulvm gdm-password][1072]: pam_env(gdm-password:session):
pam_putenv("PATH=/usr/local/sbin:/usr/local/bin:/usr/
oct 09 09:52:59 artfulvm
Hi Olivier / Sebastien,
Olivier's conclusion when debugging bug #1662031 (comment #13), that the
simple VARIABLE=value syntax is incorrect for ~/.pam_environment,
surprised me.
My belief is that it is correct. PAM ignores syntactically incorrect
lines, and simple VARIABLE=value statements are
** Changed in: accountsservice (Ubuntu)
Importance: Undecided => High
** Changed in: accountsservice (Ubuntu)
Status: New => Confirmed
** Changed in: accountsservice (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
You received this bug notification because
17 matches
Mail list logo