Closed Bug 592440 Opened 14 years ago Closed 9 years ago

Options "Save File To" not working

Categories

(Firefox :: General, defect)

3.6 Branch
x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: rustywright575, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 GTB7.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 GTB7.1

Under Tools, Options, General tab, Save Files to is selected and the folder is D:\Download HOWEVER Firefox doesn't download there. It downloads to C:\Users\username\AppData\Local\Temp.


Reproducible: Always

Steps to Reproduce:
1.I just download from any URL
2.
3.
Actual Results:  
Download went to to C:\Users\username\AppData\Local\Temp.

Expected Results:  
Download should have gone to D:\Download


Error occurs with all types of data.
Version: unspecified → 3.6 Branch
Reporter, Firefox 4.0.1 has been released, and it features significant improvements over previous releases. Can you please update to Firefox 4.0.1 or later, and retest your bug? Please also create a fresh profile (
http://support.mozilla.com/kb/Managing+profiles), update your plugins (Flash, Java, Quicktime, Reader, etc) and update your graphics driver and Operating system to the latest versions available. 

If you still continue to see this issue, please comment. If you do not, please close this bug as RESOLVED > WORKSFORME

filter: prefirefox4uncobugs
Do you still see this problem when using a current version started in safe mode?
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode?redirectlocale=en-US&redirectslug=Safe+Mode

If you still continue to see this issue, please comment. If you do not, please close this bug as RESOLVED > WORKSFORME
Whiteboard: [closeme 2015-03-25]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2015-03-25]
You need to log in before you can comment on or make changes to this bug.