Closed Bug 193502 Opened 22 years ago Closed 22 years ago

files to be downloaded renamed *.jpg

Categories

(Core Graveyard :: File Handling, defect)

Product:
Core Graveyard
Component:
File Handling
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
CLOSED DUPLICATE of bug 189598

People

(Reporter: Spuds, Assigned: law)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210 installer named with wrong extension Reproducible: Always Steps to Reproduce: 1. click on download new build (checked from mozilla's start page) 2. 3. Actual Results: app-chooser selects a jpeg viewing program as default app to open with Expected Results: program should end in .exe
Do you have ".jpg" associated to "application/octet-stream" in helper app preferences?
.
Assignee: dveditz → law
Component: Installer → File Handling
QA Contact: bugzilla → petersen
I was having this problem also.. Anytime I went to download a .exe it would save it as .exe.jpg.. In Helper Applications.. You'll see a line MIME Type:application/octet-stream Description:JPEG Application Extension: .jpg Open it with:C:\Program Files\mozilla.org\Mozilla\mozilla.exe I removed that file type, since jpeg, was listed near the bottom as image/jpeg, and it fixed it.. Dont know how that line got put into my Helper App section though
It got there because of bug 189598. *** This bug has been marked as a duplicate of 189598 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
re-opening. I may be misunderstanding, but this doesn't seem to be related to the octet-stream bug, . That appears to be what app actually OPENS the file, this is that the file gets renamed before it's opend by anything
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Summary: installer named *.exe.jpg → files to be downloaded renamed *.jpg
That bug affects both the app that opens it and what it's named. Did you remove the bogus entry? Did that fix the problem?
ahh, that wasn't clear, marking as dup again *** This bug has been marked as a duplicate of 189598 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago → 22 years ago
Resolution: --- → DUPLICATE
duplicate
Status: RESOLVED → CLOSED
Please don't mark bugs closed; only drivers should do that....
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.