Description of problem: On latest Fedora 33 Workstation system, when clicking "Report" on some issue in GNOME Abrt, "Error: File './coredump' is not a coredump" appears. When I search in journalctl, I see the relevant coredump without any issue, but GNOME Abrt not. This seems to happen on every report in GNOME Abrt, so there is no way to easily report application issues on F33. Version-Release number of selected component (if applicable): gnome-abrt-1.3.5-5.fc33.x86_64 How reproducible: Every time. Steps to Reproduce: 1. Use latest, fully updated Fedora 33 Workstation system. 2. Wait until there is some report in GNOME Abrt. 3. Click "Report". Actual results: Error: File './coredump' is not a coredump Expected results: Relevant coredump is found and issue can be reported using GNOME Abrt.
I am experiencing the same issue on latest Fedora 33 Workstation (20200906). When the problem happens, nothing is printed out in the journalctl.
Proposed as a Blocker for 33-final by Fedora user lruzicka using the blocker tracking app because: I am proposing this to be a final blocker because it breaks the cited criterion. I believe that a problem reporting application that cannot actually report a problem should not be let into the final product. *Default application functionality* * All applications that can be launched using the standard graphical mechanism after a default installation of Fedora Workstation on the x86_64 architecture must start successfully and withstand a basic functionality test.
This is almost certainly a duplicate of bug 1860616, already accepted as a blocker. *** This bug has been marked as a duplicate of bug 1860616 ***