Bug#775645: iceweasel: multiple breakages in FF after upgraded to 35, when taking the old prefs.js)

2015-01-19 Thread Mike Hommey
On Mon, Jan 19, 2015 at 06:36:36PM +0100, Christoph Anton Mitterer wrote:
 retitle 775645 iceweasel: new default of dom.indexeddb.enabled=false in FF35 
 breaks several core functionalities and add-ons
 affects 775645 xul-ext-adblock-plus xul-ext-searchload-options 
 xul-ext-tabmixplus
 stop
 
 Hi.
 
 One of the upstream authors from Tab Mix Plus found out[0], that the
 reason for all these issues is that FF35 changes the value of
 dom.indexeddb.enabled to false.
 Interestingly, FF claims, that this value would have been user
 set (but I've never set it to false).
 
 Setting it back to true and all the add-ons as well as the broken FF
 core functionalities (i.e. auto-fill for username/password) works again.

The default for dom.indexeddb.enabled is and always has been true, since
the pref was added in version 4.0b7. What has changed is that Firefox
UI code uses indexeddb, so if you disabled it before, it didn't affect
the UI, but now it does.

Note that there are other ways for a pref to end up user set besides
being user set. They can end up in that state if an addon flips the
pref. In any case, this is the result of a user action of some sort.

Mike


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#775645: iceweasel: multiple breakages in FF after upgraded to 35, when taking the old prefs.js)

2015-01-19 Thread Christoph Anton Mitterer
On Tue, 2015-01-20 at 07:45 +0900, Mike Hommey wrote: 
 The default for dom.indexeddb.enabled is and always has been true, since
 the pref was added in version 4.0b7. What has changed is that Firefox
 UI code uses indexeddb, so if you disabled it before, it didn't affect
 the UI, but now it does.
Well but something must have activated it,.. I didn't ...


 Note that there are other ways for a pref to end up user set besides
 being user set. They can end up in that state if an addon flips the
 pref. In any case, this is the result of a user action of some sort.
... might be the case... but then we should ideally probably reassign
this ticket to the respective add-on... or do you think it's appropriate
for an add-on to make such changes?


Anyway,.. I think we can leave this open for now (until the upstream fix
gets into Debian) and then close it.

Cheers,
Chris.


smime.p7s
Description: S/MIME cryptographic signature


Bug#775645: iceweasel: multiple breakages in FF after upgraded to 35, when taking the old prefs.js)

2015-01-19 Thread Christoph Anton Mitterer
retitle 775645 iceweasel: new default of dom.indexeddb.enabled=false in FF35 
breaks several core functionalities and add-ons
affects 775645 xul-ext-adblock-plus xul-ext-searchload-options 
xul-ext-tabmixplus
stop

Hi.

One of the upstream authors from Tab Mix Plus found out[0], that the
reason for all these issues is that FF35 changes the value of
dom.indexeddb.enabled to false.
Interestingly, FF claims, that this value would have been user
set (but I've never set it to false).

Setting it back to true and all the add-ons as well as the broken FF
core functionalities (i.e. auto-fill for username/password) works again.


Any ideas how to properly deal with this?


Cheers,
Chris.

[0] http://tmp.garyr.net/forum/viewtopic.php?f=2t=19018p=67433#p67420


smime.p7s
Description: S/MIME cryptographic signature


Bug#775645: iceweasel: multiple breakages in FF after upgraded to 35, when taking the old prefs.js

2015-01-17 Thread Christoph Anton Mitterer
Package: iceweasel
Version: 35.0-1
Severity: important


Hi.

Since I've upgraded to 35, I've experienced multiple issues.

- One of them is the breakage of search load options, which I've
already reported in #775391.

- Another was that the search bar didn't work anymore at all
(i.e. hitting enter and nothing happened at all).
This turned out to be a problem in tab mix plus, which was solved
by the version 0.4.1.6 already in experimental.


But several problems remained, which I first suspected to be tab
mix plus either:
- Undo closing tabs (Ctrl-Shift-t) no longer worked.
- session management (at least with the SM from TM+) didn't work
anymore, neither on restart after crash, nor on loading manually
saved sessions.

I've reported these upstream at:
http://tmp.garyr.net/forum/viewtopic.php?f=2t=19018

I further found out that add block plus stopped working, which
meant:
- adds were shown
- I cannot longer open the preferences of the add on (nothing
happens when I click on the button).
- And everything from add on's page in the add on manager is
displayed broken,... it doesn't display the underscore on the
objects, but  before (see the screenshot for what I mean).



So I came to the suspicion it may not be TM+ and digged deeper:
With a fresh profile everything seems to work fine again,
but it would be really annoying having to start from scratch,
since I have so many settings in FF and all plugins.


Starting FF with an empty .mozilla gives:
$ iceweasel 

(process:12321): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
1421544782793   addons.xpi  WARNException running bootstrap method 
startup on fire...@software.joehewitt.com: TypeError: scope.gcli.addCommand is 
not a function (resource://firebug/gcli.js:126:4) JS Stack trace: 
addcomm...@gcli.js:126:5  registercomma...@gcli.js:132:1  
firebuggclicommands.star...@gcli.js:45:9  
startup@resource://gre/modules/addons/XPIProvider.jsm - 
file:///usr/share/mozilla/extensions/%7Bec8030f7-c20a-464f-9b0e-13a3a9e97384%7D/fire...@bootstrap.js:78:5
  xpi_callbootstrapmet...@xpiprovider.jsm:4436:9  
xpi_star...@xpiprovider.jsm:2159:13  callprovi...@addonmanager.jsm:208:12  
_startprovi...@addonmanager.jsm:667:5  ami_star...@addonmanager.jsm:821:9  
amp_star...@addonmanager.jsm:2399:5  amc_obse...@addonmanager.js:55:7
0 migrated.
console.error: 
  [CustomizableUI]
  TypeError: window.caligon.status4evar is undefined -- 
resource://status4evar/Australis.jsm:166

= everything seems to work again, even Search Load Options, which is why
I'll close that bug shortly after.


Starting FF with my profile (i.e. the one where I get all these
errors shows):
$ iceweasel 

(process:10162): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
1421543699278   addons.xpi  ERROR   Failed to load bootstrap addon 
searchloadoptions@esteban.torres from 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/searchloadoptions@esteban.torres:
 [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:821  
AMP_startup()@resource://gre/modules/AddonManager.jsm:2399  
AMC_observe()@resource://gre/components/addonManager.js:55  file:unknown
1421543699280   addons.xpi  ERROR   Failed to load bootstrap addon 
{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d} from 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}:
 [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:821  
AMP_startup()@resource://gre/modules/AddonManager.jsm:2399  
AMC_observe()@resource://gre/components/addonManager.js:55  file:unknown
console.error: 
  [CustomizableUI]
  Custom widget with id loop-button-throttled does not return a valid node
console.error: 
  [CustomizableUI]
  Custom widget with id loop-button-throttled does not return a valid node

= all the