A user let us know at bug 982383 that also likewise-open causes this
problem, so I prepared a merge proposal.
** Also affects: likewise-open (Ubuntu)
Importance: Undecided
Status: New
** Changed in: likewise-open (Ubuntu)
Importance: Undecided = Medium
** Changed in: likewise-open
** Branch linked: lp:~gunnarhj/ubuntu/raring/likewise-open/pam
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1162836
Title:
likewise screws up PAM configuration for other services
On Thu, Apr 04, 2013 at 01:43:12AM -, ClaudeD wrote:
Steve's comment is interesting : our setup is with PBIS 7 (the successor
of likewise-open) and it was installed with the PowerBroker package.
However we are not using ecryptfs.
I understand; the issue is that the structure of these pam
My likewise was also from a different source. I don't know if likewise-
open does this.
We don't seem to have any reports from likewise-open users, so perhaps
it's reasonable to revert to the original 0ubuntu2, close this out, and
leave this as a record for other people using third-party likewise
Tested /etc/pam.d/common-session with session [success=ok
default=ignore] pam_lsass.so against the packaged version of
/etc/pam.d/lightdm and it works fine.
I will notify PowerBroker of this bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Here's the requested files.
** Attachment added: 1162836.tar.gz
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1162836/+attachment/3617888/+files/1162836.tar.gz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in
The following lightdm pam file seems to resolve my problem, and
hopefully resolves 952185 as well. It's the same as the 0ubuntu1 file,
except that it also reads the user environment after session start.
Would this resolve 952185? Any problems this would introduce?
** Attachment added: lightdm
On 2013-04-03 16:26, Ayecee wrote:
... It's the same as the 0ubuntu1 file, except that it also reads the
user environment after session start.
Would this resolve 952185?
Yes, it would. But Steve is the decision maker here. There may be a
better way to make everyone happy. ;-)
--
You
I had the same problem since the lightdm update but my symptom was more
disrupting : my Unity session was switched to english instead of my
default setting (french).
Using patch in comment #3 works for me.
I think this bug should get a high priority.
--
You received this bug notification
Claude,
Can you please let us know the output of these commands in a terminal
window:
cat /etc/default/locale
cat ~/.pam_environment
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
In /etc/pam.d/common-session, the line:
session sufficient pam_lsass.so
... is broken. sufficient means that no further modules will be
considered, short-circuiting any further modules in the stack.
This is absolutely incompatible with the need to stack pam_env *after*
Gunnar,
Not at my usual workstation right now but from what I remember
/etc/default/locale and ~/.pam_environment are the same and looks fine
(settings to french language).
Steve's comment is interesting : our setup is with PBIS 7 (the successor
of likewise-open) and it was installed with the
That does seem to fix the path, both for regular users and for root via
sudo.
Locale still isn't set though. I forgot to mention this in the first
report. Though /etc/default/locale contains LANG=en_CA.UTF-8, this
isn't reflected in locale output. This is another problem that
downgrading
Ok, thanks.
What you say about the locale indicates that your home directory is
encryptfs protected, and that you have a ~/.pam_environment file that
overrides /etc/default/locale. In that case it's just as it should be.
In other words: it was wrong before on encrypted HOMEs and right now.
Since
This is using whole-disk encryption, not using encryptfs. There is no
~/.pam_environment. However, the system has likewise installed, a
package that allows it to be part of an AD domain, and that probably
interacts with pam somehow. That's the only really unusual thing, I
think.
Do you have the
Hmm... This tends to become complicated for a simple contributor as
myself. ;-)
Anyway, I attach the 0ubuntu1 version of /etc/pam.d/lightdm. Basically,
as you can see when you compare, the change consists of two lines in the
beginning that were moved to the end.
** Attachment added:
Ayecee,
Can you please attach /etc/environment, /etc/default/locale,
/etc/pam.d/lightdm, and all of /etc/pam.d/common-* from the system where
you're able to reproduce this bug? (So, the confirmed-broken
combination of these files, not a version of /etc/pam.d/lightdm from
lightdm 1.2.3-0ubuntu1)
Hi Ayecee!
Thanks for your help to improve Ubuntu by reporting this issue!
The difference between version 1.2.3-0ubuntu1 and 1.2.3-0ubuntu2 of
lightdm is a fix of bug 952185, so you kind of make me feel a culprit
here. ;-) OTOH I can't reproduce the problem; for me /etc/environment is
read just
I downgraded to 1.2.3-0ubuntu1 on 03/20 according to my dpkg.log, and
removed -proposed from my sources as I couldn't see where to report the
bug at the time.
When 0ubuntu2 hit -updates, lightdm upgraded again, and _this_ time it
looks like I downgraded to 1.2.1-0ubuntu1.
So, it was both :)
--
Ok, so it seems the problem is related to the 1.2.3-0ubuntu2 fix, after
all.
For testing purposes, can you please upgrade again, replace
/etc/pam.d/lightdm with the attached file, and let us know if that makes
a difference.
** Attachment added: /etc/pam.d/lightdm
20 matches
Mail list logo
