Closed Bug 216717 Opened 22 years ago Closed 20 years ago

Failure of attempt to update to 1.5

Categories

(Core Graveyard :: File Handling, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: alanjenkin, Assigned: law)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 When I click on the link to the Win32 update I get a message to say that the file "....\TEMP\ze2gtsl6.exe could not be saved, because the source file could not be read. Try again later or contact the server administrator." Reproducible: Always Steps to Reproduce: 1. Open Mozilla at www.mozilla.org 2. Click on link to Mozilla ftp site for update to Windows Mozilla 1.5 3. Actual Results: See details above Expected Results: Should have initiated download I think this is either something to do with my mozilla settings, or it may be a conflict with ZoneAlarm. As far as I can remember, I am using the default settings in Mozilla. No theme. The problem occurs in various other places, too, but I pick this as being easiest for you to identify. In the other places it occurs, Internet Explorer runs fine and gets me out of the problem :-( I am also running Firebird under Lindows, as well as Mozilla, without problems so far.
Build Config ? How could this be build-config ? Yes, this could be your firewall. Do you used the http:// link or a ftp:// link ?
Assignee: mozbugs-build → law
Component: Build Config → File Handling
QA Contact: petersen
I am using the http://ftp.mozilla.org .... link. I have tried shutting down ZoneAlarm and McAfee VirusScan, but the problem still exists. I am using a router (with firewall) to connect to the internet. Could this be the problem? (As you say, it's really not a "build" problem -- I wasn't sure where else to put it).
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/
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: 20 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.