3

I download some file using chromium into the /tmp/ directory. Then, in a terminal, I look into /tmp/ and the file is NOT there. If I try to download it again, it is already listed in the /tmp/ directory (since it was already downloaded there, whatever 'there' means at this point).

Could it be that the download interface and the terminal refer to two different /tmp/ directories?

The interface for downloading the file is a graphical interface which offers the choice "Other Locations", and under this choice it offers "Computer", which shows the contents of a typical root (/) directory (usr, bin, home, var, etc.). From there I choose /tmp/ to download the file there. But thereafter, typing ls /tmp in a terminal does not show the file being there.

Any idea?

1 Answers1

2

The version of chromium doesn't matter, however yes you'll be using the snap version (use snap list to view your installed snaps). eg. my system shows

guiverc@d960-ubu2:~$   snap list
Name               Version                     Rev    Tracking       Publisher         Notes
chromium           87.0.4280.88                1424   latest/stable  canonical✓        -

Snaps can have different confinement restrictions, classic can access your file-system (lowest level of security), however all other levels mean they see a pretend file-system that isn't your real one as they run confined (excluding $HOME or your user directory; that's real, and if you've snap-connect /media, /mnt they an be accessed too).

The /tmp seen by chromium snap is NOT the /tmp you see a terminal/file-manager etc.

guiverc
  • 33,561