Closed Bug 305680 Opened 19 years ago Closed 18 years ago

Quality Feedback Agent unable to send a report

Categories

(Core Graveyard :: Talkback Client, defect)

Product:
Core Graveyard
Component:
Talkback Client
Version:
1.7 Branch
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 210251

People

(Reporter: wylbur, Assigned: jay)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4


This report is not a report of a crash, but a failure of the automated
reporting mechanism (Quality Feedback Agent) to send in a report for a crash.


Firefox crashed, and it generated an automated report that the Feedback Agent
has been trying to send to you for the past few days. That report has been
sitting in the queue since then, and when I hit the "send" button,
it tries to connect to talkback.mozilla.org - but it can't seem to make the
connection. I got the following error window:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Mozilla Quality Feedback Agent
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The Agent is unable to connect to the server.
Please check your proxy server settings or try again later.

                         OK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

My modem is an ActionTec Dual PC modem that interfaces with my PC
through an eithernet connection - there is no proxy server other than
the DHCP server/router within the modem.

I also have KERIO firewall in place.



Reproducible: Always
Version: unspecified → 1.0 Branch
->Core:Talkback
Assignee: nobody → jay
Component: General → Talkback Client
Product: Firefox → Core
QA Contact: general → chofmann
Version: 1.0 Branch → 1.7 Branch
Might it be your Kerio Firewall blocks Talkback?
(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8)
Gecko/20050511 Firefox/1.0.4
> Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8)
Gecko/20050511 Firefox/1.0.4
> 
> 
> This report is not a report of a crash, but a failure of the automated
> reporting mechanism (Quality Feedback Agent) to send in a report for a crash.
> 
> 
> Firefox crashed, and it generated an automated report that the Feedback Agent
> has been trying to send to you for the past few days. That report has been
> sitting in the queue since then, and when I hit the "send" button,
> it tries to connect to talkback.mozilla.org - but it can't seem to make the
> connection. I got the following error window:
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Mozilla Quality Feedback Agent
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> 
> The Agent is unable to connect to the server.
> Please check your proxy server settings or try again later.
> 
>                          OK
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> 
> My modem is an ActionTec Dual PC modem that interfaces with my PC
> through an eithernet connection - there is no proxy server other than
> the DHCP server/router within the modem.
> 
> I also have KERIO firewall in place.
> 
> 
> 
> Reproducible: Always

Build Identifier:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716
Firefox/1.0.6

Similar problem, allthough the causes may be different.
The LAN has a proxy server, which is correctly configured. The Agent still is
unable to send incidents.

Could that be due to the fact that there is now way to input user/password data
in the Agent configuration?

Reproductible: always.
Reporting an almost identical faliure as Jay Patel described underneath, I came
to the conclusion that it is definately a problem in your Quality Feedback Agent
from SupportSoft. I will describe underneath again what exactly happened and
what my system configurations are:

SITUATION:
Firefox crashed, and it generated an automated report that the Feedback Agent
has been trying to send to you for the past few days. That report has been
sitting in the queue since then, and when I hit the "send" button,
it tries to connect to talkback.mozilla.org - but it can't seem to make the
connection. I got the following error window:

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Mozilla Quality Feedback Agent
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The Agent is unable to connect to the server.
Please check your proxy server settings or try again later.

                         OK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
(IDENTICAL AS UNDERNEATH)

Strangely I don't use a proxy server, and my internet connection was online and
connected, operating normally for all my other softwares. I just have to add the
note that your Talkback Client has PMS sometimes, since he, when in better
moods, actually manages to send the error report with the same conditions
mentioned before!

SYS CONFIG:
OS: Windows XP Professional SP2
DDR Memory: 512 MB DDR (Was operating @ 203 MB at the incident)
Physical Memory: 74 GB Samsung HD (Operating in 2 partitions: 1. Basic where
DPA2 is installed, with 18,63 GB total cap.; operating at 15 GB, without
pagefile use, during the crash)
Internet Connection: 300 kbps, 30GB per month top (connected through personal
router)
IP Adress:  201.13.31.248 (Brazil)
Firewall: Agnitum Outpost Pro (configured to allow the connection)

