Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#54537 - [nss] 3.31 breaks compatibility with safesignidentityclient
Attached to Project:
Arch Linux
Opened by Peter (coolmast) - Thursday, 22 June 2017, 09:31 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 25 June 2017, 14:38 GMT
Opened by Peter (coolmast) - Thursday, 22 June 2017, 09:31 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 25 June 2017, 14:38 GMT
|
DetailsDescription:
Using either nss 3.30.2 or 3.31 works in general. However, after adding safesignidentityclient, browsers making use of nss will hang or crash at startup. Additional info: * Affected version 3.31 * downgrade to 3.30.2-1 fixed the problem Steps to reproduce: - install safesignidentityclient (aur) - modutil -dbdir sql:.pki/nssdb -add "SafeSign" -libfile /usr/lib/libaetpkss.so.3 - start Chromium => will hang/crash |
This task depends upon
Closed by Doug Newgard (Scimmia)
Sunday, 25 June 2017, 14:38 GMT
Reason for closing: No response
Additional comments about closing: Likely problem with unsupported package
Sunday, 25 June 2017, 14:38 GMT
Reason for closing: No response
Additional comments about closing: Likely problem with unsupported package
Comment by Doug Newgard (Scimmia) -
Thursday, 22 June 2017, 15:58 GMT
And you know this is a nss problem instead of a safesignidentityclient problem?