Bug 1808848

Summary:	report-gtk crashes when generating local backtrace
Product:	[Fedora] Fedora	Reporter:	Clemens Eisserer <linuxhippy>
Component:	abrt	Assignee:	abrt <abrt-devel-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	31	CC:	abrt-devel-list, ekulik, jakub, jmilan, mhabrnal, michal.toman, mkutlak, mmarusak
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-03-01 15:39:40 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 Clemens Eisserer 2020-03-01 15:34:14 UTC

Description of problem:

After a recent update, abrt crashes when fetching debug packages after the server-side retrace failed.

After restarting abrt the original crash report is gone, but there is a new one titled "libreport".

In dmesg I only see the following entry:

2447.930321] report-gtk[1921]: segfault at 7fb29085cd10 ip 00007fb1befe2f64 sp 00007fff5777ea88 error 6 in libc-2.30.so[7fb1bef5e000+14f000]


Version-Release number of selected component (if applicable):

abrt-2.14.0-1.fc31.x86_64
libreport-gtk-2.12.0-1.fc31


How reproducible:
Every time

Steps to Reproduce:
1. report a crash using abrt
2. server side retrace failes, agree with downloadig debug info packages locally
3. report-gtk crashes

Actual results:
report gtk crashes, original abrt report in GUI vanishes

Expected results:


Additional info:

Comment 1 ekulik 2020-03-01 15:39:40 UTC


*** This bug has been marked as a duplicate of bug 1807924 ***