MASTER Add-ons are broken after 2.0.0.5 upgrade

[Fabio Ornellas]

Binary package hint: firefox

After the 2.0.0.4 to 2.0.0.5 upgrade, all add-ons stopped working. I can not even uninstall them. The only fix I could find was to move the ~/.mozilla/ directory and create a new one from scratch.

I still have the buggy ~/.mozilla/ directory archived for analysis, but I did not send it here because there are a lot of sensible personal information there. I can try to filter this and send only relevant files if more users report this issue.

I can not tell exactly how to reproduce the bug, I started with a fresh Edgy system and made this last update. Here are the add-ons I had installed:

Adblock Plus 0.7.5.1
Bugmenot 1.3
Chromatabs 2.0
Cutemenus Crystal SVG 1.9.1
Firefox Showcase 0.9.3.2
Google Browser Sync 1.3.20070523.0
Google Gears 0.1.54.0
QuickJava 0.4.2.1
Live HTTP Headers 0.13.1

Hope this was a localized bug and does not affect all users...

Thank you.

ProblemType: Bug
Architecture: i386
Date: Fri Jul 20 15:38:55 2007
DistroRelease: Ubuntu 7.04
Package: firefox 2.0.0.5+1-0ubuntu1
PackageArchitecture: i386
SourcePackage: firefox
Uname: Linux morpheus 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

[Guybrush88 (guybrush)]

i also have your problem. i cannot use most of my installed themes along with all my add-ons

[Fabio Ornellas (fabio-ornellas)]

Looks like this is not a safe upgrade at all...

On 7/20/07, Guybrush88 <email address hidden> wrote:
>
> i also have your problem. i cannot use most of my installed themes along
> with all my add-ons
>
> --
> All Add-ons are broken after 2.0.0.5 upgrade
> https://bugs.launchpad.net/bugs/127235
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Fabio Pugliese Ornellas
E-Mail: <email address hidden>
gTalk: <email address hidden>
ICQ: 6516089
MSN: <email address hidden>
WWW: http://ornellas.apanela.com/

[Freddy Martinez (freddymartinez9)]

Thank you for the bug report. I am assigning it to the Mozilla Team for evaluation and hopefully we can fix this relatively shortly.

[islseur (islseur)]

I had my FlashBlock extension stop functioning after the upgrade to 2.0.0.5.

Fixed it by Enabling Javascript in Edit>Preferences>Content>Enable JavaScript

It seems that the update disabled the JavaScript by default, a lot of extensions rely on JavaScript to properly function.

[Fabio Ornellas (fabio-ornellas)]

That's not the point here. Javascript is enabled and things are broken.
Anyway, I believe this setting would affect only web sites, not
extensions...

On 7/21/07, islseur <email address hidden> wrote:
>
> I had my FlashBlock extension stop functioning after the upgrade to
> 2.0.0.5.
>
> Fixed it by Enabling Javascript in Edit>Preferences>Content>Enable
> JavaScript
>
> It seems that the update disabled the JavaScript by default, a lot of
> extensions rely on JavaScript to properly function.
>
> --
> All Add-ons are broken after 2.0.0.5 upgrade
> https://bugs.launchpad.net/bugs/127235
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Fabio Pugliese Ornellas
E-Mail: <email address hidden>
gTalk: <email address hidden>
ICQ: 6516089
MSN: <email address hidden>
WWW: http://ornellas.apanela.com/

[Freddy Martinez (freddymartinez9)]

Fabio, if the extensions use JavaScript to talk to Firefox (which many many extensions do) then it would not work after an upgrade. My guess here is that during the upgrade JS went from enabled to disabled or something similar. As a side note to Alex, I grabbed the 2.0.0.5 .deb off packages.ubuntu.com and I can not reproduce with one extension. If you want me to try more, please ping me on IRC.

[Fabio Ornellas (fabio-ornellas)]

Hello,

I checked out, javascript IS enabled and none of my extensions are working.

As I said, I still have the backup of ~/.mozilla/, I just do not send
it here due to sensible information in it. I can however check / test
anything you need to fix this.

On 7/22/07, Freddy Martinez <email address hidden> wrote:
> Fabio, if the extensions use JavaScript to talk to Firefox (which many
> many extensions do) then it would not work after an upgrade. My guess
> here is that during the upgrade JS went from enabled to disabled or
> something similar. As a side note to Alex, I grabbed the 2.0.0.5 .deb
> off packages.ubuntu.com and I can not reproduce with one extension. If
> you want me to try more, please ping me on IRC.
>
> --
> MASTER All Add-ons are broken after 2.0.0.5 upgrade
> https://bugs.launchpad.net/bugs/127235
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Fabio Pugliese Ornellas
E-Mail: <email address hidden>
gTalk: <email address hidden>
ICQ: 6516089
MSN: <email address hidden>
WWW: http://ornellas.apanela.com/

[Alexander Sack (asac)]

