Bug 1299869 - initial -setup-gui does not fill the whole display
Summary: initial -setup-gui does not fill the whole display
Keywords:
Status: CLOSED DUPLICATE of bug 1160891
Alias: None
Product: Fedora
Classification: Fedora
Component: initial-setup
Version: rawhide
Hardware: armhfp
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Kolman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-19 12:50 UTC by Lukas Brabec
Modified: 2016-02-12 19:12 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-12 19:12:08 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
screenshot 1 (842.77 KB, image/jpeg)
2016-01-19 12:50 UTC, Lukas Brabec 		no flags Details
screenshot 2 (899.06 KB, image/jpeg)
2016-01-19 12:50 UTC, Lukas Brabec 		no flags Details
screenshot 3 (909.33 KB, image/jpeg)
2016-01-19 12:51 UTC, Lukas Brabec 		no flags Details
View All

Description Lukas Brabec 2016-01-19 12:50:22 UTC 
Created attachment 1116168 [details]
screenshot 1

Description of problem:
On arm rawhide 20160115, the initial-setup starts, but the user interface is not stretched to fill the whole display. Instead, it occupies a small space in upper left corner. The user interface itself works and the size of UI area changes according to the last spoke visited (see screenshots).

Version-Release number of selected component (if applicable):
initial-setup-0.3.38-1
initial-setup-gui-0.3.38-1
Fedora-Xfce-armhfp-rawhide-20160115-sda.raw.xz


Steps to Reproduce:
1. create bootable sd card with xfce arm rawhide 20160115
2. power up the board and boot
3. initial-setup-gui is not shown in fullscreen
Comment 1 Lukas Brabec 2016-01-19 12:50:48 UTC 
Created attachment 1116169 [details]
screenshot 2
Comment 2 Lukas Brabec 2016-01-19 12:51:18 UTC 
Created attachment 1116170 [details]
screenshot 3
Comment 3 Martin Kolman 2016-02-12 19:12:08 UTC 

*** This bug has been marked as a duplicate of bug 1160891 ***
Note You need to log in before you can comment on or make changes to this bug.