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?
chromium-browser
is a snap meaning it doesn't have full access to your file-system outside of $HOME, or (snap-connect
) certain directories... so start with what OS & release you are using. – guiverc Dec 30 '20 at 11:59snap list
to view your installed snaps). 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 the run confined (excluding $HOME or your user directory; that's real, and if you'vesnap-connect
/media, /mnt they an be accessed too). The /tmp seen bychromium
snap is NOT the /tmp you see a terminal/file-manager etc. – guiverc Dec 30 '20 at 22:22