Brave Browser shows errors

General Help
1

When I launch brave-browser via the terminal, I see this error on my Zorin 18.1 Core system:

[3566:3585:1003/074635.681207:ERROR:crypto/nss_util.cc:377] After loading Root Certs, loaded==false: NSS error code: -8018

Brave-browser works (it is version 1.96.60), I don't notice a problem.
Is it a critical error? How to solve the problem? I appreciate any help.

I often see this error, too:

[8241:1:1003/085617.946298:ERROR:third_party/puffin/src/puffpatch.cc:122] Failed to create a temporary file for memory-mapping: Operation not permitted

2

nah if brave opens and works those lines are mostly noise.

NSS -8018 after loading Root Certs shows up a lot on ubuntu-ish builds. usually means the browser couldnt refresh the system cert store the way it wanted. not critical when browsing is fine.

the puffin temporary file "Operation not permitted" is often the sandbox fighting a temp map. also harmless when pages load.

id only dig if sites start failing TLS or updates croak. then try:
-brave://settings/help and let it finish an update
-or reinstall the brave package from their apt repo

no need to chase those stderr lines day to day.

3

Using the error message in Brave search engine via Mojeek gives:

" This error log indicates that the application failed to initialize the Network Security Services (NSS) cryptographic library, specifically during the loading of root certificates or PKCS#11 modules. The error originates from crypto/nss_util.cc at line 377, which is part of the Chromium-based rendering engine (used by browsers like Chrome, Edge, Brave, and Electron apps).

Common Causes and Solutions:

  • Corrupted or Missing Certificate Store : The system's NSS database (/etc/pki/nssdb on Linux or the user profile on Windows/Mac) may be empty or corrupted.

    • Fix : Rebuild the certificate store using certutil or reinstall the browser/application.

  • Outdated NSS Library : An old version of NSS may lack support for modern TLS protocols or cipher suites, causing handshake failures.

    • Fix : Update nss , libnss3 , and curl packages via your system package manager (e.g., sudo apt update && sudo apt upgrade nss libnss3 ).

  • Permission Issues : The application may not have read access to the security modules or database files.

    • Fix : Ensure the user has appropriate permissions for /etc/pki/nssdb or the application's data directory.

  • Conflicting Libraries : On Windows, loading OpenSSL before NSS can cause initialization failures.

    • Fix : Ensure the application loads NSS libraries first or updates to the latest version where this race condition is patched.

If this error occurs in a specific application (e.g., a Discord bot, a custom Electron app), updating that application to its latest version often resolves underlying NSS compatibility issues.

AI-generated answer. Please verify critical facts."

4
1 Like
5

I have read the A.I. answers of my browser search, too, but I prefer an answer from an experienced real human being user. I already reinstalled brave-browser and updated the entire system, it is now running the .61 version of brave, but still the same. If it doesn't matter, then I don't have to care because of the error lines.