Comment 1 for bug 1640805

Thanks for your pre-analysis on this Florin.

It seems it is an upstream issue - just as you pointed out with the linked ticket.
And that matches exactly what you report (and makes sense that neither me nor you find one of the changes Ubuntu introduced to be related to the issue).

IMHO this happened this way:
good: 1.11.5-1ubuntu3
> upstream introduced issue, picked up by the bugfix release to 1.11.8 by us
broken: 1.11.8-0ubuntu0.2
> upstream fixed in 1.12.3 according to the ticket.
good: 1.12.5-1~trusty1

I checked on the fixes themself since a bugtracker eventually is only text, but it matches:
$ git tag --contains 79f12880 | head -n 1
sssd-1_12_3
82a958e6 is the same as above but to dev branch
$ git tag --contains 45a089a7 | head -n 1
sssd-1_12_5

So 1.12.5 that you tested from ppa should work and that is what you report.

I doubt we want to pull in all of 1.12.5 into trusty - the whole reasons to pull 1.11.8 (I assume) was that it was meant to be a bugfix only release.

So one has to evaluate if the patches would apply.
While checking that I realized that I accidentally created almost the full fix - so we could as well test it. But since I have no knowledge of sssd nor a setup I need you for that.

So I created a ppa at https://launchpad.net/~paelzer/+archive/ubuntu/trusty-sssd-bug-1640805 and would like to have:
- a verification from you on the ppa
- a comment from Timo as he did the update to 1.11.8