Since updating to Qt 5.6.0-rc, I get a reproducible crash in kded leading to misbehaviour of the desktop. See the attached log. I've tried with two upstream Qt patches: https://codereview.qt-project.org/gitweb?p=qt%2Fqtbase.git;a=commit;h=6729ec8d39a7f17308b7178bed23084e52bc0231 and https://codereview.qt-project.org/gitweb?p=qt%2Fqtbase.git;a=commit;h=f7106a1efa98156c7f1276665c673000e6131c05 But afaics, it did not improve things. Reproducible: Always
Created attachment 97757 [details] Output of coredumpctl
Looks like powerdevil => polkit-qt is reading an invalid dbus reply. Compare bug #246638 or bug #195087 Looking into the polkit-qt source a) the error actually seems to be checked b) to occur because it queries consolekt?? Disabling powerdevil in "kcmshell5 kded" will likely prevent the particular abort. The problem is likely that the check is *not* whether the reply is QDBusMessage::ReplyMessage but whether it's not QDBusMessage::ErrorMessage (and Qt might have introduced more precise typings?) but *my* problem is that polkit-qt has no component. @Bernd, can you try reverting the logics in https://quickgit.kde.org/?p=polkit-qt-1.git Howeve, this might also have been fixed by other recent commits, so ensure to rebuild polkit-qt-1 against 5.6 anyway.
Thanks for that hint. building polkit-qt scm did actually fix kded and other things improved as well (i.e. kmix and akregator weren't showing up in the systray). Maybe it would be a good idea to make a new release of polkit-qt targeting qt 5.6.
Since this issue does not show up in newer versions, I now close it as "WORKSFORME". Please reopen or submit another report if you think otherwise.