Description of problem: Version-Release number of selected component (if applicable): $ uname -r 4.11.3-200.fc25.x86_64 How reproducible: Every time I resume from suspended state when docked and lid closed I get that behaviour. Steps to Reproduce: 1. Laptop is running on external display. Lid is closed. Internal display is not active. 2. Suspend laptop. 3. Resume laptop by using power switch on docking station (do not open lid). Actual results: Internal display is now primary, but laptop lid is closed. External display is now behaving as secondary. Expected results: When laptop is closed, its internal display should always be off, even when resuming from suspend. Additional info: If I open the lid after the laptop resumes, and then close it again, the internal display is finally powered off and the external display becomes the only one, so I do that to correct the behaviour. The bad behaviour also happened when I disabled Wayland from the GDM configuration and rebooted the computer. Also bad behaviour is independent on whether a user is logged in. Suspending/resuming from the GDM login screen causes the same issue. The affected laptop is a ThinkPad T450s with a standard IBM docking station and an external Dell display.
I updated my system to the Fedora 26 (before release), and as of the latest kernel upgrade this bug is no longer present: $ uname -r 4.11.4-300.fc26.x86_64
I updated my system to Fedora 26 Alpha, and as of the latest kernel upgrade this bug is no longer present: $ uname -r 4.11.4-300.fc26.x86_64
Updated to Fedora 27 and the big is back.
Updated to Fedora 27 and the bug is back.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
I am also experiencing this problem with Fedora 27.
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.15.3-300.f27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
This problem is now solved.