Created attachment 1473544 [details] kernel log messages of the affected 4.17.12 kernel Description of problem: This is essentially bug #1601383 again. Booting 4.17.12-200.fc28 gives a lot of flickering, some nouveau related error messages and while it knows about the display attached to the display port of the dock, there's no output there. The previous 4.17.10-200.fc28 kernel works fine in that regard (it "forgets" about the external display when undocked but that's an old, different problem). Version-Release number of selected component (if applicable): kernel-4.17.12-200.fc28.x86_64 xorg-x11-drv-nouveau-1.0.15-4.fc28.x86_64 How reproducible: reproducible Steps to Reproduce: 1. Boot Actual results: - boot takes longer - flickers back and forth a few times between text and graphical modes before displaying the login screen - only the internal display shows content, the external monitor stays dark even though it seems to be recognized after booting, the GNOME desktop spans both displays (the top bar isn't shown on and the mouse cursor can move off the visible screen). - much more nouveau related error messages than the 4.17.10 kernel Expected results: - external monitor displays content - no excessive flickering, error messages
Created attachment 1473546 [details] kernel log messages of the unaffected 4.17.10 kernel
NB: the laptop is a Lenovo Thinkpad P50
Hmm, I rebooted into 4.17.11 which didn't exhibit the problem, then back into 4.17.12 and it worked also -- so reproducibility is unclear and the previous bug #1601383 wasn't really fixed (but the conditions changes so the bug didn't occur).
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.