I'm seeing a lot of problems reported here with the upgrade to 2.0.0.5. 
Mostly it seems about add-ons not working and other features suddenly 
breaking. I got my first upgrade prompt last night and declined it. I 
think I'll continue declining it.

Is there some kind of status page we can look at where known major bugs 
in the current build are listed out in a short list (rather than 
trolling through the bugzilla DB)? Maybe such a place also acknowledges 
that they know it's a bad release and plan to issue a 2.0.0.6 shortly, 
and advise us to not update to 5.

~dd

d d wrote:
> I'm seeing a lot of problems reported here with the upgrade to 2.0.0.5. 
> Mostly it seems about add-ons not working and other features suddenly 
> breaking. I got my first upgrade prompt last night and declined it. I 
> think I'll continue declining it.
> 

> ~dd

There are loads of "problems" reported with the release of every version 
of FF. Mostly they turn out to be operator errors/omissions rather than 
actual bugs in the software (not to say that some aren't actual bugs, of 
course). What you have to bear in mind is that only the people that have 
problems bring them to this newsgroup. The many thousands of us that 
upgrade with absolutely no problem at all don't say so.

Personally, 2.0.0.5 installed itself without hassle and all of my 
add-ons are working. Even RoboForm (which is not strictly and add-on) 
works with the new version.

You can always install .5 to a different directory and keep .4 on your 
hard drive until satisfied that the newer version will work, so what's 
to lose?

-- 
Regards

Steve G

SteveG wrote:

> Personally, 2.0.0.5 installed itself without hassle and all of my 
> add-ons are working. Even RoboForm (which is not strictly and add-on) 
> works with the new version.

Have to agree, both my Win and Linux upgrades went flawlessly and with 
MR Tech installed I'm still using a couple of extension/theme that 
haven't been upgraded by there authors since 1.5.  The only place I seem 
to get probs with Mozilla are with Fx 3.0a6 and Tb 3.0 but I expect that.

-- 
Steve

Eat a live toad the first thing in the morning and nothing worse will 
happen to you the rest of the day.
- Unknown

In article <YqKdnYXEUf0jhwLbnZ2dnUVZ_qninZ2d@mozilla.org>,
   d d <dd_no_spam@please.net> wrote:
> I'm seeing a lot of problems reported here with the upgrade to 2.0.0.5. 
> Mostly it seems about add-ons not working and other features suddenly 
> breaking. I got my first upgrade prompt last night and declined it. I 
> think I'll continue declining it.

> Is there some kind of status page we can look at where known major bugs 
> in the current build are listed out in a short list (rather than 
> trolling through the bugzilla DB)? Maybe such a place also acknowledges 
> that they know it's a bad release and plan to issue a 2.0.0.6 shortly, 
> and advise us to not update to 5.

> ~dd

Quite often addons will get switched off during an update, because they
need tweaking to run with a newer version of FF, but I feel with a little
forthought an FF update/upgrade needn't be a trauma.

I run two Win PCs (Desktop XP and Laptop Vista) and after backing up the
complete 2.0.0.4 install directory and the complete profile directory, I
allowed both machines to Auto update FF 2.0.0.4 to 2.0.0.5 and aside from
the Java Console business already noted, the upgrade went without any
problems.
Re-ran FF and all was okay.

I guess it's inevitable with the very large userbase of FF that some
particular machine setup is going  to cause the occasional upgrade wobbly.

After all, even the official MS OS patches and updates sometimes mess up a
machine until you uninstall them, or they release a patch for the patch.

Cheers
Dave S

-- 

d d wrote:
> I'm seeing a lot of problems reported here with the upgrade to 2.0.0.5. 
> Mostly it seems about add-ons not working and other features suddenly 
> breaking. I got my first upgrade prompt last night and declined it. I 
> think I'll continue declining it.
> 
> Is there some kind of status page we can look at where known major bugs 
> in the current build are listed out in a short list (rather than 
> trolling through the bugzilla DB)? Maybe such a place also acknowledges 
> that they know it's a bad release and plan to issue a 2.0.0.6 shortly, 
> and advise us to not update to 5.
> 
> ~dd

