I've tested Ty's 4.4 kernel from comment #78 and can confirm it has let me log in with an LDAP user. Uname: Linux M3520 4.4.0-119-generic #143+lp1759920.1 SMP Wed Apr 4 21:32:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
version_signature: Ubuntu 4.4.0-119.143+lp1759920.1-generic 4.4.114
cmdline: BOOT_IMAGE=/vmlinuz-4.4.0-119-generic root=/dev/mapper/ubuntu--vg-root ro
dmesg: microcode: CPU0 sig=0x906e9, pf=0x20, revision=0x84 microcode: CPU1 sig=0x906e9, pf=0x20, revision=0x84 microcode: CPU2 sig=0x906e9, pf=0x20, revision=0x84 microcode: CPU3 sig=0x906e9, pf=0x20, revision=0x84 microcode: CPU4 sig=0x906e9, pf=0x20, revision=0x84 microcode: CPU5 sig=0x906e9, pf=0x20, revision=0x84 microcode: CPU6 sig=0x906e9, pf=0x20, revision=0x84 microcode: CPU7 sig=0x906e9, pf=0x20, revision=0x84 microcode: Microcode Update Driver: v2.01 <email address hidden>, Peter Oruba
I've tested Ty's 4.4 kernel from comment #78 and can confirm it has let me log in with an LDAP user.
Uname:
Linux M3520 4.4.0-119-generic #143+lp1759920.1 SMP Wed Apr 4 21:32:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
version_signature: 143+lp1759920. 1-generic 4.4.114
Ubuntu 4.4.0-119.
cmdline: IMAGE=/ vmlinuz- 4.4.0-119- generic root=/dev/ mapper/ ubuntu- -vg-root ro
BOOT_
dmesg:
microcode: CPU0 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU1 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU2 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU3 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU4 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU5 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU6 sig=0x906e9, pf=0x20, revision=0x84
microcode: CPU7 sig=0x906e9, pf=0x20, revision=0x84
microcode: Microcode Update Driver: v2.01 <email address hidden>, Peter Oruba