After a Update and restart of Firefox It told me I have a Unknown version

RESOLVED INCOMPLETE

Status

()

Firefox
General
RESOLVED INCOMPLETE
9 years ago
7 years ago

People

(Reporter: Steven Fransen, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2011-1-1])

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6; en-us) AppleWebKit/531.9 (KHTML, like Gecko) Version/4.0.3 Safari/531.9
Build Identifier: 3.5.3

Firefox did a Auto Update and asked to restart now or Later I clicked Now.
Firefox Restarted and the Webpage told me I have a Unknown Version.
 I have 3.5.3 Now.
 The Latest and Greatest Page only have 3.5.2
 I am on Snow Leopard if that matters

Reproducible: Always

Steps to Reproduce:
1. Have firefox 3.5.1 or 3.5.2 Installed ( Not sure which one I had)
2. Have it do a auto update
3. Click Restart now

Actual Results:  
The Webpage displays you have a Unknown Version

Expected Results:  
It should tell me I have the Latest version.
Steven: Since 3.5.3 is still in beta I think the page should something about a beta. I will get a new bug on file for that.

Comment 2

9 years ago
While running some Mozilla QA test on Fx3.5.2 (Windows) I had to make sure Fx was capable of finding the latest test version Fx3.5.3beta as well as finding out that the Successful update page was working. So this puts this on the Macintosh side.

What makes no sense, is why would Fx3.5.1 or 3.5.2 [whichever you had] would auto-update to a build which is not even out yet.

Now if have been upgrading from beta versions to public build versions of Firefox, than it is another story.
If you are on the beta channel (downloaded a beta somewhere along the way during Firefox 3.5 development), you will get updated to the latest beta when you check for updates. I just did a quick test of this on Mac and everything is working as expected - release builds update to 3.5.2 and beta builds update to 3.5.3, which is expected. 

Go into about:config and type app.update.channel - > if it read beta then this bug is invalid.

Bug 514774 is on file for the verbiage change.
(Reporter)

Comment 4

9 years ago
Where do you want me to go to. Yes I did down a 3.5 beta at one point.
 I just thought it was weird that I was told I had a unknown version. As Since I have installed some add-on in the last 6 months. I wanted to make sure it was not a add-on that this this. You know Hack....

Comment 5

9 years ago
(In reply to comment #4)
> Where do you want me to go to. Yes I did down a 3.5 beta at one point.
>  I just thought it was weird that I was told I had a unknown version. As Since
> I have installed some add-on in the last 6 months. I wanted to make sure it was
> not a add-on that this this. You know Hack....

To change the update channel you will need to edit a file called "channel-prefs.js"

In Mac computer the file should be located at:
{location of Firefox}/Firefox.app/Contents/MacOS/defaults/pref/channel-prefs.js

-Once you find the file open it with your text editor.

-Now look for a line that has the following: 
pref("app.update.channel", "release")

Now, if it reads anything other than "release" then this is your problem and it is not a bug.

-In the case that it doesn't say "release" then replace what it says with it.

-Save the file and you are set.


Remember, you already have downloaded Fx3.5.3 so it wont make much a difference now. But do follow the steps above to confirm this case and see if it is a misunderstanding or not.
(Reporter)

Comment 6

9 years ago
Thanks It does say release
Reporter, are you still seeing this issue with Firefox 3.6.12 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Also, please consider using the most recent Firefox 4 beta build, your bug may be resolved there.
Whiteboard: [CLOSEME 2011-1-1]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.