Bug 2075851 - Fedora 36 beta Firefox content process crash in NSS
Summary: Fedora 36 beta Firefox content process crash in NSS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: opencryptoki
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Horák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 2081640 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-15 17:10 UTC by Emilio Cobos Álvarez (:emilio)
Modified: 2022-05-12 17:02 UTC (History)
20 users (show)

Fixed In Version: opencryptoki-3.17.0-7.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-07 04:28:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
coredump stack (5.10 KB, text/plain)
2022-04-15 17:10 UTC, Emilio Cobos Álvarez (:emilio)
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-432 0 None None None 2022-04-19 13:03:31 UTC

Description Emilio Cobos Álvarez (:emilio) 2022-04-15 17:10:17 UTC
Created attachment 1872810 [details]
coredump stack

Description of problem: When opening system firefox after updating my laptop in Fedora 36 (I usually use Nightly), tab crashes. This doesn't happen with the Mozilla official builds. Restoring the tab seems to avoid it crashing again.

Version-Release number of selected component (if applicable): 99.0.1 (64-bit)


How reproducible: Always

Steps to Reproduce:
1. Open Firefox

Actual results: Your tab crashed.

Expected results: It doesn't?

Additional info:

See gdb stack above. Crash report: https://crash-stats.mozilla.org/report/index/60c7e227-6e7e-4aa4-bf24-583a40220415

It's failing when initializing system nss, in a similar fashion as bug 2074587, inside the gtprgnam("pkcs11") call.

In __GI___nss_lookup ni is 0x7fffbe8ae728, but *ni is null, and that gets dereferenced in __GI___nss_lookup_function.

Comment 1 Emilio Cobos Álvarez (:emilio) 2022-04-15 17:11:24 UTC
Martin is this known? If not is there something I can do to help diagnose?

Comment 2 Martin Stransky 2022-04-19 12:57:03 UTC
Let's move to NSS for further investigation.

Comment 3 Bob Relyea 2022-04-19 16:19:43 UTC
Moving to p11-kit. The crash is in p11-kit, trying to look up an function in the other NSS (Name Switch System).

Comment 4 Daiki Ueno 2022-04-19 18:04:52 UTC
The crash is in a PKCS#11 module loaded by p11-kit, as p11-kit does not call getpwnam by itself. I suspect it is opencryptoki from the symbols appear in the backtrace:
https://github.com/opencryptoki/opencryptoki/blob/c1c32776bff81acfea8a1e1cb8d7c9751a5cd520/usr/lib/api/api_interface.c#L353

Comment 5 Emilio Cobos Álvarez (:emilio) 2022-04-19 18:09:15 UTC
Note that I also hit another issue with that package after the update, reported as bug 2074587. This crash happened after working around that as described there.

Comment 6 Fedora Update System 2022-04-20 08:46:34 UTC
FEDORA-2022-158ea10931 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-158ea10931

Comment 7 Fedora Update System 2022-04-20 15:31:07 UTC
FEDORA-2022-158ea10931 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-158ea10931`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-158ea10931

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2022-05-07 04:28:01 UTC
FEDORA-2022-158ea10931 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Dan Horák 2022-05-10 18:18:36 UTC
*** Bug 2081640 has been marked as a duplicate of this bug. ***

Comment 10 Dominik Drazyk 2022-05-10 22:00:34 UTC
I've updated my Fedora 36 install with latest packages, but I am still unable to use Firefox extensions. Every time I use an extension dmesg reports:

WebExtensions[5979]: segfault at 0 ip 00007f0b6b51581d sp 00007ffdfc714c70 error 4 in libc.so.6[7f0b6b403000+173000]
Code: 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 f3 0f 1e fa 41 55 49 89 fd 41 54 49 89 f4 55 48 89 d5 53 48 89 cb 48 83 ec 08 48 8b 07 <48> 8b 38 48 85 ff 74 1b e8 86 1d 00 00 48 89 03 48 85 c0 74 15 48

Comment 11 Dan Horák 2022-05-12 15:49:38 UTC
(In reply to Dominik Drazyk from comment #10)
> I've updated my Fedora 36 install with latest packages, but I am still
> unable to use Firefox extensions. Every time I use an extension dmesg
> reports:

including the latest opencryptoki update? Does the workaround from https://bugzilla.redhat.com/show_bug.cgi?id=2074587#c5 fix your problem?

Comment 12 Dominik Drazyk 2022-05-12 17:02:29 UTC
Hi Dan,
I've installed recent updates today, run `dnf distro-sync` to have all packages aligned with upstream, but that doesn't help with segfaults. I have version 3.17.0-7.fc36 of opencryptoki installed on my system and it's the main problem. Once I remove the package no more segfaults for me.


Note You need to log in before you can comment on or make changes to this bug.