Closed
Bug 274091
Opened 20 years ago
Closed 14 years ago
talkback on linux can not display details.
Categories
(Core Graveyard :: Talkback Client, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: k_b0000, Assigned: jay)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20041206 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20041206 talkback on linux can not display details of the information beeing send. pressing the details button does nothing. Reproducible: Always Steps to Reproduce: 1.
Updated•20 years ago
|
Assignee: general → jay
Component: General → Talkback
Product: Mozilla Application Suite → Core
QA Contact: general → chofmann
Version: unspecified → Trunk
| Assignee | ||
Comment 1•19 years ago
|
||
Not sure anything can be done with this until we have access to the Talkback source code. Setting Target Milestone to Future in case we ever have a chance at hacking Talkback.
Target Milestone: --- → Future
Comment 2•19 years ago
|
||
dup of bug 245678?
Comment 3•19 years ago
|
||
I don't know if this is the same bug, but when I click "Details", the talkback software crashes. Here's a stack I could grab with gdb: (gdb) bt #0 0x080f14e9 in CvtStringToMatrixScrollBarDisplayPolicy () #1 0x00000218 in ?? () #2 0x00000056 in ?? () #3 0x082bbaf0 in ?? () #4 0xffffffff in ?? () #5 0xbffacd5c in ?? () #6 0x080fad27 in CvtStringToMatrixScrollBarDisplayPolicy () Previous frame inner to this frame (corrupt stack?)
Comment 4•19 years ago
|
||
I can confirm that the Talkback software crashes when clicking the Details button under Ubuntu 5.10. I have some extension causing crashes on FF shutdown and both the Talkback window and the Quality Feedback Agent window have disappeared twice when clicking Details. No Talkback id or incident is ever generated.
Comment 5•14 years ago
|
||
We have not used Talkback in years and it is not longer maintained. Closing bugs.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•