iceweasel insted ao firefox

cynwulf · 01-26-2012, 07:39 AM

As you haven't stated which version of Iceweasel or Debian this is, there's not much to go on.

You get "updating bookmarks" and such like, because both Iceweasel and Firefox will be sharing the same user space configuration files. So every time you start Firefox up after starting Iceweasel the program detects that there has been an "update".

jford_oldman · 01-26-2012, 05:12 PM

Jens -

You're on to something, I think. Starting FF in safe mode twice, it seems to be behaving like Iceweasel. Now I just have to figure out why. Thank you.

Caravel -

I did report versions. Re-read the message. I think it pretty clearly (although verbosely) says that the Wheezy system - the one showing the strange behavior - is using Iceweasel 8. I started seeing the unusual behavior when Firefox upgraded from 7 to 8, and kept behaving strangely after upgrading to 9. Right now, my FF shows 9.01

I am not aware of more detailed version information.

Jens -

Just for "closure" --- I've restarted Firefox twice in safe mode without encountering the incredibly slow image loading.

I think checked for add-ons, and removed "Test Pilot". It was the only Add-on (and I only have the Java 1.6.0.26 and Shockwave Flash 10.3 r138 plugins. I've started and stopped several times and it seems to be cured.

Thank you very much.

craigevil · 01-26-2012, 09:39 PM

Quote:

Here's the craziest part - if I run Iceweasel, exit it, and run Firefox - it first goes through a "updating bookmarks" and then runs without the freezing. If I stop FF, then run it again, the freezing is back. If I run Iceweasel, I get the same "updating bookmarks" message, and no freezing. Stop, run FF - no freezing. Stop, run FF - freezing.

That sounds like you are using the same profile for both Iceweasel and Firefox. Which can and most likely will cause these type of issues. Create a separate profile for each Icweasel/Firefox versions that you use.

jford_oldman · 01-26-2012, 10:08 PM

Craigevil - I returned to see what new had been posted, using my "cured" Firefox - only to have it freeze while loading the LQ page.
After reading your comments, I created a new profile for Firefox, and after restarting, it seems OK. But this time I'll test more thoroughly before declaring the problem solved.

Any thoughts on why sharing a profile would cause such a problem only for FF, not Iceweasel?

craigevil · 01-26-2012, 11:36 PM

If the versions are the same it 'shouldn't' cause any issues, you tend to get problems when one or the other upgrades and the other one doesn't. Hard to tell what the exact differences are other than version numbering.

I have iceweasel installed, as well as Firefox downloaded from Mozilla, haven't really noticed any differences. They do have their own profile, I also keep a testing profile for when I feel like messing around with the Nightlies.

$ apt-cache policy iceweasel
iceweasel:
Installed: 9.0.1-1
Candidate: 9.0.1-1

linux4life88 · 01-27-2012, 08:46 PM

In my own personal experience I've found Iceweasel to perform and behave the same as Firefox. The only difference is a better name and a 'cooler' looking logo, no pun intended.

jford_oldman · 01-31-2012, 09:10 PM

I now have two profiles - default and Firefox. Starting Firefox with only the "Firefox" profile still doesn't cure the extremely slow loading of images issue. It even happens when accessing THIS website. And my last Iceweasel update gave me version 9.0.1 - which is the version of Firefox I'm running, I believe.
Would you know an easy way to compare the "about:config" info of one with the other?