Closed Bug 148482 Opened 22 years ago Closed 22 years ago

Build ID different in titlebar than reported by Talkback in a crash

Categories

(SeaMonkey :: Build Config, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 36920

People

(Reporter: earthsound, Assigned: netscape)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0rc3) Gecko/20020523
BuildID:    2002052306 or is it :)

Mozilla's Build ID in titlebar is identified as 2002052306, but when this build
crashes, Talkback reports it as 2002052306. See Build ID in TB6883731Z.

Reproducible: Always
Steps to Reproduce:
1. compare your build ID in titlebar to the build ID reported by Talkback when
Mozilla crashes

can't crash Mozilla? you're not trying hard enough ;)

Actual Results:  different Build IDs

Expected Results:  same Build IDs

Some of these bugs/comments may be relevant or enlightening:

http://bugzilla.mozilla.org/show_bug.cgi?id=81344 [win32 build id discrepancies]
http://bugzilla.mozilla.org/show_bug.cgi?id=36920#c4 [build id: talkback off b/c
of time discrepancy]
http://bugzilla.mozilla.org/show_bug.cgi?id=102042 [difference in build id btwn
http one & "real one" as seen by plugins]
Summary: Build ID different in titlbar than reported by Talkback in a crash → Build ID different in titlebar than reported by Talkback in a crash
"Build ID in titlebar is identified as 2002052306, but when this build
crashes, Talkback reports it as 2002052306" ?
what is the difference between build ID "2002052306" and build ID "2002052306" ?
Doh! comment #1 SHOULD have read:

titlebar reports 2002052306, but Talkback reports 2002052308

:)
I'm pretty sure that this is a duplicate of Bug 81334 or Bug 36920, but in any
case, please change the component to "Build Config".
-> Build Config
Assignee: Matti → seawood
Component: Browser-General → Build Config
QA Contact: imajes-qa → granrose

*** This bug has been marked as a duplicate of 36920 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
v dup
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.