Bug 1098320

Summary: Custom partitioning screen rendering broken at 1024x768 in Russian (RHEL 7 RC)
Product: Red Hat Enterprise Linux 7 Reporter: Adam Williamson <awilliam>
Component: anacondaAssignee: David Shea <dshea>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: mbanas, mkovarik
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-19.31.83-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 14:01:21 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
screenshot of the incorrect display
none
the actual culprit none

Description Adam Williamson 2014-05-15 19:23:57 UTC
Similar to https://bugzilla.redhat.com/show_bug.cgi?id=1031850 for Fedora 20/21, the custom partitioning screen displays incorrectly at 1024x768 resolution with Russian locale. Other spokes appear to display correctly. Screenshot attached.

Comment 1 Adam Williamson 2014-05-15 19:24:18 UTC
Created attachment 896046 [details]
screenshot of the incorrect display

Comment 3 David Shea 2014-05-15 19:33:36 UTC
Created attachment 896048 [details]
the actual culprit

In both cases the label you initially see when entering the custom spoke ("When you create mount points for...") is not the problem. It's the note that's displayed with the partition configuration, as pictured in the attached image.

Comment 4 David Shea 2014-08-05 15:52:22 UTC
Fixed in upstream commit b189740b01a81f528a1752060eedbeea190fc10c

Comment 8 errata-xmlrpc 2015-03-05 14:01:21 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0312.html