Bug 1303326 - [abrt] corrupted "Show log" window missing the summary of the reporting process
Summary: [abrt] corrupted "Show log" window missing the summary of the reporting process
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: libreport
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Filak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1304518 1306167 (view as bug list)
Depends On:
Blocks: 1499874
TreeView+ depends on / blocked
 
Reported: 2016-01-30 20:03 UTC by Joachim Frieben
Modified: 2017-10-13 10:33 UTC (History)
11 users (show)

Fixed In Version: libreport-2.6.4-2.fc24
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-10 13:54:48 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Screenshot of corrupted "Show log" window (11.54 KB, image/png)
2016-01-30 20:03 UTC, Joachim Frieben 		no flags Details
View All

Description Joachim Frieben 2016-01-30 20:03:55 UTC 
Created attachment 1119673 [details]
Screenshot of corrupted "Show log" window

Description of problem:
As of current Fedora rawhide, the "Show log" window does not show any useful content. The text box looks corrupted; see attached screenshot.

Version-Release number of selected component (if applicable):
abrt-2.7.1-1.fc24

How reproducible:
Always

Steps to Reproduce:
1. Report a bug by means of the "Problem Reporting" utility.
2. Check report summary.

Actual results:
Log window looks corrupted with no useful content.

Expected results:
Log window reports the summary of the completed reporting process.

Additional info:
None
Comment 1 Jakub Filak 2016-02-08 17:42:45 UTC 
*** Bug 1304518 has been marked as a duplicate of this bug. ***
Comment 2 Jakub Filak 2016-02-09 05:42:16 UTC 
Upstream commit https://github.com/abrt/libreport/commit/18a1e903c35d72cdb2f436237235d70a3a798cf4 fixes the bug.
Comment 3 Matej Habrnal 2016-02-10 08:40:27 UTC 
*** Bug 1306167 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.