>

Check why an app crashed with coredumpctl

coredumpctl lists every crash the kernel recorded, when it happened, and can show a backtrace for the crash you care about.

LinuxcoredumpdebuggingtroubleshootingLow risk
Run `coredumpctl list` to find the crash, then `coredumpctl info <pid-or-name>` for its signal, log excerpt and stack trace.

01Command

Command
$ coredumpctl list

02What it does

On systems with systemd-coredump, crashing programs leave a compressed core dump plus a journal entry. This tells you which binary segfaulted, which signal killed it, and often the failing library — far more useful than 'app disappeared'. `coredumpctl dump` can export the core file for gdb.

03Risk

RiskLow risk
Requirementssystemd-coredump package (default on Fedora/Arch/Ubuntu GNOME)
!Warning: Backtraces are only symbolic with the debug symbols of the crashing package installed; without them you still see the crashing binary and module.

04Undo

Undo
$ sudo rm -rf /var/lib/systemd/coredump/*  (frees space)

05Sources

Last verified: 2026-09-18 · Category: System & Settings

06Related solutions

Show IP addresses in a compact table with `ip -br a`
Linuxifconfignetworktroubleshooting

One command that prints every interface with its state and IPv4/IPv6 addresses in a short table — the modern, memorable replacement for digging through `ifconfig` or the verbose `ip addr` output.

Low risk ✓ 2026-09-17
View the routing table and default gateway with `ip route show`
Linuxroutinggatewaytroubleshooting

The routing table is the first thing to check when traffic leaves the wrong interface or the gateway seems dead — and `ip route show` is the quick, modern way to read it.

Low risk ✓ 2026-09-17
Check if a remote port is open with `nc -zv`
Linuxncportnetcat

The fastest way to answer 'is the firewall blocking me?' — netcat in scan mode attempts one TCP connection and prints whether it succeeded.

Low risk ✓ 2026-09-17