I also just got it by firing up firefox. I'd like to file a BR, but no idea which component is at fault here.
On Mon, Jan 11, 2021 at 2:23 PM Neal Becker ndbecker2@gmail.com wrote:
Oh this is interesting. I can reproduce 100% by starting the app "signal". But closing signal doesn't stop krunner/plasmashell, I have to then kill krunner. signal is installed from flatpak.
On Mon, Jan 11, 2021 at 2:08 PM Neal Becker ndbecker2@gmail.com wrote:
A couple more points:
- Seems to have just started with latest updates
- kill krunner seems to fix it
- I think after killing krunner I see this message:
Jan 11 13:57:02 nbecker2 systemd[1584]: dbus-:1.2-org.kde.krunner@0.service: Succeeded. Jan 11 13:57:02 nbecker2 systemd[1584]: dbus-:1.2-org.kde.krunner@0.service: Consumed 2min 323ms CPU time.
On Mon, Jan 11, 2021 at 2:01 PM Robert-André Mauchin zebob.m@gmail.com wrote:
On 1/11/21 7:56 PM, Neal Becker wrote:
After restarting from last update, I have a new problem. After login,
a
few minutes later I see krunner/plasmashell using a total of close to 100% cpu (each one bouncing around 50%). I'm sure this never happened before.
I have this issue after logging out and relogin, plasmashell and krunner each occupying a full core. _______________________________________________ kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@lists.fedoraproject.org
-- *Those who don't understand recursion are doomed to repeat it*
-- *Those who don't understand recursion are doomed to repeat it*