Version-Release number of selected component: kf5-kactivities-5.14.0-1.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 3 cmdline: /usr/bin/kactivitymanagerd start-daemon executable: /usr/bin/kactivitymanagerd global_pid: 1417 kernel: 4.2.1-300.fc23.i686 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 ?? #1 QMetaObject::invokeMethod at kernel/qmetaobject.cpp:1464 #2 Plugin::callOnRet<QString, (Qt::ConnectionType)1> at ../../../../../src/service/Plugin.h:107 #3 StatsPlugin::currentActivity at ../../../../../src/service/plugins/sqlite/StatsPlugin.cpp:378 #4 ResourceScoreMaintainer::Private::run at ../../../../../src/service/plugins/sqlite/ResourceScoreMaintainer.cpp:73 #5 QThreadPrivate::start at thread/qthread_unix.cpp:331
Created attachment 1077749 [details] File: backtrace
Created attachment 1077750 [details] File: cgroup
Created attachment 1077751 [details] File: core_backtrace
Created attachment 1077752 [details] File: dso_list
Created attachment 1077753 [details] File: environ
Created attachment 1077754 [details] File: exploitable
Created attachment 1077755 [details] File: limits
Created attachment 1077756 [details] File: maps
Created attachment 1077757 [details] File: mountinfo
Created attachment 1077758 [details] File: namespaces
Created attachment 1077759 [details] File: open_fds
Created attachment 1077760 [details] File: proc_pid_status
This also happens on x86_64. The error pops up when I turn on my laptop, immediately upon log in. It seems to appear somewhat consistently, ever since I installed the f23 beta a month ago. I don't think I remember seeing the error EVERY day, but it appears most days. Ultimately, kactivitymanagerd ends up running -- or at least I see /usr/bin/kactivitymanagerd start-daemon ...when I do a "ps" after the error pops up.
Updating QT5 packages from updates-testing worked for me: sudo dnf update qt5* --enablerepo=updates-testing
Unfortunately it does not fix for me.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
It has been resolved, can you retry ?
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.