Bug#804060: How to track down problems with iceweasel

[Diederik de Haas]

Just like in all your other bugs regarding *your* iceweasel problem (it works 
fine for me and others), I'm quite convinced the problem is with your system, 
not iceweasel or any of the other dozen packages you filed bugs against.

First of all, try to reproduce it with a Debian stock kernel instead of your 
own custom compiled experimental kernel.

Secondly, have I mentioned before that having unstable, testing, stable and 
old-stable at priority 500 doesn't make sense at all? There can be legitimate 
reasons for using several different releases. But then it's very likely you'd 
use things like APT-Pinning to specify *different* priorities for different 
releases. In any case, having both old-stable and unstable on one system is 
essentially pure madness. Especially during this release cycle where the whole 
unstable archive has been recompiled against GCC-5 and those packages are now 
also part of testing ... but not stable and certainly not unstable.

Thirdly, you have a WHOLE bunch of extensions installed.
So next to using a Debian stock kernel, you should disable ALL your extensions 
and see whether you still have the problem. If you don't, which I expect, then 
you can enable your extensions one by one to see if one of your extensions is 
the cause of your issue.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-mozilla-maintainers/attachments/20160114/823f5da9/attachment.sig>