351277 - Files saved to desktop are given random filenames (filenames used for /tmp?)

Status: RESOLVED INCOMPLETE

(Toolkit :: Downloads API, defect)

Description

[OOZIE]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.0.6) Gecko/20060728 SUSE/1.5.0.6-1.3 Firefox/1.5.0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.0.6) Gecko/20060728 SUSE/1.5.0.6-1.3 Firefox/1.5.0.6

Hi guys! 

Since 1.5.0.6 my firefox started to save randomized filenames not only to 
/tmp but also on my desktop. This is always reproducable, when I try to
download e.g. an .xls file

I use a SUSE Linux 10.1, my Firefox has been updated over YAST online update.
From 1.5.0.4 to 1.5.0.6


Reproducible: Always

Steps to Reproduce:
1. Click on attachment file/file to download
2. Click on save to disk


Actual Results:  
File is stored onto my ~/Desktop directory.

Expected Results:  
The file is supposed to have it's original name, when stored to ~/Desktop
and the randomized one when stored to /tmp

Comment 1

[Adam Guthrie]

Can you reproduce this in a build from mozilla.org? SuSE could be doing something funky with their Firefox...

Comment 2

[OOZIE]

Sure, I did download mozilla from mozilla.org and the effect is the same.
Can you guys reproduce this behaviour aswell?

Best regards,
OOZIE

Comment 3

[Adam Guthrie]

Can you give an example site where this occurs?

Comment 4

[[:Aleksej]]

Thank you for your report.

It's important that Bugzilla is reserved for reporting actual problems with the
software, in enough detail that the bug report helps us fix the problem.
For a report to be useful to us, we generally have to have enough information
to make it happen to us, on our machines. If we can't reproduce the problem,
it's very difficult for us to find out the cause, because it makes it
impossible for us to run any tests that would help to diagnose it.
http://developer.mozilla.org/en/docs/Bug_writing_guidelines has more details as
to what exactly we are looking for in order to make that happen. Following the
bug writing guidelines takes time, but it makes it much more likely that a
developer will be able to identify the underlying cause of a problem and fix it
in a future release. Please, check if you can reproduce the bug with a current release with a new profile.