Bug 515306

Summary:	does not honor gamma
Product:	[Fedora] Fedora	Reporter:	Bill Nottingham <notting>
Component:	xorg-x11-drv-intel	Assignee:	Kristian Høgsberg <krh>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	ajax, jmccann, mcepl, rvokal, wally, xgl-maint
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-10-09 15:47:31 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	473302, 509829

Description Bill Nottingham 2009-08-03 16:37:51 UTC

Description of problem:

As of rawhide, X/the intel driver no longer respect gamma, whether passed
in the config file, or on the command line. The in-server value is updated, but the display never changes.

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

kernel-2.6.30-6.fc12.x86_64
xorg-x11-server-Xorg-1.6.99-22.20090724.fc12.x86_64
xorg-x11-drv-intel-2.8.0-2.fc12.x86_64

How reproducible:

100%

Steps to Reproduce:
1. run xgamma

Actual results:

No changes.

Expected results:

Changes.

Additional info:

Would use a later kernel, but can't due to bug 514106.

Comment 1 Matěj Cepl 2009-10-09 11:56:50 UTC

*** Bug 528049 has been marked as a duplicate of this bug. ***

Comment 2 Matěj Cepl 2009-10-09 11:59:04 UTC

Isn't bug 528048 also duplicate of this? Bill, you seem to fill our bugzilla with all these gamma-realted bugs :). We should really do something about it, I guess.

Comment 3 Matěj Cepl 2009-10-09 12:00:03 UTC

*** Bug 520840 has been marked as a duplicate of this bug. ***

Comment 4 Matěj Cepl 2009-10-09 12:01:54 UTC

*** Bug 522849 has been marked as a duplicate of this bug. ***

Comment 5 Bill Nottingham 2009-10-09 15:47:31 UTC

No, not really. This bug was fixed; it then broken again differently.