Bug 2533 – Xconfigurator has duplicate monitor entries (typo?)

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 2533 - Xconfigurator has duplicate monitor entries (typo?)

Summary:	Xconfigurator has duplicate monitor entries (typo?)

Status:	CLOSED CURRENTRELEASE

Aliases:	None

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

Priority	high Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Preston Brown
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-05-04 02:54 EDT by alex2
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-27 16:25:30 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 alex2 1999-05-04 02:54:30 EDT

The settings that Xconfigurator saves for the monitor
Acerview 78ie are incorrect. First of all, there are two
copies of Acerview 78ie listed. But mainly, the settings for
modes "1152x864" and "1024x768" are wroong. They cause a
complete crash on my computer when trying to use those
modes. This monitor can support a maximum refresh rate of
85Hz at "1024x768" as opposed to the listed 100Hz, and a
maximum of ~75Hz at "1152x864" (it can do 78Hz). The setting
of 100Hz is listed for that mode also. Commenting those
modes out fixed the problem.

Thanks for your time,
Alex

Comment 1 David Lawrence 1999-05-04 14:12:59 EDT

We do not have an AcerView of that model in our lab. The duplicate
entry has been observed. This is being assigned to a developer.

Comment 2 Preston Brown 1999-08-27 16:25:59 EDT

this will be fixed in the next release.

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