Version-Release number of selected component: kactivitymanagerd-5.5.0-1.fc24 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1628 kernel: 4.5.0-0.rc7.git0.2.fc24.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #11 QXcbConnection::processXcbEvents at qxcbconnection.cpp:1665 #12 QObject::event at kernel/qobject.cpp:1256 #13 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3714 #14 QApplication::notify at kernel/qapplication.cpp:3495 #15 QCoreApplication::notifyInternal2 at kernel/qcoreapplication.cpp:1015 #16 QCoreApplication::sendEvent at kernel/qcoreapplication.h:227 #17 QCoreApplicationPrivate::sendPostedEvents at kernel/qcoreapplication.cpp:1650 #18 QCoreApplication::sendPostedEvents at kernel/qcoreapplication.cpp:1508 #19 postEventSourceDispatch at kernel/qeventdispatcher_glib.cpp:270 #23 g_main_context_iteration at gmain.c:3901
Created attachment 1142490 [details] File: backtrace
Created attachment 1142491 [details] File: cgroup
Created attachment 1142492 [details] File: core_backtrace
Created attachment 1142493 [details] File: dso_list
Created attachment 1142494 [details] File: environ
Created attachment 1142495 [details] File: exploitable
Created attachment 1142496 [details] File: limits
Created attachment 1142497 [details] File: maps
Created attachment 1142498 [details] File: mountinfo
Created attachment 1142499 [details] File: namespaces
Created attachment 1142500 [details] File: open_fds
Created attachment 1142501 [details] File: proc_pid_status
Created attachment 1142502 [details] File: var_log_messages
Similar problem has been detected: Encountered this after the first boot (and login) on a freshly-installed system. reporter: libreport-2.7.0 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1327 kernel: 4.5.1-300.fc24.x86_64 package: kactivitymanagerd-5.6.2-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV reproducible: Not sure how to reproduce the problem runlevel: unknown type: CCpp uid: 0
Similar problem has been detected: Did a fresh installation of Fedora 24 KDE Beta. Almost every time I reboot, kactivitymanagerd crashes and this crash report is produced and available through ABRT. There have been eight of these crashes in about as many reboots at the time of reporting this. reporter: libreport-2.7.0 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1411 kernel: 4.5.4-300.fc24.x86_64 package: kactivitymanagerd-5.6.4-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV reproducible: The problem occurs regularly runlevel: N 5 type: CCpp uid: 1000
May be related to bug #1337526.
Similar problem has been detected: Fully up to date FC24 as of 2016/07/06. Logged in with dual monitors. Only the left one got set up. Background and KDE panel etc missign from right-hand monitor. reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1233 kernel: 4.6.3-300.fc24.x86_64 package: kactivitymanagerd-5.6.5-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV reproducible: Not sure how to reproduce the problem runlevel: N 5 type: CCpp uid: 1001
Similar problem has been detected: User was afk for +/- 10 minutes reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1401 kernel: 4.6.3-300.fc24.x86_64 package: kactivitymanagerd-5.6.5-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 2011
Similar problem has been detected: Just logged in with autologin enabled. reporter: libreport-2.7.1 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1262 kernel: 4.6.3-300.fc24.x86_64 package: kactivitymanagerd-5.6.5-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV reproducible: Not sure how to reproduce the problem runlevel: unknown type: CCpp uid: 1001
Similar problem has been detected: Tried to add a new panel to second screen. Everything froze. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 2624 kernel: 4.6.4-301.fc24.x86_64 package: kactivitymanagerd-5.7.2-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
Similar problem has been detected: Created a new KDE panel on screen 2 which did not have one. reporter: libreport-2.7.2 backtrace_rating: 4 cmdline: /usr/bin/kactivitymanagerd start-daemon crash_function: QXcbConnection::processXcbEvents executable: /usr/bin/kactivitymanagerd global_pid: 1442 kernel: 4.8.11-200.fc24.x86_64 package: kactivitymanagerd-5.8.4-1.fc24 pkg_fingerprint: 73BD E983 81B4 6521 pkg_vendor: Fedora Project reason: kactivitymanagerd killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
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.