Red Hat Bugzilla – Bug 1293729
Display image is sometimes corrupted after monitor powersave
Last modified: 2016-07-19 15:14:26 EDT
Created attachment 1108710 [details]
Screenshot of currupted display.
Description of problem:
I have had my display become corrupted after using it for a while. I believe that it is usually happens after using it for more than one day since boot.
Version-Release number of selected component (if applicable):
I don't know how to make it happen but it has been happening regularly for a while (perhaps a year).
Steps to Reproduce:
1. Boot Fedora 22 and log in
2. Use the OS as I regularly do
Display becomes corrupted
Display should not become corrupted.
Created attachment 1108711 [details]
journalctl -b _COMM=gdm-x-session
Created attachment 1108712 [details]
Now I just experienced something new. I walked away from my PC with the screen corrupted. The display went into powersave mode. Then, when I came back and entered my password, the display corruption is gone.
Looking at my screenshot attachment, that doesn't appear to be corrupted. So, whatever is making the display look corrupted is not getting picked up by the Screenshot program. Could it be that the monitor is defective and sometimes when it comes out of powersave mode the display is corrupted?
I just did a bit more testing. I repeated put the monitor into powersave mode using the Super-L key combination.
At first, I wasn't able to reproduce the screen corruption.
However, I was able to reproduce it by first running Google Chrome and then putting the monitor into powersave mode with Super-L. It doesn't happen every time but it has happened three times so far.
I found a similar problem report at
I was just able to get the color problem to happen after monitor powersave without Google Chrome running.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
This problem has not occurred since I upgraded the computer to Fedora 23.