Closed Bug 354103 Opened 18 years ago Closed 17 years ago

talkback never appears, not even for a SeaMonkey crash or kill, replaced by breakpad

Categories

(SeaMonkey :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 389382

People

(Reporter: wallykramer, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5

I've used primarily SeaMonkey since 2006-03-25.  In that time it has crashed maybe a dozen times in a variety of ways--a rate better (less) than previous products.  However, it has *never* sprung up with a talkback dialog like Mozilla or Netscape did.  Dr. Watson doesn't appear either.  It just withers away and dies.

None of these mention talkback.  Or any keyword with "talk" or "back" in it.:
* about:plugins
* about:
* Help Contents (F1)
*  search Help Contents for talkback, etc.

Is TalkBack there?  Can I verify it somehow?  Should it be catching kills?  (To cure apparently infinite looping javascript.)  In the rare case of an actual crash (maybe 2 so far this year), should TalkBack be visible?

Reproducible: Always

Steps to Reproduce:
1. Start SeaMonkey
2. Use Windows Taskmgr to kill Seamonkey
3. Observe it vanish without fuss

Actual Results:  
No talkback appears

Expected Results:  
Expect TalkBack to popup and ask for email address and whether it should submit the incident.

Used custom installer option to change installation directory (to G:\mozilla.org\SeaMonkey), but accepted other defaults.  There is plenty of available disk space on all volumes (6 nonremovable).

Snooping around in the co-resident FireFox and Netscape installations (which rarely run simultaneously), Talkback is in G:\mozilla.org\FireFox\extensions\talkback@mozilla.org\components and G:\mozilla.org\Mozilla\components.  But nothing TalkBackish is in G:\mozilla.org\SeaMonkey
The problem is the SeaMonkey project currently uses its own tinderboxen for the releases. But Talkback is a kind of closed source system and so only the tinderboxen of the Mozilla Corporation/Foundation have access to the Talkback source. That means only the so-called trunk nightly builds (very unstable builds which are built every day) include Talkback. Currently some people work on a real open source replacement for Talkback.
Whiteboard: DUPEME
I had a crash yesterday with no error messages and no Talkback running Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20061209 SeaMonkey/1.5a. I had my Inbox, at least one browser window, maybe a message window and definitely a chatzilla window open. They all just closed nearly instantly with no user interaction. I'm using a kernel 2.6.12 and KDE 3.4 from Mandriva 2006 Linux distribution.
(In reply to comment #1)
> The problem is the SeaMonkey project currently uses its own tinderboxen for the
> releases. But Talkback is a kind of closed source system and so only the
> tinderboxen of the Mozilla Corporation/Foundation have access to the Talkback
> source. That means only the so-called trunk nightly builds (very unstable
> builds which are built every day) include Talkback. Currently some people work
> on a real open source replacement for Talkback.

I've been running strictly nightly builds for years, and I'll confirm
that Seamonkey crashes / freezes forcing me to kill Seamonkey from the
MS-Windows XP task manager sometimes, but mostly not, bring up a talkback
requestor on relaunch of Seamonkey.

xanthian.


Talkback is back in SeaMonkey Windows trunk nightlies as of last week.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
resolved 2007-07-24 bug 389382
OS: Windows XP → All
Hardware: PC → All
Resolution: FIXED → DUPLICATE
Summary: talkback never appears, not even for a SeaMonkey crash or kill → talkback never appears, not even for a SeaMonkey crash or kill, replaced by breakpad
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.