activitymanagerd 5.6.3 crashes with segmentation fault Reproducible: Sometimes Steps to Reproduce: 1. Login, wait and see if core dump is generated ;-)
Created attachment 98815 [details] Backtrace #1
Created attachment 98816 [details] Backtrace #2
Created attachment 98817 [details] Backtrace #3 (fresh and empty user profile) This backtrace was taken from a core dump that was generated during the first login of a freshly created user with an empty home directory.
Created attachment 98818 [details] Backtrace #4
Something requests the activity manager to exit, and then it triggers a QSQL bug that leads to this crash. Do you have anything strange in your session, does the session terminate when this happens? This crash is benign as far as the activity manager is concerned since it happens when it exists, and it keeps its data safe even in the case of crashes. Now, I'm not saying that this should be ignored, we should try to see what exactly is going on :) Do you have any XCB errors in your .xsession-errors file?
We have a few watchers here, is kamd crashing for you as well in the middle of the session, are you all using the same distro?
Anybody working on this? I still see the crashes. I will upload a new backtrace of a fresh core dump from this day. No, no errors in .xsession-errors, fresh user home directory, no legacy stuff from KDE 4 or anything like this. Just a crashing activitymanager
Created attachment 102620 [details] Backtrace #5 kde-plasma/kactivitymanagerd-5.7.5
If QXcbConnection::processXcbEvents() causes an 'exit', then this needs to be fixed in Qt. Please report this issue directly to Qt developers via https://bugreports.qt.io/
I checked the source for QXcbConnection::processXcbEvents(), and it only exits, when the X11 connection broke. In other words, your X server caused the connection to terminate, not that I have any idea why it does that.
Given the new insight that the X server causes the exit, shall I still report upstream at https://bugreports.qt.io/ or report at http://bugs.freedesktop.org and file a bug against the X server?
Sadly, it is not easy to say whose fault it is - Xorg's, XCB library or Qt and I have no idea how you might debug the issue. The kactivitymanagerd crash should go away when Qt people patch an unrelated bug - it will just exit as it should, but the issue that it exits at all because of lost X connection will remain.