276814 - talkback segmentation faults

Status: RESOLVED INVALID

(Core Graveyard :: Talkback Client, defect)

Description

[Darlene Ford]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217

I'm running Mozilla 1.7.5 on Fedora Core 2.  While attempting to generate
talkback data for bug 275095, I accidentally discoved a bug in talkback as well.
 It can be reproduced more efficiently as described below. 

Reproducible: Always

Steps to Reproduce:
1.Start talkback.
2.Select "Create New Incident" from the "Incidents" menu.
3.Click the "Details" button on the Quality Feedback agent.

Actual Results:  
talkback exits immediately, and the shell I started it from reports a
segmentation fault.  I was able to repeat this behaviour on several consecutive
attempts.

Expected Results:  
I don't know, but surely this can't have been the intended result...

Is this the right place to report talkback bugs, or should they go under "Other
Applications" ?  I actually think that having a subcategory for talkback bugs is
a good idea because a keyword search for "talkback" brings up a large fraction
of bug reports for all mozilla products.   So, it's hard to do an efficient
search to see if this has happened before...

Comment 1

[Christian :Biesinger (don't email me, ping me on IRC)]

you could use the "Talkback" component...

I am not sure if mozillafoundation has the talkback source code... anyway,
fixing component

Comment 2

[Darlene Ford]

This bug is also present in 1.8a6.

Comment 3

[Darlene Ford]

Could I trouble you to explain?  Isn't talkback a mozilla product, or part of one?
My apologies to the author if I was mistaken about this.

I think you said that you were fixing the bug?

Comment 4

[Jay Patel [:jay]]

Darlene: 
I believe Chrisian meant he was "fixing" the component of this bug, meaning
changing it to Product: Core, Component: Talkback.  

Regarding your issue, Talkback is a third party application we integrate into
Mozilla products to help us manage stability issues (crashes).  We only have a
license to use it and do not have access to the source code to fix any bugs at
this time.

Also, if I understand your steps to reproduce, you were trying to manually
generate a "blank" incident through the Talkback Client UI, which probably
explains why the Details button leads to a crash (Talkback doesn't have any info
about a real crash in Mozilla).  I suggest you only run Talkback (talkback.exe)
manually if you need to look up you crash incidents generated while using
Mozilla products (when Mozilla crashes, it will trigger Talkback automatically
and allow you to entire more information, at which time the Details button
should work and show you everything Talkback has gathered to sent to us about
the crash).  Does that make sense?  Let me know if you need more clarification.

Marking this bug Invalid since we do not have the capability to fix Talkback
specific issues like this one.