kde-plasma/kactivitymanagerd-5.6.3 crashes with segmentation fault usually after login.
Created attachment 431824 [details] Backtrace of core dump of kactivitymanagerd
Please provide the upstream bug report.
Upstream: https://bugs.kde.org/show_bug.cgi?id=362757
(In reply to Matthias Nagel from comment #3) > Upstream: https://bugs.kde.org/show_bug.cgi?id=362757 Thanks.
5.6.4 was bumped in the meantime. Does it solve your problem?
No, it did not solve the problem. kde-plasma/kactivitymanagerd-5.6.4 keeps crashing with segmentation fault, too.
(In reply to Matthias Nagel from comment #6) > No, it did not solve the problem. kde-plasma/kactivitymanagerd-5.6.4 keeps > crashing with segmentation fault, too. In this case please provide a full build log and paste the emerge --info. No cc's on the bug since about a month, it is likely a local problem.
Created attachment 434898 [details] emerge --info
Created attachment 434900 [details] emerge --verbose --oneshot =kde-plasma/kactivitymanagerd-5.6.4
I have found something interesting in kde forums: https://forum.kde.org/viewtopic.php?f=289&t=127421#p339711 Maybe you can investigate if something helps from this options: - downgrade/upgrade xproto - upgrade xorg-server - nvidia-drivers
According to the aforementioned discussion and the further links inside it seems to be combination of problems with xproto 7.0.28 and the intel driver. Although I do not have an intel graphics I also have had xproto version 7.0.28. I just have downgraded to 7.0.27 and will come back to report if it helped.
I tried xproto 7.0.27, but kactivitymanagerd is still crashing. Next step is to upgrade xorg-server.
I upgraded to x11-base/xorg-server-1.18.3 (from 1.17.4) x11-proto/xproto-7.0.29 (from 7.0.27) x11-base/xorg-drivers-1.18-r1 (from 1.17) x11-drivers/xf86-input-evdev-2.10.2 (from 2.9.2) x11-drivers/xf86-video-nouveau-1.0.12 (from 1.0.11) But kde-plasma/kactivitymanagerd-5.6.4 is still crashing.
Confirm same problem after updating on sunday 29.5 (update every sunday).
I am experiencing the same issue after an update this weekend.
I've run into this issue in the past, but haven't noticed any crashes with 5.7.x (yet).
I recently encountered this error and I solved with applying a patch to qtcore (my current version is 5.6.1). Reference: https://bugs.kde.org/show_bug.cgi?id=348194 https://codereview.qt-project.org/#/c/140750/
Created attachment 452029 [details, diff] qtcore-5.6.1-kactivitymanagerd-segfaults.patch
Confirmed by Qt upstream. @Qt Feel free to provide a revision bump for dev-qt/qtcore-5.6 with attached patch as it seems that Qt 5.7 unmasking takes longer.
Is this in Qt-5.6.2 upstream?
(In reply to Andreas Sturmlechner from comment #20) > Is this in Qt-5.6.2 upstream? It's not part of 5.6.2, but after discussion it did get backported to 5.6 branch (https://code.qt.io/cgit/qt/qtbase.git/commit/?id=ca4d93d85ee446c5e30ec8e7814651e45cbf1218). We should decide ASAP whether we want to backport that to 5.6.2 for stabilisation.
I think we should backport the patch to 5.6.2 and then stabilize it, yes.
Thanks Davide. Fixed in git. https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5ebe88c3c2988c62baaffb71e0249e97fc30ba51
