Make it easier to identify 64 bit builds

RESOLVED WONTFIX

Status

Thunderbird
Build Config
--
minor
RESOLVED WONTFIX
5 years ago
3 years ago

People

(Reporter: helkav, Unassigned)

Tracking

17 Branch
x86_64
Windows 7

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
TB needs to have clearer version information available (e.g. am I on the 32bit / 64bit version)

Comment 1

5 years ago
The person reporting this problem was testing a earlybird and a release build and both 32 and 64 bit versions of daily and finding it difficult to determine whether he was running a 32 or 64 bit version of Thunderbird after updating each one. https://bugzilla.mozilla.org/show_bug.cgi?id=883742 explains why he needed to do this. I'd assume this is a problem mainly for testers, though an ordinary user might find it useful to be able to confirm that they did install a 64 bit version (as expected). 

help -> troubleshooting information -> about:buildconfig shows a target of i686-pc-mingw32 for a 32 bit build and x86_64-pc-mingw32 for a 64 bit build on my Windows 7 system. However, most users would not think to look there or know how to interpret that information. I suggest the Help -> About Thunderbird window mention if its a 64 bit build (don't change what it does for 32 bit builds). 

I changed the title from "Include more details in version information" to "Make it easier to identify 64 bit builds"
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Include more details in version information → Make it easier to identify 64 bit builds

Comment 2

5 years ago
> Status: UNCONFIRMED → NEW
Confirmed bugs should not left in untriaged component. :)

Help Troubleshooting for 64bit builds:
TB Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0a1
Fx Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:24.0) Gecko/20130621 Firefox/24.0
Severity: normal → minor
Component: Untriaged → Build Config
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.