Red Hat Bugzilla – Bug 511909
screen output is weird after screensaver wakeup
Last modified: 2010-05-10 19:15:06 EDT
Description of problem: if gnome-screensaver starts and i wake up my machine my screen looks weird. the colors are dark and lo-res and the fonts have hard edges instead of aliasing. it is almost like the screens contrast is boosted and the brightness is lowered. logging out solves the problem. i'm using an hp pavilion dv7 1174ca laptop with nvidia ge9600m card. i am using the nouveau driver because i haven't been able to get the proprietary nvidia driver working yet. this could be a problem with X but i'm not sure.
when it happened i took a screenshot and after logging back in i looked at it and it was normal.
i just watched it happen and it started when the screen would normally start to dim before the screensaver starts up.
Version-Release number of selected component (if applicable):gnome-screensaver-2.27.0-2.fc12.x86_64
Steps to Reproduce:
1.let computer go into screensaver mode
2.wake up from screensaver mode
Actual results:high contrast and low brightness
Expected results:normal display
i just looked at my xorg log file and these two lines were at the end.
(II) NOUVEAU(0): nv50_crtc_gamma_set is called for CRTC0.
(II) NOUVEAU(0): NV50CrtcGammaSet is called for CRTC0
it repeated a bunch of times.
i'm sorry if this is not a screensaver issue but i'm not sure if this is xorg, or nouveau or gnome-screensaver
thanks for your help.
Can you post your /var/log/Xorg.0.log please. Also, is there any particular reason you're booting without kernel modesetting? And does this issue still occur with it turned on?
i generally just boot with no added kernel options, i'm not even sure what modesetting does. i'll have to get a hold of the computer that this is happening on before i can get you that log file. the machine has an ati graphics card and without the fglrx driver so that might also be the issue. im going to try installing the fglrx driver and if it still happens i'll post back with the log file.
Um, the output you posted above is from the nouveau driver, which is for NVIDIA GPUs, where does an ATI card come into this?
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions).
Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you.
If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.
More information and reason for this action is here:
Jeremy, your Comment #3 caused some confusion. Could you please attach the log asked for in Comment #2 as well as verify what card/driver you were using when you found this bug?
Fedora Bugzappers volunteer triage team
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
Closing as INSUFFICIENT_DATA.