I was using the 2.0.0.5 pre-release nightlies for a week prior to the 
official release and had no problems whatsoever with my add-ons. 
Everything went so well I now use the 2.0.0.6 pre-release nightlies.

Ann

-- 
Remove the FISH from the net to reply

d d wrote:
> I'm seeing a lot of problems reported here with the upgrade to 2.0.0.5. 
> Mostly it seems about add-ons not working and other features suddenly 
> breaking. I got my first upgrade prompt last night and declined it. I 
> think I'll continue declining it.
> 
> Is there some kind of status page we can look at where known major bugs 
> in the current build are listed out in a short list (rather than 
> trolling through the bugzilla DB)? Maybe such a place also acknowledges 
> that they know it's a bad release and plan to issue a 2.0.0.6 shortly, 
> and advise us to not update to 5.
> 
> ~dd

Upgrade went fine. About 3 of my extensions disabled now but that's 
normal - I'll wait for the extension updates to arrive.
Java console message came up, so I went to admin account, updated to new 
Java version, rebooted, back to user account all fine.
WinXP Home.

-- 
Rev Robert M Jones, Wimborne Baptist Church, UK
http://www.wimborne-baptist.org.uk
Free trial of Mailwasher Pro - effective email spam filter - (commission
goes to our partners in Bulgaria)
http://fta.firetrust.com/index.cgi?id=420

SteveG wrote:
> d d wrote:
>> I'm seeing a lot of problems reported here with the upgrade to 
>> 2.0.0.5. Mostly it seems about add-ons not working and other features 
>> suddenly breaking. I got my first upgrade prompt last night and 
>> declined it. I think I'll continue declining it.
>>
> 
>> ~dd
> 
> There are loads of "problems" reported with the release of every version 
> of FF. Mostly they turn out to be operator errors/omissions rather than 
> actual bugs in the software (not to say that some aren't actual bugs, of 
> course). What you have to bear in mind is that only the people that have 
> problems bring them to this newsgroup. The many thousands of us that 
> upgrade with absolutely no problem at all don't say so.
> 
> Personally, 2.0.0.5 installed itself without hassle and all of my 
> add-ons are working. Even RoboForm (which is not strictly and add-on) 
> works with the new version.
> 
> You can always install .5 to a different directory and keep .4 on your 
> hard drive until satisfied that the newer version will work, so what's 
> to lose?
> 
I had trouble yesterday even getting the 2.0.0.5 upgrade yesterday. But 
later found to my misfortune I was directed to the only busted download 
server in the entire server Farm. After repeated tries it finally 
downloaded. Although I haven't used it much because My Primary Browser 
is SeaMonkey. I didn't see any problems once downloaded and operational.

-- 
------------------------------------------------------------------------
Phillip M. Jones, CET                                http://www.vpea.org
If it's "fixed", don't "break it"!            mailto:pjones@kimbanet.com
                              http://www.kimbanet.com/~pjones/default.htm
Mac G4-500, OSX.3.9               Mac 17" PowerBook G4-1.67 Gb, OSX.4.10
------------------------------------------------------------------------

d d wrote:
> I'm seeing a lot of problems reported here with the upgrade to 2.0.0.5. 
> Mostly it seems about add-ons not working and other features suddenly 
> breaking. I got my first upgrade prompt last night and declined it. I 
> think I'll continue declining it.
> 
> Is there some kind of status page we can look at where known major bugs 
> in the current build are listed out in a short list (rather than 
> trolling through the bugzilla DB)? Maybe such a place also acknowledges 
> that they know it's a bad release and plan to issue a 2.0.0.6 shortly, 
> and advise us to not update to 5.
> 
> ~dd

I think the problem is with the automatic upgrade process itself and not 
with the browser version.  I upgraded by downloading the whole Firefox 
version and installing it.  It works fine for me.  The only thing I 
allow Firefox to do about updating is to notify me if updates are 
available for add-ons.

Ever since 2.0.0.x, FireFox has been horrible.  Constant crashing, the 
lost bookmarks, the slower-than-IE speed.  Makes me wonder if Microsoft 
wrote the upgrades:  I'm certainly getting fed up with FireFox.

