Closed
Bug 698324
Opened 15 years ago
Closed 9 years ago
When switching to a different architecture (x86_64 to i386 on OSX f.e.) we re-enable all plugins
Categories
(Core Graveyard :: Plug-ins, defect)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: pfinette, Unassigned)
References
Details
Attachments
(4 files)
Every time Firefox has to restart in 32 Bit Mode (which in my case is required to use the Garmin Communicator Plug-In) it forgets all enable/disable settings in Add-Ons Manager > Plugins. This permutes back to 64 Bit Mode after another Firefox restart.
Attached screenshot shows my settings before restarting into 32 Bit Mode. After the restart all Plugins become enabled (both in 32 Bit Mode and 64 Bit Mode).
| Reporter | ||
Comment 1•15 years ago
|
||
System Information:
- Firefox 7.0.1 on Mac OS X 10.7.2 (system is up-to-date).
- Installed Add-Ons: Adblock Plus, Last Pass, Priv3, Read It Later, Readability (all through AMO)
- Happens both on an old as well as a completely fresh profile
Comment 2•15 years ago
|
||
Maybe Add-ons Manager Component...
Component: Extension Compatibility → Add-ons Manager
Product: Firefox → Toolkit
QA Contact: extension.compatibility → add-ons.manager
Comment 3•15 years ago
|
||
Pascal, could you provide a webpage which requested a restart in 32 bit mode and the corresponding plug-in?
| Reporter | ||
Comment 4•15 years ago
|
||
(In reply to Virgil Dicu [QA] from comment #3)
> Pascal, could you provide a webpage which requested a restart in 32 bit mode
> and the corresponding plug-in?
Sure - http://strava.com with the Garmin Communicator Plugin (http://www.garmin.com/garmin/cms/site/products/communicator) which is used to upload data wireless from a Garmin GPS sports watch using the Garmin ANT USB Stick.
You can try this out without this setup on the Garmin site itself (you need to install the Garmin Communicator Plugin though):
http://www.garmin.com/garmin/cms/site/products/communicator
(see attached screenshot)
| Reporter | ||
Comment 5•15 years ago
|
||
| Reporter | ||
Comment 6•15 years ago
|
||
Also - there seems to be something else going on: Every time I restart Firefox into 32 Bit Mode (and subsequently into 64 Bit Mode) I get the first run experience from the Priv3 add-on (it opens a tab with some information about the add-on).
Looks like Firefox resets some prefs/settings when restarting into a different bit mode.
Comment 7•15 years ago
|
||
Can you attach copies of pluginreg.dat and prefs.js before and after the restart so we can compare them.
| Reporter | ||
Comment 8•15 years ago
|
||
| Reporter | ||
Comment 9•15 years ago
|
||
| Reporter | ||
Comment 10•15 years ago
|
||
(In reply to Dave Townsend (:Mossop) from comment #7)
> Can you attach copies of pluginreg.dat and prefs.js before and after the
> restart so we can compare them.
Sure thing - done.
Comment 11•15 years ago
|
||
The plugin part of this will have been caused by bug 616271 which throws away the plugin registry (which includes which plugins are disabled) when switching architectures.
Not sure why the pref reset is happening, it seems to be just one pref related to that extension so might just be an extension problem.
Blocks: 616271
Component: Add-ons Manager → Plug-ins
Product: Toolkit → Core
QA Contact: add-ons.manager → plugins
Summary: When restarting Firefox in 32 Bit Mode, Firefox forgets the disable/enable settings in Add-Ons Manager > Plugins → When switching to a different architecture (x86_64 to i386 on OSX f.e.) we re-enable all plugins
Version: 7 Branch → Trunk
Comment 13•14 years ago
|
||
Also seen on Windows, see comment #12.
OS: Mac OS X → All
Hardware: x86 → All
Comment 15•13 years ago
|
||
Note that for use cases like in comment 0 you could use a different profile for the 32bit instance as a workaround.
Comment 16•9 years ago
|
||
Resolving old bugs which are likely not relevant any more, since NPAPI plugins are deprecated.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Updated•4 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•