搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Mozilla Firefox snap for Ubuntu changes browser.opaqueResponseBlocking

  • 6 个回答
  • 0 人有此问题
  • 1 次查看
  • 最后回复者为 zeroknight

more options

Why does the Mozilla Firefox snap for Ubuntu keep changing the value of browser.opaqueResponseBlocking away from the default and selected FALSE setting to TRUE? This makes Firefox nearly unusable since the streaming video keeps being cut off when Mozilla Firefox snap for Ubuntu keeps changing the value of browser.opaqueResponseBlocking randomly during use. Specifically this is the 116.0.2 (64-bit) Mozilla Firefox snap for Ubuntu canonical-002 - 1.0 that is installed with Ubuntu 23.04. Please advise.

Why does the Mozilla Firefox snap for Ubuntu keep changing the value of browser.opaqueResponseBlocking away from the default and selected FALSE setting to TRUE? This makes Firefox nearly unusable since the streaming video keeps being cut off when Mozilla Firefox snap for Ubuntu keeps changing the value of browser.opaqueResponseBlocking randomly during use. Specifically this is the 116.0.2 (64-bit) Mozilla Firefox snap for Ubuntu canonical-002 - 1.0 that is installed with Ubuntu 23.04. Please advise.

被采纳的解决方案

Thank you. It seems that Firefox 'studies' Page load time patch was enabled and that appears to be changing browser.opaqueResponseBlocking settings. After opting out of this 'study' and resetting browser.opaqueResponseBlocking settings the problem has not returned.

定位到答案原位置 👍 0

所有回复 (6)

more options

Hi

I am using the Snap myself in Xubuntu 22.04 and do watch videos without a problem. I have not changed any settings in about:config and videos play just fine and are not interupted.

Do you use any add-ons in Firefox?

Have you tried updating the Snap to 116.0.3? Does this help?

more options

You may have an extension which is changing the preference. You could try restarting in troubleshoot mode. It's possible also that your distro imposes a policy or uses an autoconfig file. You could enter about:policies in the address bar to see whether there's anything there.

https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems https://support.mozilla.org/en-US/kb/troubleshoot-issues-related-to-add-ons


https://support.mozilla.org/en-US/kb/customizing-firefox-using-policiesjson https://support.mozilla.org/en-US/kb/customizing-firefox-using-autoconfig

由Terry于修改

more options

@Paul, Thanks. I updated the Snap to 116.0.3, which begs an unrelated question as to why Ubuntu does not update the snaps; however, the behavior is the same. Also ran Firefox in safe mode and the behavior is the same. On a different computer running Ubuntu 22.04, where the default Firefox is not installed with snap, the problem is not present using 116.0.3, so this appears to be either a snap issue or a 23.04 issue. Also, FYI in this context, streaming video is coming from ZoneMinder; however, this is just a symptom, the fact that something is changing the default value of browser.opaqueResponseBlocking is the problem. @Terry, Thanks. No change while Firefox is in safe mode. Checking about:policies shows nothing that could impact this.

more options

browser.opaqueResponseBlocking is currently enabled in early beta and earlier, so it will be true for the first 7 beta builds and then switch to false until the next major version. You can see which channel you are using with the command:

snap info firefox

If you are not using the beta channel, it could be an experimental rollout to detect breakage. You can see if you are involved in an active study by visiting about:studies or a remote feature by visiting about:support#remote-features.

If you are sure this setting alone is breaking ZoneMinder media streaming in a new profile, you should report it on Bugzilla.

more options

选择的解决方案

Thank you. It seems that Firefox 'studies' Page load time patch was enabled and that appears to be changing browser.opaqueResponseBlocking settings. After opting out of this 'study' and resetting browser.opaqueResponseBlocking settings the problem has not returned.

more options

There is no guarantee it will remain optional if breakages are not reported on Bugzilla.