Bug 1808848 - report-gtk crashes when generating local backtrace
Summary: report-gtk crashes when generating local backtrace
Keywords:
Status: CLOSED DUPLICATE of bug 1807924
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: abrt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-01 15:34 UTC by Clemens Eisserer
Modified: 2020-03-01 15:39 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-01 15:39:40 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.