Description of problem: When I go from undocked to docked, the laptop monitor goes blank and the external monitors don't get activated. I have to undock, control + alt + f2, control + alt + f1, the screen wakes, and then usually when I dock this second time the laptop screen stays awake and so I can then go activate the external monitors. If it has the same issue on that second dock attempt, it has always worked on the third dock attempt. Version-Release number of selected component: plasma-systemsettings-5.4.2-1.fc24 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /bin/systemsettings5 crash_function: QXcbScreen::mapFromNative executable: /usr/bin/systemsettings5 global_pid: 7017 kernel: 4.3.0-0.rc6.git2.1.fc24.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QXcbScreen::mapFromNative at qxcbscreen.cpp:249 #1 QXcbWindow::handleEnterNotifyEvent at qxcbwindow.cpp:2327 #2 QXcbConnection::handleXcbEvent at qxcbconnection.cpp:1083 #3 QXcbConnection::processXcbEvents at qxcbconnection.cpp:1527 #4 QObject::event at kernel/qobject.cpp:1239 #5 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3716 #6 QApplication::notify at kernel/qapplication.cpp:3499 #7 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:965 #8 QCoreApplication::sendEvent at kernel/qcoreapplication.h:224 #9 QCoreApplicationPrivate::sendPostedEvents at kernel/qcoreapplication.cpp:1593
Created attachment 1089021 [details] File: backtrace
Created attachment 1089022 [details] File: cgroup
Created attachment 1089023 [details] File: core_backtrace
Created attachment 1089024 [details] File: dso_list
Created attachment 1089025 [details] File: environ
Created attachment 1089026 [details] File: exploitable
Created attachment 1089027 [details] File: limits
Created attachment 1089028 [details] File: maps
Created attachment 1089029 [details] File: mountinfo
Created attachment 1089030 [details] File: open_fds
Created attachment 1089031 [details] File: proc_pid_status
Created attachment 1089032 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.