Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

How to make Firefox to not use /tmp directory for saving *part files during downloads?

  • 2 个回答
  • 5 人有此问题
  • 3 次查看
  • 最后回复者为 LMA73

more options

Firefox: 52.5.2 (64-bit) OS: 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux

/etc/fstab entry: tmpfs /tmp tmpfs nodev,nosuid,size=100M 0 0

Firefox saves *part files in /tmp directory no matter what settings of file destination are chosen. User might configure FF so it should ask where to save file or choose a specific directory but it doesn't matter to FF during saving of *part file. There are no entries in about:config related to /tmp directory.

FF wrongly assumes that *part files should be saved in /tmp directory. FF wrongly assumes that /tmp is the place with enough disk space so all downloads of files larger than /tmp fail.

How to change or prevent this behaviour?

Firefox: 52.5.2 (64-bit) OS: 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux /etc/fstab entry: tmpfs /tmp tmpfs nodev,nosuid,size=100M 0 0 Firefox saves *part files in /tmp directory no matter what settings of file destination are chosen. User might configure FF so it should ask where to save file or choose a specific directory but it doesn't matter to FF during saving of *part file. There are no entries in about:config related to /tmp directory. FF wrongly assumes that *part files should be saved in /tmp directory. FF wrongly assumes that /tmp is the place with enough disk space so all downloads of files larger than /tmp fail. How to change or prevent this behaviour?

被采纳的解决方案

所有回复 (2)

more options

选择的解决方案

Try to set the TMPDIR environment variable to a folder in your home directory.

由cor-el于修改

more options

Thank you for your answer. It was a pleasure to look at nicely coded FF :)

I did some more testing: with new user account a freshly started FF behaves correctly. So it must be somewhere in configuration of my account :(

Well, it also works in my account properly. Maybe reconfiguring and restarting FF helped.

Thank you for your help.