Description of problem: After upgrade to most recent issue (as found in updates 2016-06-04 apx 11:00 AM CEST) on two f23 hosts I get the following response when issuing the 'xemacs' command in a console: [eha@theta ~]$ xemacs *** Error in XEmacs initialization (tls-error "NSS unable to disable SSLv2" "SEC_ERROR_INVALID_ARGS") *** Backtrace really-early-error-handler((tls-error "NSS unable to disable SSLv2" "SEC_ERROR_INVALID_ARGS")) *** Killing XEmacs Version-Release number of selected component (if applicable): 21.5.34-13.20160507hgd5b51c618ef8.fc23 How reproducible: Always Steps to Reproduce: 1. start xemacs in console 2. 3. Actual results: Does not start and displays this message: *** Error in XEmacs initialization (tls-error "NSS unable to disable SSLv2" "SEC_ERROR_INVALID_ARGS") *** Backtrace really-early-error-handler((tls-error "NSS unable to disable SSLv2" "SEC_ERROR_INVALID_ARGS")) *** Killing XEmacs Expected results: xemacs is started Additional info:
Hi Erik, This was actually caused by an nss update that was probably installed at the same time that you got the latest xemacs update. See bug 1342158 for details, and information on a new update that fixes the problem. In addition, I did a new build of xemacs yesterday that fixes the problem as well. You can see that update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-4df5002763. If you try it out, please leave karma. Thank you! *** This bug has been marked as a duplicate of bug 1342158 ***
(In reply to Jerry James from comment #1) Hi Jerry Thanks for your prompt response. I have updated with the new nss package on one of the hosts, and it solved the problem there. Thank you.