[Bug 127235] Re: MASTER Add-ons are broken after 2.0.0.5 upgrade

2008-04-21 Thread Alexander Sack
if this is still an issue for ffox2 then we wont see a fix for that. ** Changed in: firefox (Ubuntu) Status: Confirmed = Won't Fix -- 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 member of

[Bug 127235] Re: MASTER Add-ons are broken after 2.0.0.5 upgrade

2008-03-16 Thread Daniel Hahler
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). -- 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

[Bug 127235] Re: MASTER Add-ons are broken after 2.0.0.5 upgrade

2007-08-15 Thread 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

[Bug 127235] Re: MASTER Add-ons are broken after 2.0.0.5 upgrade

2007-08-15 Thread 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

[Bug 127235] Re: MASTER Add-ons are broken after 2.0.0.5 upgrade

2007-07-31 Thread 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... -- 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 member

Re :[Bug 127235] Re: MASTER Add-ons are broken after 2.0.0.5 upgrade

2007-07-24 Thread drsandrug
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 - Bug 127235 wrote Can you please let us know what releases you are on? I can\'t reproduce this on Gutsy.

[Bug 127235] Re: MASTER Add-ons are broken after 2.0.0.5 upgrade

2007-07-23 Thread Alexander Sack
would be great if you could try to reproduce it. If it works, please attach that fresh profile. -- 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 member of Ubuntu Bugs, which is the bug contact for

[Bug 127235] Re: MASTER Add-ons are broken after 2.0.0.5 upgrade

2007-07-22 Thread Alexander Sack
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 ** Summary changed: - MASTER All Add-ons

[Bug 127235] Re: MASTER Add-ons are broken after 2.0.0.5 upgrade

2007-07-22 Thread Freddy Martinez
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 member of Ubuntu Bugs, which is the bug contact for Ubuntu. --

[Bug 127235] Re: MASTER Add-ons are broken after 2.0.0.5 upgrade

2007-07-22 Thread Freddy Martinez
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 member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list

Re: [Bug 127235] Re: MASTER Add-ons are broken after 2.0.0.5 upgrade

2007-07-22 Thread 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.