| Summary: | Change of font causes 100% CPU Utilization in plasmashell | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | paulcee33 |
| Component: | generic-performance | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | heri+kde, nate, noahadvs, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.11.4 | ||
| Target Milestone: | 1.0 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
paulcee33
2017-12-24 16:43:48 UTC
Can you tell us which exactly font you used? I can't reproduce here. Also, this only happens after reboot, not when you apply the font? I've tried two from the Avenir font family (LT 45 book, and LT 55 Roman), both of which are Truetype fonts installed through the "Configure Desktop" (systemsettings5) menu, as system fonts. And it seems to follow a restart of X, not just a reboot. After setting font things *APPEAR* to work fine, until restart of X and/or reboot (which of course, restarts X). After that, 100% CPU from plasmashell. Reset font back to Noto/other pre-installed font, reset, and normal CPU. Is this still a problem with Plasma 5.27? I've never experienced this issue with user installed TrueType fronts in Plasma 5.26 and 5.27, so the issue may be gone. 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 bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |