3.5 randomly reverts back to my previous version of FF.




10 years ago
8 years ago


(Reporter: kympylee, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2010-11-15])



10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv: Gecko/20081217 Firefox/ (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv: Gecko/20081217 Firefox/ (.NET CLR 3.5.30729)

I downloaded 3.5 today. Previously, I had a much older version of Firefox, because  3.1 didn't work on my computer. 

Everything worked fine. I closed FF, opened it back up, and it was still 3.5. Then, I opened it up, and it had been taken back to the previous version I had. I didn't uninstall it, in fact, I didn't do anything.

Reproducible: Didn't try
3.5 is a beta version and it installs in a different directory.
It doesn't replace the other Firefox installation and you must opened the old Firefox. Only one Firefox se4ssion can run at the same time and you have to close all windows of Firefox 2.0.20 and use the 3.5 Beta link to open Firefox 3.5
This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles. If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.

This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.
Whiteboard: [CLOSEME 2010-11-15]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.