Package: sssd-ad Version: 1.13.3-1+b1 Severity: important The system is a samba 4 AD domain member, configured with sssd. After a packages update about a week ago, I found I could no longer login with lightdm. However I'm still aboe to login with a console (i.e. tty1).
A local accound just works whatever I use lightdm or a console. I finally found that the update process switched sssd* from 1.12 (I guess) to 1.13. I had to edit /etc/sssd/sssd.conf and add the following line in the section related to my domain : ad_gpo_access_control = disable As sssd.conf is not provided in the packages, I think a warning should be displayed during the update. I did not took time to check the changelog of sssd to determine if the ad_gpo* settings are new or changed their behavior between the old version and the new one (because I was not aware if the exact version I had before upgrading). -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages sssd-ad depends on: ii libbasicobjects0 0.5.0-1 ii libc6 2.22-3 ii libcollection4 0.5.0-1 ii libcomerr2 1.42.13-1 ii libdhash1 0.5.0-1 ii libini-config5 0.5.0-1 ii libk5crypto3 1.13.2+dfsg-5 ii libkrb5-3 1.13.2+dfsg-5 ii libldap-2.4-2 2.4.42+dfsg-2+b2 ii libpopt0 1.16-10 ii libref-array1 0.5.0-1 ii libsasl2-2 2.1.26.dfsg1-14+b1 ii libsmbclient 2:4.3.6+dfsg-1 ii libsss-idmap0 1.13.3-1+b1 ii libtalloc2 2.1.5-2 ii libtevent0 0.9.28-1 ii samba-libs 2:4.3.6+dfsg-1 ii sssd-ad-common 1.13.3-1+b1 ii sssd-common 1.13.3-1+b1 ii sssd-krb5-common 1.13.3-1+b1 sssd-ad recommends no packages. sssd-ad suggests no packages. -- no debconf information