Thank you and please reply soon :D(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8)
Gecko/20050511 Firefox/1.0.4
> Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8)
Gecko/20050511 Firefox/1.0.4
> 
> 
> This report is not a report of a crash, but a failure of the automated
> reporting mechanism (Quality Feedback Agent) to send in a report for a crash.
> 
> 
> Firefox crashed, and it generated an automated report that the Feedback Agent
> has been trying to send to you for the past few days. That report has been
> sitting in the queue since then, and when I hit the "send" button,
> it tries to connect to talkback.mozilla.org - but it can't seem to make the
> connection. I got the following error window:
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Mozilla Quality Feedback Agent
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> 
> The Agent is unable to connect to the server.
> Please check your proxy server settings or try again later.
> 
>                          OK
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> 
> My modem is an ActionTec Dual PC modem that interfaces with my PC
> through an eithernet connection - there is no proxy server other than
> the DHCP server/router within the modem.
> 
> I also have KERIO firewall in place.
> 
> 
> 
> Reproducible: Always

(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8)
Gecko/20050511 Firefox/1.0.4
> Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8)
Gecko/20050511 Firefox/1.0.4
> 
> 
> This report is not a report of a crash, but a failure of the automated
> reporting mechanism (Quality Feedback Agent) to send in a report for a crash.
> 
> 
> Firefox crashed, and it generated an automated report that the Feedback Agent
> has been trying to send to you for the past few days. That report has been
> sitting in the queue since then, and when I hit the "send" button,
> it tries to connect to talkback.mozilla.org - but it can't seem to make the
> connection. I got the following error window:
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Mozilla Quality Feedback Agent
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> 
> The Agent is unable to connect to the server.
> Please check your proxy server settings or try again later.
> 
>                          OK
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> 
> My modem is an ActionTec Dual PC modem that interfaces with my PC
> through an eithernet connection - there is no proxy server other than
> the DHCP server/router within the modem.
> 
> I also have KERIO firewall in place.
> 
> 
> 
> Reproducible: Always


Same results for me
Win XP Home edition with Zone Alarm firewall and symantec corp. antivirus
I (and some other people) have the same problem.

I use no firewall (just a router) and no proxy.

System Win2k, Fx 1.5
FWIW, I am also experiencing this issue.

As far as I know, I am not using a proxy nor SOCKS.

Though Windows XP 2002 Service Pack 2 may be doing so behind my back...

Perhaps the Mozilla.org FAQ page about Proxies and SOCKS could tell the reader how to find out if proxy and/or SOCKS are in force.

In may case, the firewall / virus protection is NOD32 from Eset.  This is the third distinct such package, so unless they are all doing something in common, it's probably not a firewall on the PC issue.

It's possibly a firewall further up the stream on my LAN, but I'd have zero control over that no matter what, so if that's the problem, it's not really solvable by an end user, and some kind of work-around should be considered.

I have tried multiple times to get the queued feedback out, and am happy to keep pushing the button, but another option, if it's just over-loaded servers, is to allow me to set a frequency of retry times, and let the software keep re-trying until it works.

In addition, if the Agent isn't going to work at all, I ought to be able to access, from the agent, a dump of what would have been sent, so I can paste it into Bugzilla (in a separate bug report).  Alas, there seems to be no facility to get at the data it's trying to send, from the agent, so I'm stuck with filing the original bug report rather badly, I'm afraid...

If I had known it wasn't going to work, I'd have just copied the text from the "Show Details" of what was being sent, and come here to file a bug report.

I dunno how much of that gobbledy-gook about registers and traceback in HEX is actually useful to you guys, but you ain't getting any of it, and I figure you wouldn't have put it all in there if you didn't want it, so that's gotta be bad...

