Description of problem: When display is put to sleep, Xorg continues to show blank screen on waking up - but text consoles still work (so display is actually awake again). Version-Release number of selected component (if applicable): xorg-x11-drv-intel-2.99.916-3.20141117.fc21.i686 kernel-3.18.7-200.fc21.i686 How reproducible: Always. Steps to Reproduce: 1. Activate "Put display to sleep when inactive for..." 2. Wait the configured time 3. Press a key to wake up display Actual results: Display wakes up (backlight comes on, and text consoles work), but Xorg continues to display a blank screen. Expected results: Normal session unlock screen Additional info: 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c) journalctl shows this over and over: Feb 13 11:01:54 elissa.gathman.org kernel: [drm:intel_connector_check_state] *ERROR* wrong connector dpms state Feb 13 11:01:54 elissa.gathman.org kernel: [drm:intel_connector_check_state] *ERROR* active connector not linked to encoder Feb 13 11:01:54 elissa.gathman.org kernel: [drm:intel_connector_check_state] *ERROR* encoder->connectors_active not set Feb 13 11:01:54 elissa.gathman.org kernel: [drm:intel_connector_check_state] *ERROR* WARN_ON(!encoder->base.crtc) Feb 13 11:01:54 elissa.gathman.org kernel: [drm:check_encoder_state] *ERROR* encoder's hw state doesn't match sw tracking (expected 0, found 1) Feb 13 11:01:54 elissa.gathman.org kernel: [drm:intel_connector_check_state] *ERROR* wrong connector dpms state Feb 13 11:01:54 elissa.gathman.org kernel: [drm:intel_connector_check_state] *ERROR* active connector not linked to encoder Feb 13 11:01:54 elissa.gathman.org kernel: [drm:intel_connector_check_state] *ERROR* encoder->connectors_active not set Feb 13 11:01:54 elissa.gathman.org kernel: [drm:intel_connector_check_state] *ERROR* WARN_ON(!encoder->base.crtc) Feb 13 11:01:54 elissa.gathman.org kernel: [drm:check_encoder_state] *ERROR* encoder's hw state doesn't match sw tracking (expected 0, found 1) Using MATE desktop and mate-screensaver kernel-3.16.7 works (but gets tainted during boot process) bug#624320 looks similar
Workaround: disable putting display to sleep.
Suspend/resume work correctly. I tried another workaround of suspending by closing the lid after locking up Xorg as described, to see if resume would reset things. Resume works, and restores the locked up Xorg perfectly. mate-screensaver-1.8.1-1.fc21.i686 Next up is to try an alternate screensaver.
Now, suspend/resume no longer restore Xorg. Alt-consoles still work. Screen displays background on resume instead of blank screen. kernel-3.18.9-200.fc21.i686
Still broken in kernel-3.19.3-200.fc21.i686
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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 this bug is closed as described in the policy above. 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.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.