Closed
Bug 43705
Opened 25 years ago
Closed 25 years ago
Build is not initiating Talkback
Categories
(Core Graveyard :: Talkback Client, defect, P2)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: stephend, Assigned: leaf)
References
()
Details
(Keywords: crash, Whiteboard: [nsbeta2+][dogfood-] work-around listed)
Attachments
(1 file)
3.96 KB,
text/configuration-settings
|
Details |
Friday, June 23, 2000 10:40 AM
Central Time, so most likely your 8 am build in Mountain View.
Expected outcome: When a crash occurs, Talkback is supposed to initialize and
report the data to the engineering staff.
Actual outcome: Mozilla's Talkback feature is not building or working, one of
the two.
Steps to reproduce:
1. Download a nightly.
2. Unzip the nighly and execute Mozilla.exe
3. Use Mail/News, cuz man, that *always* crashed :-)
Reporter | ||
Comment 1•25 years ago
|
||
Co-ordinated this bug with Chofmann, so I'll cc: him to this bug.
Comment 2•25 years ago
|
||
Talkback binaries and master.ini are missing in these builds. This is a build
issues. Re-assigning to leaf and ccing granrose.
Assignee: namachi → leaf
Reporter | ||
Comment 3•25 years ago
|
||
I feel this is critical for all developers and testers, so I'm adding nsbeta2
and dogfood.
Thanks
Reporter | ||
Updated•25 years ago
|
Whiteboard: nsbeta2
Comment 4•25 years ago
|
||
Talkback is a requirement for the rest of Mozilla QA and I. Those of us on
win32 platforms can't get any information on crashes at all, and this is
greatly hurting the QA effort. Talkback hasn't been in a build in awhile, and
reporting crashes without the info that talkback provides is nearly useless.
Whiteboard: nsbeta2
Comment 5•25 years ago
|
||
while this is a problem that needs to be fixed, I will point out that we now
have linux mozilla talkback-enabled builds. so if you have a reproducible crash
that is xp, you can crash it on linux and submit that talkback request as a
temporary workaround.
Comment 6•25 years ago
|
||
Putting on [nsbeta2+][dogfood-] radar. Does not need
a fix ASAP for daily work, but we should fix this for
beta2.
Whiteboard: [nsbeta2+][dogfood-]
Comment 7•25 years ago
|
||
granrose: the temporary workaround is appreciated, but not everyone on the QA
team (and esp. those not employed by Netscape) has a linux box...and some
crashes are not XP
Assignee | ||
Comment 8•25 years ago
|
||
finally got a chance to look at this today, automation was referencing an xpi
that is no longer named the same thing; fix checked in talkback should be
working again tonight or tomorrow morning. Rheeeet!
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Comment 9•25 years ago
|
||
RRRRRRhhhhhhhhheeeeeeeeeeeeeeettttttttttttah!
Reporter | ||
Comment 10•25 years ago
|
||
This bug is NOT fixed on the Win32 platform, it's probably in the build, but it
does not initiate..re-opening. Leaf, if this isn't your problem this time,
just pass it along, just to let you all know it's not initiating.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 11•25 years ago
|
||
As of 2000070108 win32, talkback binaries were included.
master.ini was not
stdout directed to dynamic console
stderr directed to dynamic console
WEBSHELL+ = 1
I am inside the initialize
Hey : You are in QFA Startup
(QFA)Talkback error: Can't initialize.
WEBSHELL+ = 2
substituting a master.ini from another build seems to work
stdout directed to dynamic console
stderr directed to dynamic console
WEBSHELL+ = 1
I am inside the initialize
Hey : You are in QFA Startup
(QFA)Talkback loaded Ok.
WEBSHELL+ = 2
My crash is TB13533966G, if it's valid then this is no longer a blocker, If it
contains no useful data then someone should reset severity to blocker.
Leaf, I told you that there was no master.ini in my build, but i'm not sure i
understand who owns master.ini
Note: when copying the master.ini there's a build id flag which we should
probably forge.
Severity: blocker → critical
Keywords: crash
Priority: P3 → P2
Summary: Build is not initiating or including Talkback (most likely the former). → Build is not initiating Talkback
Whiteboard: [nsbeta2+][dogfood-] → [nsbeta2+][dogfood-] work-around listed
Comment 12•25 years ago
|
||
Assignee | ||
Comment 13•25 years ago
|
||
Nope, still my problem; though i have realized i've been screwed by someone else
more thoroughly than i previously anticipated. It's going to take me a few
minutes to get the packaging made right again.
Status: REOPENED → ASSIGNED
Assignee | ||
Comment 14•25 years ago
|
||
ok, i've checked what i hope is a fix into the commercial talkback.xpi creation
code. should be fixed with tonight's builds.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Comment 15•25 years ago
|
||
oops, I forgot to mention that to use my attached workaround you save it
as %mozroot%\bin\components\master.ini
where mozroot is the parent of bin, and mozilla.exe lives in %mozroot%\bin
Comment 17•25 years ago
|
||
Talkback working fine in Win32 2000-07-17-08-M17 build. Marking Verified.
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 18•25 years ago
|
||
Talkback is broken again using Windows ME, build # 2000100108. Reopening.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Reporter | ||
Comment 19•25 years ago
|
||
Kerz - are you seeing this in commercial builds, also?
Comment 20•25 years ago
|
||
could be some problems connecting to the talkback database
to create a master.ini. first thing to check is if you
have a master.ini in your installation. namachi has been
working on cleaning up the database connection problem.
should be resolved when he gets this figured out.
Comment 21•25 years ago
|
||
Talkback Database Machine was experiencing hardware problems and database also
had problems due to size and index issues. We are on top it right now. It will
take couple of days to bring it fully under control. For now, the systems are
working fine. Talkback disabled in linux most probably due to unavailablity of
the talkback server when the build process created master.ini. If the master.ini
is present and talkback is not bringing up the dialog box then that is a
different issue.
Assignee | ||
Comment 22•25 years ago
|
||
technutz, is this still the case? i think people have successfully been using
talkback on windows for a while. Shiva, are there still problems on 98?
Comment 23•25 years ago
|
||
This problem was due to non-availability of talkback server to generate
master.ini. This is not specific to Windows 98.
Assignee | ||
Comment 24•25 years ago
|
||
talkback servers generating master.ini these days.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 25•25 years ago
|
||
Confirmed resolved on Windows ME, latest trunk builds.
You need to log in
before you can comment on or make changes to this bug.
Description
•