Bug 832700 - Gamma reset to 1.0 on VT switch or suspend/resume, xgamma inconsistent
Gamma reset to 1.0 on VT switch or suspend/resume, xgamma inconsistent
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-06-16 13:03 EDT by James Ettle
Modified: 2013-07-31 13:46 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-31 13:46:05 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description James Ettle 2012-06-16 13:03:02 EDT
Description of problem:
The X server resets any custom-set gamma settings to 1.0 following a VT switch (or suspend-resume cycle). Note that when it does this, it still thinks that the RGB gamma values are what was set -- but the display is definitely otherwise.

For example:

1. Run xgamma:

$ xgamma -rgamma 0.75 -bgamma 0.7 -ggamma 0.7
-> Red  1.000, Green  1.000, Blue  1.000
<- Red  0.750, Green  0.700, Blue  0.700

   and note the change in colours.

2. VT switch away and back to X again. Note that it's bluer and brighter.
3. Run xgamma again to find out what's going on:

$ xgamma
-> Red  0.750, Green  0.700, Blue  0.700

   so the programmed values are still there.

4. Run xgamma -gamma 1.0 to check that's the real current setting.

I've only tested this on Intel HD3000 graphics as this is the only hardware at my disposal.

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

How reproducible:

Actual results:
Gamma reset to 1.0 (and xgamma lies)

Expected results:
Consistent, persistent gamma settings.
Comment 1 Fedora End Of Life 2013-07-03 15:22:49 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Fedora End Of Life 2013-07-31 13:46:09 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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