Upgrading to the latest libnss3 (3.23) fixes the problem. Since the bug has been fixed could the maintainers close it?
Thanks
Upgrading to the latest libnss3 (3.23) fixes the problem. Since the bug has been fixed could the maintainers close it?
Thanks