Closed
Bug 1122524
Opened 9 years ago
Closed 9 years ago
Some addons not working with FF35, e.g. Adblock Plus
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1079355
People
(Reporter: werner, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/31.0 Build ID: 20150108202552 Steps to reproduce: Update to FF35 with my addons like Adblock Plus and Element Hiding Helper for Adblock Plus. Actual results: There is *no* addon check then but on the command line I see: 1421415437667 addons.xpi ERROR Failed to load bootstrap addon elemhidehelper@adblockplus.org from /suse/werner/.mozilla/firefox/test/extensions/elemhidehelper@adblockplus.org.xpi: [Exception... "Unexpected error in XPConnect" nsresult: "0x80570008 (NS_ERROR_XPC_UNEXPECTED)" location: "JS frame :: resource://gre/modules/addons/XPIProvider.jsm :: XPI_loadBootstrapScope :: line 4307" data: no] Stack trace: XPI_loadBootstrapScope()@resource://gre/modules/addons/XPIProvider.jsm:4307 < XPI_callBootstrapMethod()@resource://gre/modules/addons/XPIProvider.jsm:4408 < XPI_startup()@resource://gre/modules/addons/XPIProvider.jsm:2159 < callProvider()@resource://gre/modules/AddonManager.jsm:208 < _startProvider()@resource://gre/modules/AddonManager.jsm:667 < AMI_startup()@resource://gre/modules/AddonManager.jsm:824 < AMP_startup()@resource://gre/modules/AddonManager.jsm:2402 < AMC_observe()@resource://gre/components/addonManager.js:55 < <file:unknown> Expected results: On update the addons should be checked and if not working FF may search for an update and if not found disable the addon.
Reporter | ||
Comment 1•9 years ago
|
||
I've removed some addons within as test profile with FF34.0.5 and open a larger session. My session save by FF34.0.5 will not be restored with FF35 and this is a nogo. The History -> Restore Previous Session does do exactly nothing. Switching back to FF34.0.5 restores the missed session.
Reporter | ||
Comment 2•9 years ago
|
||
Also I can not do a Quit from File -> Quit nor a Ctrl-Q
Reporter | ||
Comment 3•9 years ago
|
||
Just updated HTTPS-EveryWhere and then disabled it. With this a quit shows on the command line 1421417069888 addons.xpi ERROR Failed to load bootstrap addon the-addon-bar@GeekInTraining-GiT from /suse/werner/.mozilla/firefox/test/extensions/the-addon-bar@GeekInTraining-GiT.xpi: [Exception... "Unexpected error in XPConnect" nsresult: "0x80570008 (NS_ERROR_XPC_UNEXPECTED)" location: "JS frame :: resource://gre/modules/addons/XPIProvider.jsm :: XPI_loadBootstrapScope :: line 4307" data: no] Stack trace: XPI_loadBootstrapScope()@resource://gre/modules/addons/XPIProvider.jsm:4307 < XPI_callBootstrapMethod()@resource://gre/modules/addons/XPIProvider.jsm:4408 < XPI_startup()@resource://gre/modules/addons/XPIProvider.jsm:2159 < callProvider()@resource://gre/modules/AddonManager.jsm:208 < _startProvider()@resource://gre/modules/AddonManager.jsm:667 < AMI_startup()@resource://gre/modules/AddonManager.jsm:824 < AMP_startup()@resource://gre/modules/AddonManager.jsm:2402 < AMC_observe()@resource://gre/components/addonManager.js:55 < <file:unknown> 1421417069892 addons.xpi ERROR Failed to load bootstrap addon elemhidehelper@adblockplus.org from /suse/werner/.mozilla/firefox/test/extensions/elemhidehelper@adblockplus.org.xpi: [Exception... "Unexpected error in XPConnect" nsresult: "0x80570008 (NS_ERROR_XPC_UNEXPECTED)" location: "JS frame :: resource://gre/modules/addons/XPIProvider.jsm :: XPI_loadBootstrapScope :: line 4307" data: no] Stack trace: XPI_loadBootstrapScope()@resource://gre/modules/addons/XPIProvider.jsm:4307 < XPI_callBootstrapMethod()@resource://gre/modules/addons/XPIProvider.jsm:4408 < XPI_startup()@resource://gre/modules/addons/XPIProvider.jsm:2159 < callProvider()@resource://gre/modules/AddonManager.jsm:208 < _startProvider()@resource://gre/modules/AddonManager.jsm:667 < AMI_startup()@resource://gre/modules/AddonManager.jsm:824 < AMP_startup()@resource://gre/modules/AddonManager.jsm:2402 < AMC_observe()@resource://gre/components/addonManager.js:55 < <file:unknown> 1421417069896 addons.xpi ERROR Failed to load bootstrap addon {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d} from /suse/werner/.mozilla/firefox/test/extensions/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi: [Exception... "Unexpected error in XPConnect" nsresult: "0x80570008 (NS_ERROR_XPC_UNEXPECTED)" location: "JS frame :: resource://gre/modules/addons/XPIProvider.jsm :: XPI_loadBootstrapScope :: line 4307" data: no] Stack trace: XPI_loadBootstrapScope()@resource://gre/modules/addons/XPIProvider.jsm:4307 < XPI_callBootstrapMethod()@resource://gre/modules/addons/XPIProvider.jsm:4408 < XPI_startup()@resource://gre/modules/addons/XPIProvider.jsm:2159 < callProvider()@resource://gre/modules/AddonManager.jsm:208 < _startProvider()@resource://gre/modules/AddonManager.jsm:667 < AMI_startup()@resource://gre/modules/AddonManager.jsm:824 < AMP_startup()@resource://gre/modules/AddonManager.jsm:2402 < AMC_observe()@resource://gre/components/addonManager.js:55 < <file:unknown>
Reporter | ||
Comment 4•9 years ago
|
||
OK ... after removing Tab Mix Plus I'm able to do a quit ...
Reporter | ||
Comment 5•9 years ago
|
||
... but the session will not restored by FF35
Reporter | ||
Comment 6•9 years ago
|
||
and even without any addon the session stored by FF34.0.5 will not be restarted by FF35
Reporter | ||
Comment 7•9 years ago
|
||
Even with the addon Session Manager the session from FF34.0.05 is not shown in FF35. Also the menu of the addon is broken away. IMHO the FF35 is totally broken
Reporter | ||
Comment 8•9 years ago
|
||
This is what I see with addon Session Manager after switching from 34.0.5 to 35: 1421419565691 addons.xpi ERROR Failed to load bootstrap addon {1280606b-2510-4fe0-97ef-9b5a22eafe30} from /suse/werner/.mozilla/firefox/test/extensions/{1280606b-2510-4fe0-97ef-9b5a22eafe30}.xpi: [Exception... "Unexpected error in XPConnect" nsresult: "0x80570008 (NS_ERROR_XPC_UNEXPECTED)" location: "JS frame :: resource://gre/modules/addons/XPIProvider.jsm :: XPI_loadBootstrapScope :: line 4307" data: no] Stack trace: XPI_loadBootstrapScope()@resource://gre/modules/addons/XPIProvider.jsm:4307 < XPI_callBootstrapMethod()@resource://gre/modules/addons/XPIProvider.jsm:4408 < XPI_startup()@resource://gre/modules/addons/XPIProvider.jsm:2159 < callProvider()@resource://gre/modules/AddonManager.jsm:208 < _startProvider()@resource://gre/modules/AddonManager.jsm:667 < AMI_startup()@resource://gre/modules/AddonManager.jsm:824 < AMP_startup()@resource://gre/modules/AddonManager.jsm:2402 < AMC_observe()@resource://gre/components/addonManager.js:55 < <file:unknown>
Reporter | ||
Comment 9•9 years ago
|
||
Interesting, the session is restored on switching back to 34.0.5 and now I see the entry of the addon Session Manager in the Tools
Comment 10•9 years ago
|
||
Turn on dom.indexeddb.enabled in about:config, and this will start working. :-)
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 11•9 years ago
|
||
(In reply to :Gijs Kruitbosch from comment #10) > Turn on dom.indexeddb.enabled in about:config, and this will start working. > :-) > > *** This bug has been marked as a duplicate of bug 1079355 *** Does this also making the session managment working again? I'd like to use my session across a version update!
Flags: needinfo?(gijskruitbosch+bugs)
Comment 12•9 years ago
|
||
(In reply to Dr. Werner Fink from comment #11) > (In reply to :Gijs Kruitbosch from comment #10) > > Turn on dom.indexeddb.enabled in about:config, and this will start working. > > :-) > > > > *** This bug has been marked as a duplicate of bug 1079355 *** > > Does this also making the session managment working again? I'd like to use > my session across a version update! I don't think that is related; Without any add-ons, my sessions get restored fine, and the builtin session manager doesn't use indexeddb, so shouldn't be affected. Please file a new bug if after turning on dom.indexeddb and using session restore without add-ons like session manager is still broken for you.
Flags: needinfo?(gijskruitbosch+bugs)
You need to log in
before you can comment on or make changes to this bug.
Description
•