Fabio, can you please re-instantiate your old .mozilla directory and see exactly which extensions are broken? Does reinstalling them from addons.mozilla.org help?

(BTW, please keep the broken .mozilla directory backed-up for now)

Thanks,

 - Alexander

[Freddy Martinez (freddymartinez9)]

Can you please let us know what releases you are on? I can't reproduce this on Gutsy.

[Freddy Martinez (freddymartinez9)]

Oops, nevermind, we have the proper information.

[Fabio Ornellas (fabio-ornellas)]

Alexander,

As I said, I can not even uninstall the extensions. They are all
broken. The only solution I found was to move away ~/.mozilla and
start a new one, that is working.

I guess to reproduce, do what I did might work:

  - Install previous version, create the ~/.mozilla with this version.
  - Install all extensions I had, referred at my first post.
  - Upgrade FF to the newer version and "hope" they are all broken.

I mad many settings customizations, may be one of them "helped" to
break everything. I can not tell.

On 7/22/07, Freddy Martinez <email address hidden> wrote:
> Oops, nevermind, we have the proper information.
>
> --
> MASTER Add-ons are broken after 2.0.0.5 upgrade
> https://bugs.launchpad.net/bugs/127235
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Fabio Pugliese Ornellas
E-Mail: <email address hidden>
gTalk: <email address hidden>
ICQ: 6516089
MSN: <email address hidden>
WWW: http://ornellas.apanela.com/

[Alexander Sack (asac)]

would be great if you could try to reproduce it. If it works, please attach that fresh profile.

[drsandrug (drsandrug-rediffmail)]

The problem was solved by deleting the .mozilla folder in my home folder and reinstalling firefox.it is working fine now.Satyanarayana===================On Sun, 22 Jul 2007 20:38:51 -0000 Bug 127235 wrote Can you please let us know what releases you are on? I can\'t reproduce this on Gutsy. -- MASTER Add-ons are broken after 2.0.0.5 upgrade https://bugs.launchpad.net/bugs/127235 You received this bug notification because you are a direct subscriber of a duplicate bug.

[Fabio Ornellas (fabio-ornellas)]

After the first 2.0.0.5 upgrade available.

Sorry I did not sent a clean .mozilla dir yet, my vacation has ended, I have very little time now...

[Fabio Ornellas (fabio-ornellas)]

Update: Some extensions stopped working with the latest firefox (after my cleanup) which indicates that there might have some buggy code added in this 2.0.0.6 release. I'll try to make a full reproduction scenario when I find time.

By now, one can install the extensions I listed above and then upgrade the the 2.0.0.6 and I believe it will break.

[Fabio Ornellas (fabio-ornellas)]

Well, I found some time. Here is my ~/.mozilla after the upgrade to 2.0.0.6 that broke everything (Ubuntu 7.04 32bit).

I tried to strip out all personal information, hope I did not cut too much. It is still all buggy as it was before.

Things to note:

  - CuteMenus Crystal SVG should render some icons on the menus on the top, they are just text
  - Entering AddOns menu, and clicking to configure any of the extensions, gives to result.

Also, here is my environment (in case my locale generated the bug):

SSH_AGENT_PID=6181
SHELL=/bin/bash
TERM=xterm
GTK_RC_FILES=/etc/gtk/gtkrc:/home/fabio/.gtkrc-1.2-gnome2
WINDOWID=41943119
USER=fabio
LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.avi=01;35:*.fli=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.flac=01;35:*.mp3=01;35:*.mpc=01;35:*.ogg=01;35:*.wav=01;35:
LIBGL_DRIVERS_PATH=/usr/lib/dri
SSH_AUTH_SOCK=/tmp/ssh-ajKkFu6139/agent.6139
GNOME_KEYRING_SOCKET=/tmp/keyring-KGMM5f/socket
SESSION_MANAGER=local/morpheus:/tmp/.ICE-unix/6139
USERNAME=fabio
PATH=/home/fabio/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
DESKTOP_SESSION=default
GDM_XSERVER_LOCATION=local
PWD=/home/fabio
LANG=pt_BR.UTF-8
GDMSESSION=default
HISTCONTROL=ignoreboth
SHLVL=1
HOME=/home/fabio
LANGUAGE=pt_BR:pt:en
GNOME_DESKTOP_SESSION_ID=Default
LOGNAME=fabio
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-lrgDAeytqU,guid=a979783621f5b89fb197bd0046be48e7
LESSOPEN=| /usr/bin/lesspipe %s
DISPLAY=:0.0
LESSCLOSE=/usr/bin/lesspipe %s %s
COLORTERM=gnome-terminal
XAUTHORITY=/home/fabio/.Xauthority
_=/usr/bin/env

Hope this helps.

Thank you.

[Daniel Hahler (blueyed)]

Any chance that this is a duplicate of bug 65609?
There's a workaround provided there and it's currently blocking FF3 (but has affected FF2 already).

[Alexander Sack (asac)]

if this is still an issue for ffox2 then we wont see a fix for that.