I suspect the other answers blaming a browser are likely correct, but they don't give any advice on how to find out for yourself.
There's a few tools that can help:
opensnoop-bpfcc
from the bpfcc-tools
package:
run sudo apt install bpfcc-tools ; sudo opensnoop-bpfcc
fatrace
from the fatrace
package:
run sudo apt install fatrace ; sudo fatrace
auditctl
from the auditd
package. This is a heavy complex piece of software, if you're not already running it, I wouldn't recommend using it here. If you're already running it, look for -F
file watches in the documentation.
I've had better luck with opensnoop-bpfcc
than fatrace
, so my preference is to use opensnoop-bpfcc
, but fatrace
is popular with many people.
$ sudo opensnoop-bpfcc
[sudo] password for sarnold:
PID COMM FD ERR PATH
5541 i3status 4 0 /etc/mtab
5541 i3status 4 0 /proc/loadavg
5541 i3status 4 0 /proc/meminfo
2252844 MemoryPoller 57 0 /proc/meminfo
3147 thermald 9 0 /sys/class/powercap/intel-rapl/intel-rapl:0/intel-rapl:0:2/energy_uj
3147 thermald 9 0 /sys/class/powercap/intel-rapl/intel-rapl:0/energy_uj
3147 thermald 9 0 /sys/class/thermal/thermal_zone5/temp
2252844 glean.dispatche 57 0 /home/sarnold/.mozilla/firefox/q9a14s71.default/datareporting/glean/db/data.safe.bin
2252844 glean.dispatche 57 0 /home/sarnold/.mozilla/firefox/q9a14s71.default/datareporting/glean/events/events
...
In this output the PID column shows the process identifier, the COMM shows the first 15 characters of the program name, ERR of 0 showed the file opened successfully, and the PATH shows the best guess of which file was opened. (The FD column shows what file descriptor the process uses to access the file. It won't be very helpful here.)
Run this in a terminal and check the output as you use browsers, download files, etc. Hopefully you'll see the results quickly.