On Mon, Feb 06, 2017 at 02:50:27PM +0200, Timo Aaltonen wrote: > On 06.02.2017 12:49, Jonathan McDowell wrote: > > Package: sssd > > Version: 1.50.0-2 > > Severity: grave > > > > I updated my stretch system this morning which led to it failing to > > reach a login prompt; the system would start up and then avahi-daemon, > > ModemManager and NetworkManager would all fail to start, then > > systemd-logind would fail. This repeated in a continuous loop. Initially > > suspecting ModemManager or NetworkManager I tried removing them (the > > machine has wired ethernet, configured via /etc/network/interfaces), but > > this did not help. > > > > Looking at the errors provided by systemd in my logs led me to: > > > > https://lists.debian.org/debian-user/2017/02/msg00025.html > > > > which provided the clue I needed to try downgrading ssd from 1.15.0-2 > > (which was pulled in by the update this morning) to 1.14.2-1 (the > > previously installed version). The machine subquently rebooted cleanly. > > > > A coworker's machine was similiarly affected, and the same solution > > worked there. > > This is now fixed in 1.15.0-3 which had to wait for -2 to migrate first. > > Sorry for the inconvenience, the easiest way to restore sanity while you > wait for -3 is to remove /etc/systemd/system/sssd.service.wants.
Demoting #854048 to "so that sssd can automigrate" seems to me to be abuse of the bug severity; this bug caused serious problems logging in for users of sssd and the package should not have migrated to testing. The existence of a work around is not a sufficient reason to do so; systems that ended up with the upgraded package would end up not coming up to a login prompt with an unclear root cause. J. -- "Scattered f***ing showers my ass." -- Noah
