Hello Cláudio, I am not maintainer of the din package, just reading through some crash reports.
Unfortunately I cannot follow your claim "The crash occurred in the module libzstd.so.1". None of the 5 threads show a frame inside libzstd. It seems just listed in the Module list. Thread 166294 shows all the last frames in the din executable, all other visible threads may just be "waiting", therefore the epoll_wait frame. I would suggest to install systemd-coredump and gdb if not happened yet. If it was, following sequence of command should enable the debugger to load debug information for involved executables and print out function names with source file and line number information. export DEBUGINFOD_URLS="https://debuginfod.debian.net"; coredumpctl gdb 166294 y thread apply all bt full quit This downloads several megabytes into $HOME/.cache/debuginfod_client. And would show way more details for the maintainer to look at. I tried to reconstruct the line information to your first thread, which I suspect is the crashing one. More information about debugging crashes can be found in this page: https://wiki.debian.org/HowToGetABacktrace Kind regards, Bernhard Stack trace of thread 166294: #0 0x00005617dbae42ab n/a (din + 0xc02ab) in font::draw_char(char, int, int, int) at ./src/font.cc:203 #1 0x00005617dbae4a75 n/a (din + 0xc0a75) in draw_string(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int, int, int) at ./src/font.cc:220 #2 0x00005617dba8c2e4 n/a (din + 0x682e4) in options_list::draw() at ./src/options_list.h:93 #3 0x00005617dbb73b55 n/a (din + 0x14fb55) in settings::draw() at ./src/settings.cc:281 #4 0x00005617dbb8aab0 n/a (din + 0x166ab0) in ui_list::draw() at ./src/ui.cc:151 #5 0x00005617dba5a15b main (din + 0x3615b) in main(int, char**) at ./src/main.cc:1606 https://sources.debian.org/src/din/56-1/src/font.cc/#L203
