Bug 74861

Summary:	dialog has foreign chars when asking about X setup
Product:	[Retired] Red Hat Linux	Reporter:	Josiah Royse <jroyse>
Component:	gdm	Assignee:	Havoc Pennington <hp>
Status:	CLOSED DUPLICATE	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	harald
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-02-21 18:49:42 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:

Description Josiah Royse 2002-10-02 12:20:07 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
When Xfree fails to load under runlevel 5 on the first boot (before first-boot)
dialog is called asked if you want to try to configure the X setup again.  The
border and Yes <No> is unreadable.

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


How reproducible:
Always

Steps to Reproduce:
1. Install with an ATI Radeon VE, Samsung SyncMaster 753df (leave as probed)
2. Choose 1280x1024 16bit (works great up to 1400x1050 with
redhat-config-xfree86 BTW- might be that the SyncMaster 753df isn't probed
correctly?)
3. Hit next to finish install and reboot (the Test button hangs the display)
	

Actual Results:  During the next reboot, dialog comes up with some hard to read
text for the buttons, scaring the newbies.

Expected Results:  Dialog showing normal English, making it easy to reconfigure X.

Additional info:

This was an all English install.

Comment 1 Harald Hoyer 2002-10-02 12:27:44 UTC

- the console used was not switched to unicode
- dialog was not called with latin-1 charset

Comment 2 Brent Fox 2002-10-02 15:18:14 UTC

That failure screen you are seeing is part of GDM, if I recall correctly.  GDM
tries to start, and after failing a few times, it pops up a message.

Changing component to gdm.

Comment 3 Havoc Pennington 2002-12-20 00:27:35 UTC


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

Comment 4 Red Hat Bugzilla 2006-02-21 18:49:42 UTC

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.