[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lightdm (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same issue. Lightdm fails to auth LDAP user, same account works via SSH.
/var/log/lightdm/lightdm.log:[+700210.55s] DEBUG: Authenticate result for user
user: Success
/var/log/lightdm/lightdm.log:[+700210.55s] DEBUG: User user authorized, but
no account of that name exists
User sees Incorrect
Dear Robert,
Thank you for you answer.
The text login works 100% of the time.
Your question about the local user is interesting.
The home directory is created at the first login, but my problem arises even if
the directory exists.
There is no error in /var/log/auth.log
My intuition is that
Other things that may help debugging:
- Contents of /etc/pam.d (i.e. your PAM configuration)
- If you can log in with another display manager (e.g. gdm) fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There shouldn't be any local caching in lightdm, since it just calls
getpwnam() to get the user information. To me that hints that perhaps
/etc/passwd hasn't been completely written to disk by PAM with the new
user at the point lightdm reads it via getpwnam(). I'm not sure if
getpwnam() is reading
I can't login using gdm (gdm display the busy icon forever).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237306
Title:
lightdm + LDAP login intermitent fail
To manage notifications about this
** Attachment added: pam.d directory
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1237306/+attachment/3870885/+files/pam.d.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237306
Oops, I missed your comment #7...
The user is never added to the /etc/passwd file, but it is accessible using
getent passwd.
getpwnam probably uses the same access for getting the passwd name.
however the man page of getpwnam is interesting:
...
The return value may point to a static area, and
It seems that some tests in ~lightdm-team/lightdm/1.2 : /src/accounts.c
(revision 1526) are strange:
example, in the accounts_get_user_by_name (const gchar *username)
if (!user errno != 0)
g_warning (Unable to get information on user %s: %s, username,
strerror (errno));
should be
** Attachment added: lightdm log when working
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1237306/+attachment/3868691/+files/lightdm.log.work
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: lightdm log when bugging(3 successive attemps)
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1237306/+attachment/3868686/+files/lightdm.log.bug
** Description changed:
Sometimes (often) LDAP users fails to log using lightdm.
When this happens, lightdm shows
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1237306
Title:
lightdm + LDAP login intermitent fail
To manage notifications about this bug
The attachment /etc/init/lightdm.conf workaround seems to be a patch.
If it isn't, please remove the patch flag from the attachment, remove
the patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
The log indicates that LightDM completed the pam_authenticate() but the
local user account was not created after this function returned. LightDM
can't actually start the session because it can't set the appropriate
environment variables based on the username (home directory etc).
This suggests a
14 matches
Mail list logo
