Description of problem: resuming from suspend on a dual motior machine Version-Release number of selected component: plasma-workspace-5.4.2-4.fc22 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /bin/systemmonitor crash_function: QXcbWindow::handleClientMessageEvent executable: /usr/bin/systemmonitor global_pid: 32725 kernel: 4.2.3-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QXcbWindow::handleClientMessageEvent at qxcbwindow.cpp:1940 #1 QXcbConnection::handleXcbEvent at qxcbconnection.cpp:1043 #2 QXcbConnection::processXcbEvents at qxcbconnection.cpp:1487 #3 QObject::event at kernel/qobject.cpp:1246 #4 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3717 #5 QApplication::notify at kernel/qapplication.cpp:3500 #6 QCoreApplication::notifyInternal at kernel/qcoreapplication.cpp:965 #7 sendEvent at kernel/qcoreapplication.h:224 #8 QCoreApplicationPrivate::sendPostedEvents at kernel/qcoreapplication.cpp:1593 #9 QCoreApplication::sendPostedEvents at kernel/qcoreapplication.cpp:1451
Created attachment 1087786 [details] File: backtrace
Created attachment 1087787 [details] File: cgroup
Created attachment 1087788 [details] File: core_backtrace
Created attachment 1087789 [details] File: dso_list
Created attachment 1087790 [details] File: environ
Created attachment 1087791 [details] File: limits
Created attachment 1087792 [details] File: maps
Created attachment 1087793 [details] File: mountinfo
Created attachment 1087794 [details] File: namespaces
Created attachment 1087795 [details] File: open_fds
Created attachment 1087796 [details] File: proc_pid_status
Created attachment 1087797 [details] File: var_log_messages
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.