Bug 604037

Summary: abrt backtrace gui not resizing automatically
Product: [Fedora] Fedora Reporter: Pratyush Sahay <pratyush.a.sahay>
Component: abrtAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: anton, dfediuck, dvlasenk, iprikryl, jmoskovc, kklic, npajkovs
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-15 09:09:52 UTC Type: ---
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
scerenshot of the abrt backtrace report window showing its extra large size. none

Description Pratyush Sahay 2010-06-15 08:59:45 UTC
Created attachment 424079 [details]
scerenshot of the abrt backtrace report window showing its extra large size.

Description of problem: The GUI containing the ABRT backtrace for a crash is not resizing automatically for different screens sizes. For my Thinkpad R60, i always have to manually resize the window to see the CANCEL , REFRESH and SEND REPORT buttons. This problem was not there for sure in the abrt in F12.


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


How reproducible: Everytime the backtrace window is opened in abrt for filing the crash report.


Steps to Reproduce:
1. Click on a bug in the abrt logger window, Click Report and choose bugzilla.
2. The new window that opens is having far higher resolution than the screen size.
3.
  
Actual results: The abrt backtrace window lacks automatic resize as per the screen size available


Expected results: The gui should resize on its own, with scroll bars to show whole of the content.


Additional info:

Comment 1 Nikola Pajkovsky 2010-06-15 09:09:52 UTC

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