Every time I attempt to report a crash in Fedora 29 or Rawhide - well, first retrace server generation fails, that's https://github.com/abrt/retrace-server/issues/220 . Then, when I try and generate a backtrace locally, it always fails. If using gnome-abrt, it says the backtrace is unusable. If using report-cli, I get this:

Generating backtrace
Backtrace is generated and saved, 35591 bytes
Backtrace parsing failed for .
180:0: Frame start sequence expected.

Looking at the backtrace file itself, I see this:

...
Program terminated with signal SIGABRT, Aborted.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0x7f5703fff700 (LWP 26025))]

Thread 1 (Thread 0x7f5703fff700 (LWP 26025)):
A syntax error in expression, near `full'.
From                To                  Syms Read   Shared Object Library
0x00007f571ff91950  0x00007f571ff94e9d  Yes         /lib64/libnautilus-extension.so.1
0x00007f571fe8adc0  0x00007f571ff08732  Yes         /lib64/libglib-2.0.so.0
0x00007f571f7b7e90  0x00007f571fb0e98b  Yes (*)     /lib64/libgtk-3.so.0
...

i.e. the entire actual frame sequence is missing, apparently due to some sort of 'syntax error'.

Note I can always generate backtraces for the same crashes OK using 'coredumpctl gdb (pid)', so systemd-coredump doesn't have the same problem.