Bug 1311223

I'm seeing something similar, but I'm not sure if it's an x driver bug, a kernel bug or an interaction. Today I updated to xorg-x11-drv-intel.x86_64 2.99.917-19.20151206.fc23 and xorg-x11-drv-nouveau.x86_64 1:1.0.12-3.fc23. If I boot with the latest kernel (kernel-4.3.5-300.fc23.x86_64), when I wake from sleep I get a black screen with a cursor that responds to mouse movement. I can switch to a text tty and log in.  If I reboot and select kernel kernel-4.3.4-300.fc23.x86_64, resume works.

MacBook Pro (MBP 6,2), Xorg.0.log shows nouveau and intel drivers loaded, but nouveau selected.

I'm having the same issue (screen stays black after coming back from display sleep) with:

kernel-4.3.5-300.fc23.x86_64
xorg-x11-drv-intel-2.99.917-16.20150729.fc23.x86_64

If I upgrade xorg-x11-drv-intel to 2.99.917-19.20151206.fc23, and reboot, the screen stays black when coming back from display sleep.  If I downgrade back to 2.99.917-16.20150729.fc23.x86_64, the screen comes back on after display sleep. I've tried digging into the system journal but I can't find anything useful there.

Here's a peculiar workaround I found:

* Boot with 2.99.917-19 loaded
* Log into GNOME
* Press Windows-L to lock the screen
* Wait a few seconds for the display to sleep
* Wiggle the mouse (screen stays black)
* Connect an external display via DisplayPort
* Screen comes on and I can log in
* Disconnect external display

That's not a pleasurable workaround by any means, but I hope it helps with the troubleshooting. :)

I'm on a 4th gen ThinkPad X1 Carbon with an i7-5600U with Intel HD Graphics 5500.

After more testing, the old kernel just let one sleep/wake cycle work. The second would result in the black screen on wake. But if I downgrade the nouveau driver to xorg-x11-drv-nouveau-1.0.12-1.fc23.x86_64, things work. So it seems like a common issue in nouveau and intel drivers.

Same here. Downgrade of the xorg-x11-drv-nouveau package helped, so it must be an issue in the latest version there.

(In reply to Max from comment #4)
> Same here. Downgrade of the xorg-x11-drv-nouveau package helped, so it must
> be an issue in the latest version there.

I can confirm that. For the time being you can remove the newest and install previous:

(I have Fedora 23)
sudo dnf remove xorg-x11-drv-intel;
sudo dnf install xorg-x11-drv-intel-2.99.917-16.20150729.fc23.x86_64;


The appears in version 2.99.917-19.20151206.fc23

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.