Summary: | Plasma utilizing 100% CPU (1 core) after upgrade to 17.10 | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Petr Nehez <petr.nehez> |
Component: | general | Assignee: | David Edmundson <kde> |
Status: | CLOSED INTENTIONAL | ||
Severity: | major | CC: | plasma-bugs |
Priority: | NOR | ||
Version: | 5.10.5 | ||
Target Milestone: | 1.0 | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Petr Nehez
2017-10-31 09:17:04 UTC
That line of output has nothing to do wtih a freeze. (also it's clearly not come from plasma) If you have a freeze please run "sudo gdb --pid `pidof plasmashell`" then type "bt" and copy and paste that output. We can do nothing with this, sorry. OK, I have written it in a bad way. Plasmashell was utilizing 1 core on 100% and doing a lot of IO writes. That line was the only thing I have found out by executing * "lsof | grep plasmashe" * "sudo strace -p XXXX -v" and checking what was being written. And that line was the only thing that was being written. When I deleted the folder "/home/petr/.local/share/plasma/plasmoids/com.github.zren.batterytime/" and restarted system, plasmashell started correctly. I deleted the folder after logging in and pressing of Ctrl+Alt+F1 and logging in again in terminal. Now I have no idea how you want from me to debug it after fixing of the issue. My computers was not usable after upgrade until I deleted that folder. >When I deleted the folder "/home/petr/.local/share/plasma/plasmoids/com.github.zren.batterytime/" and restarted system, plasmashell started correctly.
Sounds like they're stuck in a layout loop.
But not Plasma code, so I can't do anything.
OK, I understand it is not specifically Plasma's code, but would it be possible to disable all plasmoids while doing an upgrade? This would avoid such problems. For less experienced users this would mean full reinstall only... |