Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 85078 - Russian letters do not show up in login screen
Summary: Russian letters do not show up in login screen
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gdm
Version: 8.0
Hardware: i586
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-02-25 13:55 UTC by Need Real Name
Modified: 2007-04-18 16:51 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-02-25 16:54:12 UTC


Attachments (Terms of Use)

Description Need Real Name 2003-02-25 13:55:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3; Linux)

Description of problem:
I am using Russian locale (ru_RU.UTF8).
After changing the login screen using gdmsetup the Russian words on the bottom (options etc.) do not show up - I see only buttons but
no text at all.

I don't remember exactly, but at the time when I just installed RedHat from CDs everything was OK.

Letters are missing in all of the login screens.

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


How reproducible:
Always

Steps to Reproduce:
1. Install RH8.0 with Russian locale (or maybe just change it after installation  - I hadn't tried)
2. Run gdmsetup
3. Choose any other login screen instead of BlueCurve (you can change it then back to BlueCurve - the bug will stay)
    

Actual Results:  Missing russian labels to the right of the buttons at the bottom of the screen

Expected Results:  Russian labels to the right of the buttons at the bottom of the screen

Additional info:

Comment 1 Havoc Pennington 2003-02-25 16:54:12 UTC
This should be fixed in latest betas.


Note You need to log in before you can comment on or make changes to this bug.