Closed
Bug 324105
Opened 19 years ago
Closed 17 years ago
Talkback (Quality feedback agent) always shows as "program not responding", and I can only get rid of it by rebooting.
Categories
(Core Graveyard :: Talkback Client, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: ere, Assigned: jay)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 A problem is indicated by a popup window. Np matter what I click (send, cancel, the x) or if I try to close it by right clicking on the icon in toolbar or by using program manager, the box will not disappear. The box showing "End Program Mozilla Quality Feedback agent" does not disappear when I hit End Now or Cancel or the x or the icon in the toolbar/tray. I have to reboot to get rid of it. Reproducible: Always Steps to Reproduce: 1.Happens on its own. Sure wouldn't encourage that. 2. 3. Expected Results: Reported the error and then the box should disappear.I do not have this I do not have this problem with the MS error reporting system.
Comment 1•19 years ago
|
||
Have you allowed QFA access through the firewall?
Comment 2•19 years ago
|
||
As a workaround, you might be able to close it through Task Manager (Ctrl+Shift+Esc).
Summary: My problems are listed as 'unconfirmed' Quality feedback agent always shows as "program not responding" but there is no way to close that window though I can minimize it to get it out of the way. I can only get rid of it by rebooting. → Talkback (Quality feedback agent) always shows as "program not responding", and I can only get rid of it by rebooting.
Updated•19 years ago
|
Assignee: nobody → jay
Component: General → Talkback Client
Product: Firefox → Core
QA Contact: general → chofmann
Version: unspecified → 1.8 Branch
Comment 3•17 years ago
|
||
no response from reporter, so => incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•