Bug 1875418

Summary:	"File './coredump' is not a coredump" error when trying to report an issue using gnome-abrt
Product:	[Fedora] Fedora	Reporter:	Daniel Rusek <drusek>
Component:	gnome-abrt	Assignee:	Jakub Filak <jakub>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	33	CC:	abrt-sig, digitalfreak, ekulik, jakub, kparal, lruzicka, mail, mmarusak, msuchy, robatino
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-07 14:18:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel Rusek 2020-09-03 14:02:05 UTC

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.

Comment 1 Lukas Ruzicka 2020-09-07 08:56:51 UTC

I am experiencing the same issue on latest Fedora 33 Workstation (20200906).

When the problem happens, nothing is printed out in the journalctl.

Comment 2 Fedora Blocker Bugs Application 2020-09-07 11:04:46 UTC

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.

Comment 3 Kamil Páral 2020-09-07 14:18:04 UTC

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 ***