Mint report 1.0.9 can quickly fill root partition with systemd coredumps

[smurphos]

Hi,

So I've got a bunch of mobile phone recorded videos in a directory and xplayer-video-thumbnailer chokes on 16 of them. I'll raise a separate report against the thumbnailer but the common factor for the failures appears to be that the videos are all very short in duration (1 to 2 seconds).

So I cleared the failed thumbnail cache and the contents of /var/lib/systemd/coredumps and viewed the folder containing the videos in nemo. This resulted in 16 coredumps being generated in /var/lib/systemd/coredumps for a total of 786MB of storage. Move those videos to another folder and view them there - more coredumps. In about 5 mins of 'managing' some video files I've got over 3GB of coredumps.

Mintreport offers no GUI option to remove crashreports / coredumps. A naive user over time could end up with a problematic storage issue as a result. The coredumps are included in Timeshift snapshots potentially exacerbating the issue.

I'm not sure what the best solution is but I don't think the circumstances I've described are necessarily very unusual. Coredumps should probably be excluded by default from Timeshift snapshots.

[LinuxOnTheDesktop]

So here we have a tool designed to solve problems seemingly causing a problem.

[okaestne]

Coredumps are created by systemd-coredump and only read by mintreport. You can set size limits in /etc/systemd/coredump.conf (don't know the default values, but there are already limits if nothing is set there) or even disable them by setting Storage=none and ProcessSizeMax=0. Check the man pages for more details (man 5 coredump.conf and man 8 systemd-coredump)