https://bugs.kde.org/show_bug.cgi?id=393438
Bug Janitor Service changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINF
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #13 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=393438
Justin Zobel changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #11 from UberPanda ---
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). And whether your filesystem suppo
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #10 from Zakhar ---
Qt 5.9.5
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #9 from UberPanda ---
(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 #8 from David Edmundson ---
What Qt version?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #7 from Zakhar ---
I should add this problem existed in the last stable release pre 5.45.0 however
cpu usage was not as high as it is with this revision. I should mention the new
revision plugged some serious memory leaks but unfortunately d
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #6 from UberPanda ---
(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 slighty reduces cpu usage and then it goes back to
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #4 from UberPanda ---
Created attachment 112208
--> https://bugs.kde.org/attachment.cgi?id=112208&action=edit
First screenshot of blinking activity settings
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #5 from UberPanda ---
Created attachment 112209
--> https://bugs.kde.org/attachment.cgi?id=112209&action=edit
Second screenshot of blinking activity settings
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #3 from Zakhar ---
(In reply to UberPanda from comment #1)
> pkill -f kactivitymanagerd stopped the coredumps and high cpu usage.
Running it slighty reduces cpu usage and then it goes back to the normal ~15 -
30% wilst idling because kactiv
https://bugs.kde.org/show_bug.cgi?id=393438
--- Comment #2 from UberPanda ---
(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, I noticed a few coredumps in HTOP.
>
>
https://bugs.kde.org/show_bug.cgi?id=393438
a...@heriban.net changed:
What|Removed |Added
CC||a...@heriban.net
--- Comment #1 from a...@her
14 matches
Mail list logo
