Bug 187499 - Preferences ->Screen Resolution not showing all resolution options
Summary: Preferences ->Screen Resolution not showing all resolution options
Keywords:
Status: CLOSED DUPLICATE of bug 183308
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-applets
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-31 13:18 UTC by Need Real Name
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-06-14 14:44:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2006-03-31 13:18:33 UTC
Description of problem:
The screen resolution is not displaying all of the options available.  If I go
under System -> Administration -> Display I may select a resolution of 1600x
1200.  If I then go under System -> Preferences -> Screen Resolution I only see
options for 1024x768 800x600 600x480.

This occurs even if I reset XWindows or reboot the machine.  To troubleshoot, I
manually edited /etx/X11/xorg.conf and removed all screen resolutions except
1600x1200.  I then entered init 3 (text mode) then back to init 5 to reset
xwindows.  I believe the login screen is 1600x1200, but when I login with the
user account, under preferences->Screen Resolution I now see an option for
1280x1024, but not 1600x1200.

The software has correctly detected my graphics card as a GForce 6600 and my
monitor as a ViewSonic 17PS.


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

Fedora Core 5

Comment 1 Mike A. Harris 2006-05-19 09:49:53 UTC
Bug is misfiled against incorrect component (XFree86 does not exist in
Fedora Core 5, and the config tool is also not part of X)

Reassigning to gnome-applets for gui RandR resolution tool (not part of
X).

Comment 2 Mike A. Harris 2006-06-14 14:44:23 UTC

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


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