FS#34719 - [nspr] nspr(4.9.6-1)makes thunderbird build-in security token failed

Attached to Project: Arch Linux
Opened by Zhengjun Zhang (siyanmao) - Wednesday, 10 April 2013, 18:35 GMT
Last edited by Jan de Groot (JGC) - Thursday, 05 September 2013, 07:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Ionut Biru (wonder)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
thunderbird 17.0.5
nspr 4.9.6-1

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
1.enable software security token in thunderbird:
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 05 September 2013, 07:18 GMT
Reason for closing:  No response
Comment by Zhengjun Zhang (siyanmao) - Wednesday, 10 April 2013, 18:45 GMT
Steps to reproduce:
1.enable software security token in thunderbird:
Edit-Preferences-Advanced-Certificates-Security Devices-Enable FIPS
2.restart Thunderbird
3.you will see that:

Could not initialize the application's security component. The most likely cause is problems with files in your application's profile directory. Please check that this directory has no read/write restrictions and your hard disk is not full or close to full. It is recommended that you exit the application and fix the problem. If you continue to use this session, you might see incorrect application behaviour when accessing security features.

downgraded nspr to 4.9.5-1 will solve this problem.

What‘s more,
Architecture: x86_64
Comment by Jan de Groot (JGC) - Friday, 12 April 2013, 13:24 GMT
Can you try to rebuild nss? We've had FIPS bugs before because of the checksum files inside nss that need to match the libraries.
Comment by Zhengjun Zhang (siyanmao) - Sunday, 14 April 2013, 09:28 GMT
Sorry, I don't konw how to build nss.
Comment by Evangelos Foutras (foutrelis) - Friday, 10 May 2013, 21:55 GMT
Please test nss 3.14.3-3; it's been built against nspr 4.9.6.
Comment by Zhengjun Zhang (siyanmao) - Saturday, 11 May 2013, 05:24 GMT
Same problem.

nss:3.14.3-3
nspr:4.9.6-1
Comment by Jan de Groot (JGC) - Friday, 19 July 2013, 07:37 GMT
Is this still an issue with nss/nspr from testing?

Loading...