Bug 129992 - Major screen resolution problem at default login screen
Summary: Major screen resolution problem at default login screen
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-16 13:40 UTC by phl73@comcast.net
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2005-04-22 06:00:47 UTC


Attachments (Terms of Use)

Description phl73@comcast.net 2004-08-16 13:40:06 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; 
Maxthon; .NET CLR 1.0.3705; .NET CLR 1.1.4322)

Description of problem:
I've just upgraded my HP z7020 from RH9 to FC2 (with WinXP Home as 
dual boot using Grub). Everything went smoothly with one exception. I 
selected the generic 1440x900 LCD setting for my screen (17" with 
1440x900 native resolution) and, once past the GUI login screen, it 
works well. However, the GUI login screen resolution is practically 
impossible to work with.

FC2 boots to a fullscreen login and then, after a few seconds, 
switches to the GUI login screen. The letters on the GUI login screen 
are each at least 2 inches wide!  I see the word "enter" across the 
middle of the screen and part of the word "your" below it (with the 
bottom third of the letters cut off).  The word "your" is overlaid on 
top of what looks to be the upper half of the letters "lang".

I can enter the userid <enter> and password <enter> and the system 
changes back to the correct resolution for the rest of the startup 
process that then ends with GNOME up and running with the correct 
resolution.

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


How reproducible:
Always

Steps to Reproduce:
1. Boot my HP zd7020 and wait for the login screen.
2.
3.
    

Additional info:

Comment 1 Matthias Clasen 2005-04-22 06:00:47 UTC
We fixed dpi issues in gdmgreeter recently, which were probably causing these
symptoms.


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