Closed Bug 211785 Opened 22 years ago Closed 22 years ago

Suddenly, Mozilla will stop downloading files properly. Same files download in IE, and will download in Mozilla if reinstalled

Categories

(SeaMonkey :: Download & File Handling, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 203689

People

(Reporter: linda, Assigned: bugzilla)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Mozilla works fine for a day or so, then whenever I try to download a file, it gives me a message that says "<path to temp, then crazy filename> could not be saved, because the source file could not be read. Check with systems admin," etc. This has happened, for instance, trying to download the Flash plugin from the Macromedia site. I can immediately go over and download it with IE, and if I reinstall Mozilla, it works properly. Right-clicking at least brings up the correct filename and makes it look as though I am downloading, but the file neer appears. Reproducible: Always Steps to Reproduce: 1.(This is once the program has started acting this way) 2.Click on the file to download. 3.Watch the error message tell you that the source is corrupted, try again later. 4. Right click and save link target as... 5. Dialogue box comes up, asking where you want to save file, but then nothing else happens. Actual Results: Nothing. Expected Results: It should download files properly. I'm not using any external themes, and have Mozilla installed as Browser only.
Summary: Suddenly, Mozilla will stop downloading properly. Same files download in IE, and will download in Mozilla if reinstalled → Suddenly, Mozilla will stop downloading files properly. Same files download in IE, and will download in Mozilla if reinstalled
*** This bug has been marked as a duplicate of 203689 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.