Bug 2081640

Summary: Firefox 99.0-1 extensions cause segmentation fault after installing latest Fedora 36 upgrades [@ nss_Init]
Product: [Fedora] Fedora Reporter: Dominik Drazyk <ddrazyk>
Component: opencryptokiAssignee: Dan Horák <dan>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 36CC: crypto-team, dan, elio.maldonado.batiz, erack, gecko-bugs-nobody, jhorak, kai-engert-fedora, kdudka, klaas, ksinny, mschmidt, pjasicek, rhughes, rrelyea, rstrode, sandmann, stransky
Target Milestone: ---Flags: fedora-admin-xmlrpc: mirror+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-10 18:18:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dominik Drazyk 2022-05-04 09:27:31 UTC
Description of problem:
After recent dnf upgrade, all Firefox extensions are causing segmentation fault. If I try to use any of them only a vertical bar is displayed in Firefox instead of a regular extension window. 

Version-Release number of selected component (if applicable):
firefox-99.0-1.fc36.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open Firefox.
2. Click any of the installed extensions.
3. Segfault reported in dmesg.

Actual results:
Extensions are unusable.

Expected results:
Extensions work as usual.

Additional info:
Problem has been reported to ABRT: https://retrace.fedoraproject.org/faf/problems/bthash/?bth=4c3b205f81b2481d0bda58d8e5ebb4a1644957d7

Comment 1 Martin Stransky 2022-05-04 09:43:48 UTC
A crash in /lib64/libnss3.so

Comment 2 Bob Relyea 2022-05-10 15:01:29 UTC
The crash is when opencryptoki calls name switch system. There is a similiar bug out there as well.

Comment 3 Dan Horák 2022-05-10 18:18:36 UTC

*** This bug has been marked as a duplicate of bug 2075851 ***