The only reasons for kamd to crash are inability to create WAL sqlite database (it will return an assert with a detailed message), and to crash on *exit* due to the QSql bug related to driver deinit.
Other than that, I haven't had any crashes reported for quite a long time now. Are there any backtraces or more info related to this issue? One of the things that we could try is for kactivities to return 'Unknown' as the state until it figures out whether there is kamd running or not. And then set it as Running or NotRunning. But Plasma will still have to decide what to do in both cases. Cheers, Ivan p.s. I've approved D2275 - the old script was indeed very wrong. _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
