Closed
Bug 242751
Opened 20 years ago
Closed 19 years ago
Talkback causes internet connection to crash when it attempts to send error report.
Categories
(Core Graveyard :: Talkback Client, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: cbankston, Assigned: namachi)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316 MultiZilla/1.6.3.1c Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316 MultiZilla/1.6.3.1c I am using Mozilla 1.7b with Windows XP and a cable internet connection. To download the Flash Player plugin I used the following steps: 1. Help menu: about:plugins 2. Netscape.com link at top of Installed plugins page 3. Download Now link under Macromedia Flash Player on wp.netscape.com/plugins/index.html 4. This page, wp.netscape.com/plugins/index.html includes the following statement: You are using the following browser and operating system: Netscape Communicator 5.0 for Windows Windows NT 5.1 5. "Download the plugin" link on that page 6. Macromedia Flash Player link on www.macromedia.com/downloads/ links to www.macromedia.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash which offers version 3.0.10.0 (for Windows 3.1) even though instructions on that page mention an "Install Flashplayer 7.exe" icon. 7. Back to www.macromedia.com/downloads/ 8. Clicked More players link 9. Mozilla crashed, activating Talkback Agent. 10. Clicked Send on Talkback Agent 11. After several seconds saw message that Talkback Agent cannot connect to server. 12. Windows XP displayed message in area of Systray saying "A network cable is disconnected." 13. All other internet client programs showed cannot find server errors until I rebooted. 14. After reboot I started Mozilla and Talkback Agent again tried to send the queued error message, again crashing my internet connection. 15. I had to disable Talkback to interrupt this cycle. I was able to get the proper Flash Player version 7 through the link on the mozilla.org plugins page. As I was repeating the above sequence to copy the link information for this message, step 8 would usually but not always cause Mozilla to crash. With multiple Mozilla crashes I have never seen Talkback successfully send an error report. Reproducible: Always Steps to Reproduce: 1. 2. 3. This report is about problems with Mozilla browser and Talkback. I entered it under the Talkback topic because the Talkback problem prevents all my other internet client programs from connecting. At least the Mozilla crashes allow other programs to continue to function.
Reporter | ||
Comment 1•20 years ago
|
||
I just installed 1.7rc2 and had the same problem with loss of internet connection after crash & Talkback attempt to send error report.
Comment 2•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 3•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•