[Bug]: Metamask extension stuck after entering password

[chuacw]

Describe the bug

After entering the password in the Metamask extension, Metamask gets stuck.
It shows the processing icon(as seen below), but doesn't proceed any further:

Expected behavior

Metamask shows the accounts, or show that the password is wrong.

Screenshots/Recordings

Steps to reproduce

1. Click on Metamask icon, which shows the unlock screen.
2. Enter the password

Error messages or log output

Removing unpermitted intrinsics runtime-lavamoat.js:4223:15
Removing intrinsics.Promise.try sentry-install.js:1:750
Removing intrinsics.Uint8Array.fromBase64 sentry-install.js:1:750
Removing intrinsics.Uint8Array.fromHex sentry-install.js:1:750
Removing intrinsics.%InitialMath%.f16round sentry-install.js:1:750
Removing intrinsics.%SharedMath%.f16round sentry-install.js:1:750
Removing intrinsics.%Uint8ArrayPrototype%.setFromBase64 sentry-install.js:1:750
Removing intrinsics.%Uint8ArrayPrototype%.setFromHex sentry-install.js:1:750
Removing intrinsics.%Uint8ArrayPrototype%.toBase64 sentry-install.js:1:750
Removing intrinsics.%Uint8ArrayPrototype%.toHex sentry-install.js:1:750
Removing intrinsics.%FunctionPrototype%.apply.prototype sentry-install.js:1:750
Tolerating undeletable intrinsics.%FunctionPrototype%.apply.prototype === undefined sentry-install.js:1:750
Removing intrinsics.%FunctionPrototype%.bind.prototype sentry-install.js:1:750
Tolerating undeletable intrinsics.%FunctionPrototype%.bind.prototype === undefined
InstallTrigger is deprecated and will be removed in the future. runtime-lavamoat.js:12786:21
onmozfullscreenchange is deprecated. runtime-lavamoat.js:12786:21
onmozfullscreenerror is deprecated. runtime-lavamoat.js:12786:21
Snow detected a new realm creation attempt in MetaMask. Performing scuttling on new realm. 
Window moz-extension://8f390b5b-893f-4d92-bb30-a4d6d5903d4f/home.html#unlock
use-snow.js:23:14
Snow detected a new realm creation attempt in MetaMask. Performing scuttling on new realm. 
Window moz-extension://8f390b5b-893f-4d92-bb30-a4d6d5903d4f/home.html#unlock
use-snow.js:23:14
Property eval will not be hardened because it is scuttled by LavaMoat protection. Visit https://github.com/LavaMoat/LavaMoat/pull/360 to learn more. sentry-install.js:1:750
unreachable code after return statement ui-0.js:1:26150
unreachable code after return statement ui-0.js:1:31112
unreachable code after return statement ui-0.js:1:33435
unreachable code after return statement ui-0.js:1:95814
unreachable code after return statement ui-0.js:1:96322
unreachable code after return statement ui-0.js:1:100037
WARNING: Missing strong random number source sentry-install.js:1:750
The object notation for `createSlice.extraReducers` is deprecated, and will be removed in RTK 2.0. Please use the 'builder callback' notation instead: https://redux-toolkit.js.org/api/createSlice sentry-install.js:1:750
Content-Security-Policy: The page’s settings blocked a JavaScript eval (script-src) from being executed because it violates the following directive: “script-src 'self' 'wasm-unsafe-eval'” (Missing 'unsafe-eval') runtime-lavamoat.js:10422:15
Content-Security-Policy: The page’s settings blocked a JavaScript eval (script-src) from being executed because it violates the following directive: “script-src 'self' 'wasm-unsafe-eval'” (Missing 'unsafe-eval') runtime-lavamoat.js:4525:30
The Web Console logging API (console.log, console.info, console.warn, console.error) has been disabled by a script on this page.
Use of the orientation sensor is deprecated. runtime-lavamoat.js:12866:22

Detection stage

In production (default)

Version

12.6.2

Build type

Other (please specify exactly where you obtained this build in "Additional Context" section)

Browser

Firefox

Operating system

Windows

Hardware wallet

No response

Additional context

Using Firefox 135.0 (64-bit)

Severity

No response

[danjm]

Hi, thanks for reporting

Users that have experience this in the past have found that fully closing and reopening firefox, or going to about:addons and turning the extension off and then on, fixes this problem

[chuacw]

Thanks! That worked!

So, the Content-Security-Policy errors/warnings are a red herring?
If not, is it possible to get it fixed?

[Gudahtt]

Looks like this may be a duplicate of #29332. Closing. That issue has a fix in-progress now, hopefully we'll have this fixed soon. Please follow that issue for further updates.

And yes, the Content-Security-Policy errors look like a red herring. Good point though, we should be able to fix that as well. I see there is an issue tracking that already here: #25354