https://bugs.kde.org/show_bug.cgi?id=516768
Wolfgang Müller <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Wolfgang Müller <[email protected]> --- I'm wondering whether what you are seeing is the system actually running out of space because it attempts to store an entirely too big coredump to disk. systemd does this by default, and by default on 64-bit systems it will attempt to store coredumps of up to 32GiB. Hence the message in your journal about "No space left on device". Once it couldn't write any more, it backed out and deleted the file again. Thus it would seem that your system never actually ran out of space (but for a very short time it did). I'm unsure whether you can get Discord to crash consistently, but you can try telling systemd-coredump to not even attempt saving coredumps over a specific size. Put the following in /etc/systemd/coredump.conf.d/limits.conf: > [Coredump] > ProcessSizeMax=256M > ExternalSizeMax=256M Then observe whether the problem happens again. For more info, see https://www.freedesktop.org/software/systemd/man/latest/coredump.conf.html To find out what the current coredump settings are, you can run: $ systemd-analyze cat-config systemd/coredump.conf -- You are receiving this mail because: You are watching all bug changes.
