https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #11 from UberPanda <a...@heriban.net> ---
I think I found a way to brute force a fix :
In systemctl, the error boils down to :
KActivities: Database can not be opened in WAL mode. Check the SQLite version
(required >3.7.0). An
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #9 from UberPanda <a...@heriban.net> ---
(In reply to David Edmundson from comment #8)
> What Qt version?
5.10.1-1 in my case
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #6 from UberPanda <a...@heriban.net> ---
(In reply to Zakhar from comment #3)
> (In reply to UberPanda from comment #1)
> > pkill -f kactivitymanagerd stopped the coredumps and high cpu usage.
>
> Running it slig
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #4 from UberPanda <a...@heriban.net> ---
Created attachment 112208
--> https://bugs.kde.org/attachment.cgi?id=112208=edit
First screenshot of blinking activity settings
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #5 from UberPanda <a...@heriban.net> ---
Created attachment 112209
--> https://bugs.kde.org/attachment.cgi?id=112209=edit
Second screenshot of blinking activity settings
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #2 from UberPanda <a...@heriban.net> ---
(In reply to UberPanda from comment #1)
> Note sure if the exact same issue :
> I was also having ridiculous cpu usage with plasma (30% on all cores). Upon
> closer inspection,