I realize some of these things are a ton of work to implement, and Feedback Agent might not even be your application to fix in the first place, but you can probably pass on these suggestions with more oomph behind them than I can.

THANKS!

I have the same problem only I am using Win 98SE.  I am unable to send a report even though I am connected to internet with dial-up and all other internet connections seem to be working fine.  When I shut down and reboot, I get the same message to send report but each time I get the same reply.  This has happened about 4 time in the past year when my Mozilla/Firefox Browser suddenly died.  I remain unable to ever send a report until someone from Firefox instructs me how to overcome this problem.  It would seem to me that Firefox would want to know about this problem and make some suggestions to repair the problem, but as I read down this Bug Report, I see no resolutions.  What to do?  


Same problem, using XP SP2 spanish.i've d-link d512 router.
Only different: I think i've installed Firefox 1.5.1 after another 1.0.6 and this time i have not checked the option to install the Quality feedback agent.
The QFA itself tells me that it's latest version.

Then I can suposse that this isn't working because it's a old version/outdated url to send the report 
(Sending incident to talkback.mozilla.org/spiral-bin/collector.dll Report 1 of 1 fails)
I have the same problem.
For both Firefox and Thunderbird.
I use both with 1.5 version, the crash stays in QUEUE but NEVER goes
I have the same problem. Connected directly by cable. NOD32 antivirus active. It does not depend on MS Firewall (I tested it to switch off and on).
Same result for me...I don't have any proxy server set in either IE or Firefox.

I have crashes from both firefox and thunderbird to report and I cannot report them due to this problem.

I checked, and talkback.exe has been added under windows firewall as an exception.

Can somebody please change the status of this to NEW?  It seems there's enough confirmation above to warrant this.

Thunderbird just crashed again on me and I simply cannot report the crash.

The situation here:
* WinXP SP2
* No proxy set in Internet Explorer settings
* Internet Explorer works fine with web browsing
* Firefox works fine with browsing
* Windows firewall is enabled, and the talkback.exe is in the list of exceptions, and turning the windows firewall off makes no difference to the behaviour
* If I run the www.sysinternals.com TCPVIEW.EXE tool to monitor TCP connections out from talkback.exe, I do not see ANY AT ALL, and yet it fails.


Please search Bugzilla for similar bugs, this bug has been reported many many times, and unfortunately my answer is always the same... look at:
http://wiki.mozilla.org/Mozilla_QA_Community:Talkback:FAQ

Marking dup, as there isn't anything I can do about htis bug.

*** This bug has been marked as a duplicate of 210251 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
verifying that this bug should *not* be confirmed. there's a process and there are reasons we don't confirm bugs randomly :).
Status: RESOLVED → VERIFIED
(In reply to comment #14)
> Please search Bugzilla for similar bugs, this bug has been reported many many
> times, and unfortunately my answer is always the same... look at:
> http://wiki.mozilla.org/Mozilla_QA_Community:Talkback:FAQ
> 
> Marking dup, as there isn't anything I can do about htis bug.
> 
> *** This bug has been marked as a duplicate of 210251 ***
> 

But here's the thing.

I'm on a dual T-1 shared by an office, and it's the middle of the night.

There is NO WAY it's a slow connection on my end.

The thing will sit there and fail to send the report for days, and then nuke it, and I never ever ever get an Incident ID.

You guys *ARE* losing these reports to the bit bucket, as far as we users can tell... :-(

The FAQ referenced simply does not address this adequately, if at all.

Turning off the talkback doesn't help anybody.

Bug reports of crashes going to the bit bucket don't help anybody.

Oh well.
[shrug]
in the future airbag is replacing talkback, if you want something now (and don't mind random builds), you're free to follow the steps at http://developer.mozilla.org/en/docs/How_to_get_a_stacktrace_with_WinDbg

otherwise, we get lots of reports and don't have enough time to analyze them.

(but if you do follow the steps in that url, we'll make time.)
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.