Prohledat stránky podpory

Vyhněte se podvodům. Za účelem poskytnutí podpory vás nikdy nežádáme, abyste zavolali nebo poslali SMS na nějaké telefonní číslo nebo abyste sdělili své osobní údaje. Jakékoliv podezřelé chování nám prosím nahlaste pomocí odkazu „Nahlásit zneužití“.

Zjistit více

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

  • 2 odpovědi
  • 5 má tento problém
  • 72 zobrazení
  • Poslední odpověď od 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?

Zvolené řešení

Všechny odpovědi (2)

more options

Zvolené řešení

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

Upravil uživatel cor-el dne

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.