Anyone know of a way to "downgrade" to v1.xx?  Anyone have a full copy 
of the v1.5x download?
W
PS:  If you have the file and post a link, make sure your server can 
handle a lot of traffic!

d d wrote:
> I'm seeing a lot of problems reported here with the upgrade to 2.0.0.5. 
> Mostly it seems about add-ons not working and other features suddenly 
> breaking. I got my first upgrade prompt last night and declined it. I 
> think I'll continue declining it.
> 
> Is there some kind of status page we can look at where known major bugs 
> in the current build are listed out in a short list (rather than 
> trolling through the bugzilla DB)? Maybe such a place also acknowledges 
> that they know it's a bad release and plan to issue a 2.0.0.6 shortly, 
> and advise us to not update to 5.
> 
> ~dd

Wink wrote:
> Ever since 2.0.0.x, FireFox has been horrible.  Constant crashing, the 
> lost bookmarks, the slower-than-IE speed.  Makes me wonder if Microsoft 
> wrote the upgrades:  I'm certainly getting fed up with FireFox.
> 
> Anyone know of a way to "downgrade" to v1.xx?  Anyone have a full copy 
> of the v1.5x download?
> W
> PS:  If you have the file and post a link, make sure your server can 
> handle a lot of traffic!
> 
> d d wrote:
>> I'm seeing a lot of problems reported here with the upgrade to 
>> 2.0.0.5. Mostly it seems about add-ons not working and other features 
>> suddenly breaking. I got my first upgrade prompt last night and 
>> declined it. I think I'll continue declining it.
>>
>> Is there some kind of status page we can look at where known major 
>> bugs in the current build are listed out in a short list (rather than 
>> trolling through the bugzilla DB)? Maybe such a place also 
>> acknowledges that they know it's a bad release and plan to issue a 
>> 2.0.0.6 shortly, and advise us to not update to 5.
>>
>> ~dd
I cannot form a valid opinion about 2.0. I have uninstalled it for it 
does not allow to communicate easily with TB (and vice-versa) the way I 
do with 1.5. I will forgo the security "improvements" (I rely on 
efficient tools to avoid malware, and so far, so good).

I do have a 1.5 version available, but no site to post it, should this 
prove necessary. But it seems it is available here: 
http://www.mozilla.com/en-US/firefox/all-older.html

Regards
-- 
John Doue

On Jul 19, 2:18 pm, EE <nu...@bees.wax> wrote:
> d d wrote:
> > I'm seeing a lot of problems reported here with the upgrade to 2.0.0.5.
> > Mostly it seems about add-ons not working and other features suddenly
> > breaking. I got my first upgrade prompt last night and declined it. I
> > think I'll continue declining it.
>
> > Is there some kind of status page we can look at where known major bugs
> > in the current build are listed out in a short list (rather than
> > trolling through the bugzilla DB)? Maybe such a place also acknowledges
> > that they know it's a bad release and plan to issue a 2.0.0.6 shortly,
> > and advise us to not update to 5.
>
> > ~dd
>
> I think the problem is with the automatic upgrade process itself and not
> with the browser version.  I upgraded by downloading the whole Firefox
> version and installing it.  It works fine for me.  The only thing I
> allow Firefox to do about updating is to notify me if updates are
> available for add-ons.

I was hesitating for the longest time but finally let Mozilla update
my FF 1.5.0.12 to 2.0.0.4., then to 2.0.0.5.  My computer runs Win98SE
but the install went perfectly, no bugs or problems, just one
extension, Autofill 0.3 is no longer working. I like the automatic
spell checker, will learn the other new features as I require them.

On 2007-07-24, Wink <rwcleary@verizon.net> wrote:

> Ever since 2.0.0.x, FireFox has been horrible.  Constant crashing, the 
> lost bookmarks, the slower-than-IE speed.  Makes me wonder if Microsoft 
> wrote the upgrades:  I'm certainly getting fed up with FireFox.
>
> Anyone know of a way to "downgrade" to v1.xx?  Anyone have a full copy 
> of the v1.5x download?

All the older releases are on the mozilla ftp site: ftp.mozilla.org

