Comment 2 for bug 1746947

It also seems to have effect on bug 1746948 with corosync postinst.

I only thought "hey nss minor update, why not pull it in", but without help to understand and resolve this I might be forced to go to a 3.35+really3.34 update to go back as I'm not enough of an nss expert to resolve :-/