Bug 101511 - login dialog occupies same place on screen as hostname info
Summary: login dialog occupies same place on screen as hostname info
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux Beta
Classification: Retired
Component: gdm
Version: beta1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks: CambridgeTarget
TreeView+ depends on / blocked
 
Reported: 2003-08-02 02:26 UTC by Elton Woo
Modified: 2007-04-18 16:56 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-11-10 22:43:50 UTC
Embargoed:


Attachments (Terms of Use)

Description Elton Woo 2003-08-02 02:26:52 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703

Description of problem:
When gdm is setup for automatic login the informational message
shows on screen (in black letters) but is unreadable, because this
info is displayed *behind* the white letters which say: "Welcome
to {hostname / machinename}.

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

How reproducible:
Always

Steps to Reproduce:
1. Configure gdm for automatic login of a user.
2. Reboot machine
3. (Try to) read info that appears in black *behind* the welcome message
    

Actual Results:  Dialog information on screen: "Welcome to {host / machine name}
obliterates other infomation, viz "user {usename} will login
in {n} seconds / minutes"

Expected Results:  These two infomational messages should be readable with one
message
above the other.

Additional info:

Using an nVidia video card, but nVidia drivers are NOT installed.
Instead the 'nv' driver is in use by the system.

Comment 1 Elton Woo 2003-11-02 17:34:58 UTC
I respectfully submit this should be marked as closed. The situation has
been corrected with the last few updates from rawhide.

Comment 2 Ray Strode [halfline] 2004-11-10 22:43:50 UTC
Hi Elton,
Sure.  Closing now.


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