Closed Bug 1677947 Opened 5 years ago Closed 3 years ago

My containers suddenly got disabled in beta

Categories

(Core :: Security, defect)

Firefox 84
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox84 --- affected

People

(Reporter: petcuandrei, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0

Steps to reproduce:

I installed some extensions that use containers like https://addons.mozilla.org/en-US/firefox/addon/temporary-containers/ and https://addons.mozilla.org/en-US/firefox/addon/search-and-switch-containers/
This automatically enabled containers feature. I did this a long time ago.
I updated to the latest beta.

Actual results:

Containers got disabled. See screenshot with about:preferences

Expected results:

Nothing. I still have the container extensions enabled so containers should still be enabled.

As a workaround I disabled both extensions, manually enabled containers and enabled the extensions back.
This issue happened in Nightly also some time ago but now I reported it since it's in Beta.

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Preferences

Assuming that container features were actually disabled and this wasn't just a glitch in the preferences UI, this isn't the right component. Moving. If it was just a glitch in the prefs UI, please move it back.

Johann, who works on containers these days?

Component: Preferences → Security
Flags: needinfo?(jhofmann)
Product: Firefox → Core

They were disabled. Temporary container extension was not working anymore. Same with long press on new tab button.

I saw this two or three times on Release 84.0--container tabs could not be created through the UI or by add-ons. Each time a Firefox restart fixed the problem. This is using the Canonical Firefox build on a Linux computer that gets booted daily. No other issues have been seen on the computer.

For the past week I've been watching more closely to see if Firefox starts with the issue or if it arises later, and the issue hasn't returned.

I don't think anyone really works on containers enough to look into this at the moment :/

cc'ing Luke and Maxx on the chance they're interested in this

Flags: needinfo?(jhofmann)

How can I troubleshoot this locally? It constantly gets disabled. It also removes my old containers. Super frustrating to re-create them.

Bugs for the add-on actually go in its own repo: https://github.com/mozilla/multi-account-containers/issues/

Are addons getting uninstalled (not just disabled) and reinstalled? I can't imagine how that would happen, but on uninstall the Containers add-on does "clean up" the container settings and could result in these symptoms.

Do you use Firefox Sync? If you do, do you have Sync enabled in the Container prefs in about:addons? Are you syncing to another computer, or just a mobile device (which doesn't support containers)? Fishing expedition, but maybe something with sync is making the addon get uninstalled and reinstalled? While these are good questions to explore and answer, putting the answer in a github issue will go further than adding them here.

Flags: needinfo?(petcuandrei)

It's been a while since this last happened. If you are still interested in investigating this see details bellow. I think it can be closed from my end since I can't reproduce it anymore.

I don't think it's a problem with the addon. It's a problem with the API.

Container extension are enabled in about:addons but I can't use them in any way as if the containers API were disabled. The addon is enabled and installed but none of the APIs work. The "Enable Container Tabs" feature is disabled. Normally this gets enabled when you install any container extension.

In order to get this feature back, I disable all container extensions from about:addons and then click the "Enable Container Tabs". After that I re-enable the extensions.

Yes, I use sync.

Flags: needinfo?(petcuandrei)

It removes the containers, not the addons.

We never got to the bottom of this, but given comment 9 I don't think we're going to make any progress.

If the containers themselves are removed but the addon is still present (whether disabled or enabled) then there might be some corruption in the extension storage that is losing data. There shouldn't be any reason to lose your container customizations unless the addon is uninstalled.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: