Reporting is disabled because the generated backtrace has low informational value
I've got a 100% reproducible crash ([chris@flap ~]$ flatpak install
--from com.slack.Slack.flatpakref from flathub.org) and every time
abrt+retrace server puke on it as having low informational value.
That strikes me as either a bug in abrt or the package or libraries it
depends on but I can't figure out which.
$ sudo abrt-cli list
[sudo] password for chris:
Sorry, try again.
[sudo] password for chris:
id 645e5e13c63a70214dd45fe5514dae06d9ad395c
reason: flatpak killed by SIGSEGV
time: Sun 23 Jun 2019 07:28:19 PM MDT
cmdline: flatpak install --from com.slack.Slack.flatpakref
package: flatpak-1.4.1-1.fc30
uid: 1000 (chris)
count: 1
Directory: /var/spool/abrt/ccpp-2019-06-23-19:28:19.332559-6190
[chris@flap ~]$ sudo abrt-cli report
/var/spool/abrt/ccpp-2019-06-23-19:28:19.332559-6190
('report_uReport' completed successfully)
Ok to upload core dump? (It may contain sensitive data). If your
answer is 'No', a stack trace will be generated locally. (It may
download a huge amount of data). [y/N/f/e] y
Querying server settings
Preparing an archive to upload
Uploading 6.4 MiB
Upload successful
Retrace job started
Analyzing crash data
..............................
Preparing environment for backtrace generation
.........
Generating backtrace
Cleaning environment after backtrace generation
Saving crash statistics
Looking for similar problems in bugzilla
Reporting is disabled because the generated backtrace has low
informational value.
Please try to install debuginfo manually using the command:
"debuginfo-install flatpak-1.4.1-1.fc30" and try again.
--
Chris Murphy