Bug 32219 - Xconfigurator XF86Config-4 output error
Summary: Xconfigurator XF86Config-4 output error
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: Xconfigurator   
(Show other bugs)
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Preston Brown
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-19 11:42 UTC by adler
Modified: 2007-04-18 16:32 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-03-19 11:42:29 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description adler 2001-03-19 11:42:20 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-0.1.25smp i686)


When running the Xconfigurator I select the field for configuring my X11
server to run in 24bpp under all the monitor resolutions offerd. When the
Xconfigurator goes to test the server, it starts up the server in 640x480
when I expected it to startup in 1600x1200, (although I did select 640x480
at one of the resolutions I wanted the X11 server to run at.) After exiting
the Xconfigurator and starting X11 (i.e. startx), the server comes up in
16bpp at 640x480. I then have to edit the XF86Config-4 file and change the
places which read "default 16" to "default 24". I only seem to get this
problem when running Xconfigurator stand alone. during the standard
installation process, the X11 server resolutions are set properly. At least
this is what happend when I installed fisher, I then upgraded to Wolverine
from fisher so the XF86Config-4 file was probably preserved.

Reproducible: Always
Steps to Reproduce:
1.Run Xconfigurator
2.Choose 24bpp
3.

Comment 1 Preston Brown 2001-03-19 15:02:10 UTC
This bug has been fixed in recent rawhide versions of Xconfigurator.



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