|
Xolademoness Wanderer
Joined: 18 Jun 2004 Posts: 73 Location: United Kingdom
|
Posted: Fri Aug 31, 2007 7:22 pm
Sending error reports doesn't work |
It does connecting to server then says Error | Sorry, sending the bug report didn't work. [ Ok ]
I have tried turning my firewall off so its definitely nothing to do with that |
|
_________________ mhm.. |
|
|
|
Tech GURU
Joined: 18 Oct 2000 Posts: 2733 Location: Atlanta, USA
|
Posted: Fri Aug 31, 2007 7:32 pm |
Do you ever try sending it again? Sometimes it doesn't go through the first time, I'm guessing it doesn't get the confirmation back in time and throws an error. Usually the second time works for me.
|
|
_________________ Asati di tempari! |
|
|
|
haiku Wanderer
Joined: 19 Nov 2004 Posts: 70
|
Posted: Fri Aug 31, 2007 7:51 pm |
yeah, the error reporting tool could be better. I'd like to click "ok" send and just automatically send it without entering data.
|
|
|
|
Xolademoness Wanderer
Joined: 18 Jun 2004 Posts: 73 Location: United Kingdom
|
Posted: Fri Aug 31, 2007 7:54 pm |
I tried several times and it just keeps on saying it can't send :(
|
|
_________________ mhm.. |
|
|
|
Tech GURU
Joined: 18 Oct 2000 Posts: 2733 Location: Atlanta, USA
|
Posted: Fri Aug 31, 2007 9:45 pm |
I'm pretty sure it has to do you with your PC settings. It took some tweaking with my firewall to get it to go, but now I almost never have a problem.
Haiku the reason you are asked to enter text, is so that you can describe what you were doing to help Zugg recreate the problem. The easier it is to report a problem, the faster and more likely the problem will get fixed.
Personally I'm fond of the tool and it was a huge addition to CMUD in terms of bug fixing. In the zMUD days, if you had a bug the best you could do was try and describe the problem to Zugg. In CMUD he has a line of code he can reference, automatic tracking and potentially a screenshot and a means of reproducing the problem. |
|
_________________ Asati di tempari! |
|
|
|
Vijilante SubAdmin
Joined: 18 Nov 2001 Posts: 5182
|
Posted: Fri Aug 31, 2007 10:59 pm |
Xolademoness, I have been tracing a few bugs in the 3rd party software used by Zugg to do the entire bug reporting system. The earliest bug I traced has since been corrected, but I found another under my specific system specifications. It would help if you posted your system specifications, including proxy and firewall settings and programs. That sort of information can be sanitized and then passed on to the other developer to make a better version of that component while Zugg focuses on fixing bugs in his own code. Please, provide some of the details.
|
|
_________________ The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Fri Aug 31, 2007 11:40 pm |
The bug report tool uses the proxy server settings stored within Internet Explorer. So if you use another browser, such as Firefox, you still need to go into your Internet Options control panel and set your proxy server settings for IE. That's the most common issue with it if you have any sort of proxy server problem.
There is a very limited amount of "fancy" stuff the bug reporter can do. Keep in mind that the bug reporter needs to be able to run after a nasty crash, which means it cannot rely on anything other than low-level Windows API libraries.
haiku: Those text boxes are there for a reason. If you don't fill them in with some information on what you were doing when you got the crash, then I usually will ignore the crash report. |
|
|
|
|
|