| Summary: | Plasma extremely slow just after boot and high disk usage | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | mnrbn <rubenxinternet> |
| Component: | generic-performance | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.24.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | plasmashell process in ksysguard | ||
|
Description
mnrbn
2022-07-06 08:54:09 UTC
Created attachment 150438 [details]
plasmashell process in ksysguard
Comment on attachment 150438 [details]
plasmashell process in ksysguard
name/user/pid/CPU%/Ram/Time/Disk IO Write/Command
Removing "critical" tag if you've had the bug for 2 years and still use Plasma. Neither stderr or lsof show anything abnormal. Best thing will be to capture log from perf/hotspot when it's in the high usage mode. 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! It's still a problem, it shouldn't be closed It won't be useful probably, but here is the perf.data. Tell me what else to do to get a log of the problem. https://pastebin.pl/view/c3ba086d Also, I do think it's a critical bug. I still use plasma, but if some random days I can't use it after 10 minutes from login, and the disk is being used so much for that time that it will wear down my ssd a lot more than what should be necessary, that's critical. I'm very sorry no one was able to look at those logs years ago. :/ That's on us. A lot of things have changed since then. Can I ask you whether the issue is still seen anymore in Plasma 6.4 or later? Thanks a lot, and I'm sorry once more for the poor responsiveness here ๐๐งน โ ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. 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. Closing as RESOLVED WORKSFORME. |