Bug 1304518

Summary: Can't read gnome-abrt's reporting log
Product: [Fedora] Fedora Reporter: Giulio 'juliuxpigface' <juliux.pigface>
Component: libreportAssignee: abrt <abrt-devel-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: abrt-devel-list, jfilak, mhabrnal, michal.toman, mmilata, phelia
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-08 17:42:45 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:
Attachments:
Description Flags
gnome-abrt's log opened
none
gnome-abrt's closed log none

Description Giulio 'juliuxpigface' 2016-02-03 21:44:20 UTC
Created attachment 1120912 [details]
gnome-abrt's log opened

Description of problem:
I'm running the Gnome+Wayland session, on a qemu-kvm guest installed from Fedora Workstation the 20160130 Rawhide compose.

Version-Release number of selected component (if applicable):
gnome-abrt-1.2.1-2.fc24.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Report a problem with gnome-abrt.
2.Try to read the log of the process.

Actual results:
There aren't details about the process. The responsible widget seems to have an invalid size.

Expected results:
Users should be able to read the details related to the reporting process.

Additional info:
I'm attaching two screenshot in order to try to explain this issue.

Comment 1 Giulio 'juliuxpigface' 2016-02-03 21:45:02 UTC
Created attachment 1120913 [details]
gnome-abrt's closed log

Comment 2 Jakub Filak 2016-02-08 17:42:45 UTC
Thank you for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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