[Bug] Generation of a backtrace for a "System" failure fails with "Failed to generate microreport from the problem data". #389
Description
An Example
When processed, I saw:
Details
Failed to generate microreport from the problem data
Unfortunately, abrt immediately deleted it, rather like discussion.fedoraproject.org/t/162891 describes (although more similarly to when it locates a duplicate). 1
Environment
#!/usr/bin/env sh
rpm -qa | grep abrtabrt-libs-2.17.6-4.fc42.x86_64 abrt-dbus-2.17.6-4.fc42.x86_64 python3-abrt-2.17.6-4.fc42.x86_64 abrt-2.17.6-4.fc42.x86_64 abrt-addon-kerneloops-2.17.6-4.fc42.x86_64 abrt-addon-pstoreoops-2.17.6-4.fc42.x86_64 abrt-addon-vmcore-2.17.6-4.fc42.x86_64 abrt-addon-xorg-2.17.6-4.fc42.x86_64 abrt-plugin-bodhi-2.17.6-4.fc42.x86_64 python3-abrt-addon-2.17.6-4.fc42.noarch gnome-abrt-1.4.3-4.fc42.x86_64 abrt-gui-libs-2.17.6-4.fc42.x86_64 abrt-gui-2.17.6-4.fc42.x86_64 abrt-addon-ccpp-2.17.6-4.fc42.x86_64 abrt-tui-2.17.6-4.fc42.noarch abrt-cli-2.17.6-4.fc42.x86_64 abrt-desktop-2.17.6-4.fc42.x86_64
Tangential
This is an example of when #378 (comment) might be useful, considering that it might pertain to bugzilla.redhat.com/show_bug.cgi?id=2391169#c0.