Hide Forgot
Version-Release number of selected component: kf5-kactivities-5.17.0-1.fc24 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QtWaylandClient::QWaylandDisplay::exitWithError executable: /usr/bin/kactivitymanagerd global_pid: 3712 kernel: 4.4.0-0.rc6.git1.1.fc24.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #11 QtWaylandClient::QWaylandDisplay::exitWithError at qwaylanddisplay.cpp:210 #12 QtWaylandClient::QWaylandDisplay::flushRequests at qwaylanddisplay.cpp:193 #13 QMetaObject::activate at kernel/qobject.cpp:3730 #15 QSocketNotifier::activated at .moc/moc_qsocketnotifier.cpp:134 #16 QSocketNotifier::event at kernel/qsocketnotifier.cpp:260 #17 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3712 #18 QApplication::notify at kernel/qapplication.cpp:3493 #19 QCoreApplication::notifyInternal2 at kernel/qcoreapplication.cpp:1013 #20 QCoreApplication::sendEvent at ../../src/corelib/kernel/qcoreapplication.h:227 #21 socketNotifierSourceDispatch at kernel/qeventdispatcher_glib.cpp:100
Created attachment 1110190 [details] File: backtrace
Created attachment 1110191 [details] File: cgroup
Created attachment 1110192 [details] File: core_backtrace
Created attachment 1110193 [details] File: dso_list
Created attachment 1110194 [details] File: environ
Created attachment 1110195 [details] File: exploitable
Created attachment 1110196 [details] File: limits
Created attachment 1110197 [details] File: maps
Created attachment 1110198 [details] File: mountinfo
Created attachment 1110199 [details] File: namespaces
Created attachment 1110200 [details] File: open_fds
Created attachment 1110201 [details] File: proc_pid_status
Created attachment 1110202 [details] File: var_log_messages
Similar problem has been detected: This happened in a wayland session reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QtWaylandClient::QWaylandDisplay::exitWithError executable: /usr/bin/kactivitymanagerd global_pid: 1962 kernel: 4.5.0-0.rc5.git0.1.fc24.x86_64 package: kf5-kactivities-5.19.0-1.fc24 reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.