please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
Login prompt never presented
I'll try to get 17.04 up somewhere and test that as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
Login prompt never presented with ldap login and ldapi set with a
name.
To
I'll try to get 17.04 up somewhere and test that as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libpam-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
Login prompt never presented with ldap login and ldapi
The ldapi:/// worked just fine, as did ldap:// with an IP or a name. And
I don't have an entry in /etc/hosts for the ldap server, I'm really
using DNS. Reboot works just fine, login prompt, and I can login at the
console (and via ssh) with an ldap user.
I'm sorry but I will need the files I
The ldapi:/// worked just fine, as did ldap:// with an IP or a name. And
I don't have an entry in /etc/hosts for the ldap server, I'm really
using DNS. Reboot works just fine, login prompt, and I can login at the
console (and via ssh) with an ldap user.
I'm sorry but I will need the files I
ldapi:/// is a unix socket connection, it shouldn't have a "name" or IP
component. It can optionally take a path component, but usually should
just be left blank.
Could you please attach your /etc/ldap.conf and /etc/ldap/ldap.conf?
Is your ldap server on localhost, or remote on another machine
ldapi:/// is a unix socket connection, it shouldn't have a "name" or IP
component. It can optionally take a path component, but usually should
just be left blank.
Could you please attach your /etc/ldap.conf and /etc/ldap/ldap.conf?
Is your ldap server on localhost, or remote on another machine
I'm taking a look.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libpam-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
Login prompt never presented with ldap login and ldapi set with a
name.
To manage
I'm taking a look.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
Login prompt never presented with ldap login and ldapi set with a
name.
To manage notifications about this bug go
** Changed in: libpam-ldap (Ubuntu)
Status: Invalid => Incomplete
** Changed in: libpam-ldap (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Re-opening. This issue is apparently not version specific.
** Changed in: accountsservice (Ubuntu)
Status: Invalid => New
** Changed in: systemd (Ubuntu)
Status: Invalid => New
** Tags removed: yakkety
--
You received this bug notification because you are a member of Ubuntu
Hummm, apparently Canonical is using the let's-wait-until-the-Ubuntu-
version-mentioned-in-the-bug-report-gets-EOL-so-we-can-close-the-bug-
without-fixing-anything" method for closing bug reports...
After confirming this bug for 2 current releases I give up. Let the bug
remain and let's keep this
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Changed in:
Thank you for the prompt testing. I'm marking a few potential src
packages where the actual issue might lie.
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
Thank you for the prompt testing. I'm marking a few potential src
packages where the actual issue might lie.
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
I have just tested 17.04. The issue remains unchanged. It's not fixed.
** Changed in: libpam-ldap (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676977
I also believe that this issue is related to systemd. I filed this issue
on libpam-ldap because I don't know exactly which systemd service might
be wrong and so don't know exactly what package exactly should be
changed.
"When the login service fails, did you obtain the logs for it to see why
it
If you are dropped to an emergency shell on failure to boot, does name
resolution period work?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libpam-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
Login prompt never
Almost certainly the issue is that login.service is not waiting for
networking before starting, when ldap is configured.
In the screenshot, I see "Failed to start Login Service" and then later
"Started to raise network interfaces".
--
You received this bug notification because you are a member
Finally, is this reproducible with 17.04? Note that 16.10 goes eol in
about 3 months so there is some non-zero cost to trying to fix it there,
if it's already fixed in 16.10.
** Changed in: libpam-ldap (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
For what it's worth, the same version of libpam-ldap has been present in
Ubuntu since (at least) 15.04. So I don't think the bug is in libpam-
ldap.
When the login service fails, did you obtain the logs for it to see why
it failed?
More than likely this is a systemd change, but it's unclear yet.
Almost certainly the issue is that login.service is not waiting for
networking before starting, when ldap is configured.
In the screenshot, I see "Failed to start Login Service" and then later
"Started to raise network interfaces".
--
You received this bug notification because you are a member
If you are dropped to an emergency shell on failure to boot, does name
resolution period work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676977
Title:
Login prompt never presented with ldap
Finally, is this reproducible with 17.04? Note that 16.10 goes eol in
about 3 months so there is some non-zero cost to trying to fix it there,
if it's already fixed in 16.10.
** Changed in: libpam-ldap (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
For what it's worth, the same version of libpam-ldap has been present in
Ubuntu since (at least) 15.04. So I don't think the bug is in libpam-
ldap.
When the login service fails, did you obtain the logs for it to see why
it failed?
More than likely this is a systemd change, but it's unclear yet.
** Attachment added: "syslog as requested"
https://bugs.launchpad.net/ubuntu/+source/libpam-ldap/+bug/1676977/+attachment/4849984/+files/syslog.1.gz
** Changed in: libpam-ldap (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
"Would it be possible for you to give an example configuration to help us
reproduce this issue?"
https://help.ubuntu.com/community/LDAPClientAuthentication
"Are there any logs as well that you could provide?"
Added as an attachement.
"understanding the current ordering on boot and what is
Thank you for taking the time to file a bug report.
Would it be possible for you to give an example configuration to help us
reproduce this issue? Trying to get enough information to at least
reproduce this and then we can start to determine a fix.
Are there any logs as well that you could
28 matches
Mail list logo
