Comment 29 for bug 90378

>This is a bug in the application that you're using to edit the files.
No I don't think it is a bug in the application that I'm using to edit the files, it's the behaviour of the application I'm using to download the files, in this case Firefox.

For example, if I download a word document, Firefox saves it with 644 permissions to my default download location. If instead I choose to "open" the file (using FF's "Open With" dialog window) it saves the file to /tmp with 400 permissions and the file is unwriteable. This is not the same behaviour that (I remember) with Hardy, and to me it's not a feature enhancement as it reduces my productivity. However, I do see where this could be beneficial new Linux & Ubuntu users who might be aware that the file is in /tmp and may be removed upon reboot.

I would like to have the option to change this behaviour, or at least know where this is set so I can determine how to change the behaviour myself.

>Relying on this is probably a bad idea.
It's worked OK for me for the past 10 years! ;)

/tmp normally is cleaned automatically upon reboot. The length of time files are retained in /tmp can be configured via the /etc/default/rcS configuration file. By default this is set to zero which means that no files will be retained in /tmp upon restart.