Bug 3917 – Xconfigurator won't list 32-bit modes if the server supports 8, 16, and 24-bit as well

Bug 3917 - Xconfigurator won't list 32-bit modes if the server supports 8, 16, and 24-bit as well

Summary:	Xconfigurator won't list 32-bit modes if the server supports 8, 16, and 24-bi...

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	Xconfigurator (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-07-06 11:10 EDT by Nalin Dahyabhai
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-08-23 12:17:13 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Nalin Dahyabhai 1999-07-06 11:10:11 EDT

This happends with an ATI Mach64 GB in a Dell Optiplex GX1.
The default display mode Xconfigurator offers is
1280x1024@32 bits, but if you turn that down only the 8-,
16-, and 24-bit modes are listed in the next screen.

Comment 1 Preston Brown 1999-08-23 12:17:59 EDT

24bpp and 32bpp are internally treated the same by Xconfigurator.  It
will first try to determine a 32bpp mode, and if the driver doesn't
support it, it will use a 24bpp mode.  Therefore even if it describes
the "24 bit modes", the mode actually selected will be 32bit if
necessary.

A bit confusing, and could probably use some work, but Xconfigurator
is being rewritten anyway, so this problem will go away.

Comment 2 Pekka Savola 2000-01-17 03:50:59 EST

I got very confused about this too.  I'd recommend changing "24" bit to  "24/32"
bit as a quick workaround; this would at least give a hint that 32 bpp hasn't
just been forgotten.

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