Created attachment 459998 [details] emerge --info kactivitymanagerd Hello. I constantly find core dumps in my home directory created by kactivitymanagerd. I don't use KDE plasma session, I don't start kactivitymanagerd manually, but I do use some of the KDE applications. kactivitymanagerd somehow started for me automatically. I'll gladly provide more info. Please fix.
Created attachment 460002 [details] backtrace Backtrace from core dump. It seems I need to rebuild many huge libraries with debug symbols. But even now it looks much like backtrace from bug 581068. However, I have qt-5.7.1 installed.
Created attachment 460014 [details] backtrace I've rebuilt all the libraries with debug symbols and here's a complete backtrace.
It appears the while the patch discussed in bug #581068 is part of 5.7 branch, it did not make 5.7.1.
Upstream bug says 'Fix Version/s: 5.8.0'. Waiting for Qt-5.8 to land in tree to test.
(In reply to Michael Palimaka (kensington) from comment #3) > It appears the while the patch discussed in bug #581068 is part of 5.7 > branch, it did not make 5.7.1. Feel free to apply the patch to 5.7.1 as well then.
Re-backported to 5.7.1-r1. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7672298dd8d14ffeb2ae56a93ac5d0a421974cde
Sadly 5.7.1-r1 doesn't fix the problem for me. $ emerge -pqv qtcore [ebuild R ] dev-qt/qtcore-5.7.1-r1 USE="icu -debug -systemd {-test}" Do I need to rebuild kactivitymanagerd or smth else?
I haven't seen any more crashes since update to qtcore-5.7.1-r1. I removed all coredumps prior to rebooting my machine after qtcore update from 5.7.1 to 5.7.1-r1. After reboot there was a fresh coredump from kactivitymanagerd, but none since then. I assume that coredump could have been created during shutdown, while kactivitymanagerd still had 5.7.1 loaded in memory. I forgot to check timestamps and quickly removed it. I'll keep an eye for any new coredumps, but it looks like the problem is solved. Thanks!