-- 

John (john@os2.dhs.org)

Wink wrote:
> Ever since 2.0.0.x, FireFox has been horrible.  Constant crashing, the 
> lost bookmarks, the slower-than-IE speed.  Makes me wonder if Microsoft 
> wrote the upgrades:  I'm certainly getting fed up with FireFox.
> 
> Anyone know of a way to "downgrade" to v1.xx?  Anyone have a full copy 
> of the v1.5x download?
> W
> PS:  If you have the file and post a link, make sure your server can 
> handle a lot of traffic!
> 
> d d wrote:
>> I'm seeing a lot of problems reported here with the upgrade to 
>> 2.0.0.5. Mostly it seems about add-ons not working and other features 
>> suddenly breaking. I got my first upgrade prompt last night and 
>> declined it. I think I'll continue declining it.
>>
>> Is there some kind of status page we can look at where known major 
>> bugs in the current build are listed out in a short list (rather than 
>> trolling through the bugzilla DB)? Maybe such a place also 
>> acknowledges that they know it's a bad release and plan to issue a 
>> 2.0.0.6 shortly, and advise us to not update to 5.
>>
>> ~dd

Strange, I run 2.0.0.5 on three computers here and have had zero 
problems with it.  I suspect most of the problems have to do with 
questionable extensions, or use of sites with questionable coding.  And 
using Mozilla browsers since the old Netscape 1.2, I have NEVER lost 
bookmarks.  I believe that people DO, and I don't know why, but suspect 
something to do with profile corruption, but I wish someone could figure 
out a definitive cause for lost bookmarks (really lost, not just 
mislaid).  As for crashing, this just hasn't happened here.


-- 
Ron Hunter  rphunter@charter.net

Wink wrote:
> Ever since 2.0.0.x, FireFox has been horrible.  Constant crashing, the 
> lost bookmarks, the slower-than-IE speed.  Makes me wonder if Microsoft 
> wrote the upgrades:  I'm certainly getting fed up with FireFox.
> 
> Anyone know of a way to "downgrade" to v1.xx?  Anyone have a full copy 
> of the v1.5x download?
> W
> PS:  If you have the file and post a link, make sure your server can 
> handle a lot of traffic!
> 
> d d wrote:
>> I'm seeing a lot of problems reported here with the upgrade to 
>> 2.0.0.5. Mostly it seems about add-ons not working and other features 
>> suddenly breaking. I got my first upgrade prompt last night and 
>> declined it. I think I'll continue declining it.
>>
>> Is there some kind of status page we can look at where known major 
>> bugs in the current build are listed out in a short list (rather than 
>> trolling through the bugzilla DB)? Maybe such a place also 
>> acknowledges that they know it's a bad release and plan to issue a 
>> 2.0.0.6 shortly, and advise us to not update to 5.
>>
>> ~dd

Maybe the problem is that the automatic update process itself has bugs 
in it.  I have read about a lot of problems happening right after an 
automatic update.  I do my updates manually and I have had none of those 
problems.

John Doue wrote:
> Wink wrote:
>> Ever since 2.0.0.x, FireFox has been horrible.  Constant crashing, the 
>> lost bookmarks, the slower-than-IE speed.  Makes me wonder if 
>> Microsoft wrote the upgrades:  I'm certainly getting fed up with FireFox.
>>
>> Anyone know of a way to "downgrade" to v1.xx?  Anyone have a full copy 
>> of the v1.5x download?
>> W
>> PS:  If you have the file and post a link, make sure your server can 
>> handle a lot of traffic!
>>
>> d d wrote:
>>> I'm seeing a lot of problems reported here with the upgrade to 
>>> 2.0.0.5. Mostly it seems about add-ons not working and other features 
>>> suddenly breaking. I got my first upgrade prompt last night and 
>>> declined it. I think I'll continue declining it.
>>>
>>> Is there some kind of status page we can look at where known major 
>>> bugs in the current build are listed out in a short list (rather than 
>>> trolling through the bugzilla DB)? Maybe such a place also 
>>> acknowledges that they know it's a bad release and plan to issue a 
>>> 2.0.0.6 shortly, and advise us to not update to 5.
>>>
>>> ~dd
> I cannot form a valid opinion about 2.0. I have uninstalled it for it 
> does not allow to communicate easily with TB (and vice-versa) the way I 
> do with 1.5. I will forgo the security "improvements" (I rely on 
> efficient tools to avoid malware, and so far, so good).
> 
> I do have a 1.5 version available, but no site to post it, should this 
> prove necessary. But it seems it is available here: 
> http://www.mozilla.com/en-US/firefox/all-older.html
> 
> Regards

