Closed Bug 278013 Opened 20 years ago Closed 19 years ago

Failure to use remembered lastDir target directory for downloads

Categories

(Toolkit :: Downloads API, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: Valdis.Kletnieks, Assigned: bugs)

Details

I invoke the 'Save As..', and it puts up a directory selector.  The 4 choices in
the pulldown are "Home", "Filesystems", a horizontal separator, and then a
displayed "Downloads" (referencing /home/valdis/Downloads), and "valdis"
(referencing /usr/src/valdis - a rarely used target for large downloads of
program source).  I select 'Downloads', and download the file.  The next time I
download something, the default target directory is again 'valdis', and I have
to select 'Downloads' again.  This behavior even persists across stopping and
restarting Firefox, even though there is no obvious place (such as prefs.js)
even *listing* /usr/src/valdis. Even doing this:

find .mozilla/firefox -type f | xargs cat | grep usr/src/valdis

finds *no* files that reference it at all.  So why does it keep coming back as a
target (which I don't mind) and listed *as the default* (which I *do* mind)?

Likely related info:

% grep download prefs.js 
user_pref("browser.download.dir", "/home/valdis/Downloads");
user_pref("browser.download.folderList", 9);
user_pref("browser.download.lastDir", "/home/valdis/Downloads");
user_pref("browser.download.save_converter_index", 0);
user_pref("browser.download.useDownloadDir", false);

lastDir isn't being honored....
when filing bugs, always include a useragent. also, are you using a gtk2 build?
if so, what versions of gtk2/gnome2 do you have?
Running on Fedora Core devel tree, gtk2-2.6.0-1.

Firefox build is from the
ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-1.0+.en-US.linux-i686.tar.gz

chrome://global/content/about.xhtml reports
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a6) Gecko/20041213 Firefox/1.0+
(Thank you, bug 272556 ;)

All builds I've tried more recent than the 12/13 one have the same problem (and
the problem was there before then as well...)
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: 19 years ago
Resolution: --- → EXPIRED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.