The default bug view has changed. See this FAQ.

No release date shown in new about dialog under Linux

VERIFIED INVALID

Status

()

Firefox
General
VERIFIED INVALID
7 years ago
7 years ago

People

(Reporter: Dave Garrett, Unassigned)

Tracking

({pp})

Trunk
x86
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
Screenshot under Windows 7:
attachment 475863 [details]
My screenshot under Linux (w/ KDE4.4):
attachment 475865 [details]

Both are from the same latest nightly, just different OSes.

Windows has "4.0b7pre (released 09-16-2010)". Linux has just the version.

See also 596905.

Comment 1

7 years ago
(In reply to comment #0)

> Both are from the same latest nightly, just different OSes.

Did you build it yourself, or get it through the nightly website? If you built it yourself, there won't be a released date.
(Reporter)

Comment 2

7 years ago
I said "latest nightly" and the term "nightly" is usually implied to be one of the Mozilla built nightlies, not self-built. My build is a standard nightly downloaded from Mozilla FTP. Full info:

ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-4.0b7pre.en-US.linux-i686.tar.bz2

Mozilla/5.0 (X11; Linux i686; rv:2.0b7pre) Gecko/20100916 Firefox/4.0b7pre
Built from http://hg.mozilla.org/mozilla-central/rev/f38ef1080bfe

This is Kubuntu 10.04 with KDE 4.4 running on an Intel P4 (x86) laptop.

Tested again with the above using a new Firefox profile.
Hmm... we're using nsIUpdateManager.getUpdateAt(0).buildID. Isn't that the same as navigator.buildID (i.e. the build ID of the currently running build)? I guess the idea is that we only want to show it if it was actually "updated"? The text just says "released", though, so it would be just as (in)accurate for non-updates...

Comment 4

7 years ago
This bug is invalid now because we got rid of the release date string in bug 596905.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
(Reporter)

Comment 5

7 years ago
Verified. Yep, non-issue now.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.