You can get all the various versions of Firefox here:
http://ftp.mozilla.org/pub/mozilla.org/firefox/
Just navigate to whatever one you like.

Ron Hunter wrote:
> Wink wrote:
>> Ever since 2.0.0.x, FireFox has been horrible.  Constant crashing, the 
>> lost bookmarks, the slower-than-IE speed.  Makes me wonder if 
>> Microsoft wrote the upgrades:  I'm certainly getting fed up with FireFox.
>>
>> Anyone know of a way to "downgrade" to v1.xx?  Anyone have a full copy 
>> of the v1.5x download?
>> W
>> PS:  If you have the file and post a link, make sure your server can 
>> handle a lot of traffic!
>>
>> d d wrote:
>>> I'm seeing a lot of problems reported here with the upgrade to 
>>> 2.0.0.5. Mostly it seems about add-ons not working and other features 
>>> suddenly breaking. I got my first upgrade prompt last night and 
>>> declined it. I think I'll continue declining it.
>>>
>>> Is there some kind of status page we can look at where known major 
>>> bugs in the current build are listed out in a short list (rather than 
>>> trolling through the bugzilla DB)? Maybe such a place also 
>>> acknowledges that they know it's a bad release and plan to issue a 
>>> 2.0.0.6 shortly, and advise us to not update to 5.
>>>
>>> ~dd
> 
> Strange, I run 2.0.0.5 on three computers here and have had zero 
> problems with it.  I suspect most of the problems have to do with 
> questionable extensions, or use of sites with questionable coding.  And 
> using Mozilla browsers since the old Netscape 1.2, I have NEVER lost 
> bookmarks.  I believe that people DO, and I don't know why, but suspect 
> something to do with profile corruption, but I wish someone could figure 
> out a definitive cause for lost bookmarks (really lost, not just 
> mislaid).  As for crashing, this just hasn't happened here.
> 
> 
I also have never lost my bookmarks.  I take care to back them up so 
that I can always find a copy.  I have had problems with profiles, and 
have had to redo them, but the important files in those profiles are 
backed up.

EE wrote:
> Wink wrote:
>> Ever since 2.0.0.x, FireFox has been horrible.  Constant crashing, the 
>> lost bookmarks, the slower-than-IE speed.  Makes me wonder if 
>> Microsoft wrote the upgrades:  I'm certainly getting fed up with FireFox.
>>
>> Anyone know of a way to "downgrade" to v1.xx?  Anyone have a full copy 
>> of the v1.5x download?
>> W
>> PS:  If you have the file and post a link, make sure your server can 
>> handle a lot of traffic!
>>
>> d d wrote:
>>> I'm seeing a lot of problems reported here with the upgrade to 
>>> 2.0.0.5. Mostly it seems about add-ons not working and other features 
>>> suddenly breaking. I got my first upgrade prompt last night and 
>>> declined it. I think I'll continue declining it.
>>>
>>> Is there some kind of status page we can look at where known major 
>>> bugs in the current build are listed out in a short list (rather than 
>>> trolling through the bugzilla DB)? Maybe such a place also 
>>> acknowledges that they know it's a bad release and plan to issue a 
>>> 2.0.0.6 shortly, and advise us to not update to 5.
>>>
>>> ~dd
> 
> Maybe the problem is that the automatic update process itself has bugs 
> in it.  I have read about a lot of problems happening right after an 
> automatic update.  I do my updates manually and I have had none of those 
> problems.
I did mine automatically, and I have none of those problems.  I think it 
has more to do with 'local conditions', such as the plugins and/or 
extensions the user has.


-- 
Ron Hunter  rphunter@charter.net