Hi Bernhard,
Thank you for the instructions. After additional testing, my initial
report was mistaken; instead, it is probably the selection of a
particular destination folder. When I ask Handbrake to write to my
external (5 TB) disk, connected over USB 2, it crashes with any preset.
However, the backtrace (in /var/lib/systemd/coredump) is ~320 MB. Is
there information I can extract from it, or a particular way I should
make such a large file available?
Output from journalctl --no-pager:
=======================================
Aug 03 09:25:25 sethix kernel: show_signal_msg: 17 callbacks suppressed
Aug 03 09:25:25 sethix kernel: ghb[26263]: segfault at 0 ip
00007f0f9a103fb4 sp 00007f0e81ff14e8 error 4 in
libc-2.28.so[7f0f9a084000+148000]
Aug 03 09:25:25 sethix kernel: Code: 74 12 88 0c 0c 8a 48 03 48 83 c0 04
88 0c 0c f6 c1 ff 75 d2 48 8d 42 fc 66 66 2e 0f 1f 84 00 00 00 00 00 0f
1f 00 48 83 c0 04 <8a> 08 84 0c 0c 74 21 8a 48 01 84 0c 0c 74 16 8a 48
02 84 0c 0c 74
Aug 03 09:25:25 sethix systemd[1]: Created slice
system-systemd\x2dcoredump.slice.
Aug 03 09:25:25 sethix systemd[1]: Started Process Core Dump (PID
26399/UID 0).
Aug 03 09:25:27 sethix systemd-coredump[26400]: Core file was truncated
to 2147483648 bytes.
Aug 03 09:25:28 sethix systemd-coredump[26400]: Process 7024 (ghb) of
user 1000 dumped core.
Stack trace of thread
26263:
#0 0x00007f0f9a103fb4
n/a (n/a)
Aug 03 09:25:28 sethix systemd[1]: systemd-coredump@0-26399-0.service:
Succeeded.
=======================================
Thanks, --SF
