On Friday, February 24, 2017 12:28:04 PM EST Rex Dieter wrote: > FYI, sent of kf5-5.31.0 and plasma-5.8.6 to -testing (both > kde-testing and updates-testing) repos yesterday , Well, I did have a small problem on my desktop machine (no problems on my laptop). My log filled up with these messages every second[*]. I had walked away for several hours and came back to huge memory consumption (korgac was up to 11+ GB and swap was over half filled on a 16 GB machine). I finally noticed that several akonadi agents were duplicated in the akonadiconsole. I removed them and rebooted and all is now well. Actually, I disabled kde-testing first and did a dnf distro-sync first to downgrade, but the problem was still there. That's when I found the duplicate agents, removed them, and updated again. I have no idea how this happened, but it was immediately after updating using kde-testing and rebooting. I didn't collect any real information -- just removed the duplicated agents. Shrug. ________________________ [*] Feb 27 16:26:01 vfr akonadi_kalarm_resource[3340]: org.kde.pim.kalarmresource: KCalCore::Event has no alarms: "b485bdb9-1e23-4506-9325-a88939dbc2a9" Feb 27 16:26:01 vfr akonadi_kalarm_resource[3340]: org.kde.pim.kalarmresource: KCalCore::Event has no alarms: "236edc49-9dbd-4f8f-9b82-03e048a678f1" Feb 27 16:26:01 vfr akonadi_kalarm_resource[3340]: org.kde.pim.kalarmresource: KCalCore::Event has no alarms: "2c18e3e9-3004-4a98-88df-37f697288c8f" Feb 27 16:26:01 vfr akonadi_kalarm_resource[3340]: org.kde.pim.kalarmresource: KCalCore::Event has no alarms: "libkcal-668562259.70" Feb 27 16:26:01 vfr akonadi_kalarm_resource[3340]: org.kde.pim.kalarmresource: KCalCore::Event has no alarms: "57bbe403-fa4b-46e5-9304-693deca257ba" Feb 27 16:26:01 vfr akonadi_kalarm_resource[3340]: org.kde.pim.kalarmresource: KCalCore::Event has no alarms: "704067cf-5ea4-46f4-b805-8fd59ae10952" -- Garry T. Williams _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
