https://bugs.kde.org/show_bug.cgi?id=428048
--- Comment #6 from Umbertho dellarojadecanariaportedelacruzkarrrrrdinalll <mnmm1j+4hehta00jr...@sharklasers.com> --- So, if a running system updates to a 'bad' version of libksysguard, the effects will not show until the system is rebooted. If a bad version gets replaced with a good one, reboot isn't necessary somehow. I found that commit 23852597c642a5c5303bb994d4d28e20d9c863cb there might be a problem deleting the objects that are created.... I patched this on my end by changing processcore/read_procsmaps_runnable.cpp to -setAutoDelete(false) +setAutoDelete(true) I could also just git revert the entire commit and things are back to normal. I'm having a hard time believing that some will suffer from this and others don't. Reboot if you dare ;) -- You are receiving this mail because: You are watching all bug changes.