SUMMARY *** Some times, randomly, when I boot the system and login, the plasmashell session is unusable because of lag. Trying to open the main menu or a window in the task manager is impossible. This comes with a very high disk usage of the root disk by plasmashell process, which makes that disk also unusable. The CPU usage of that process is also a bit higher that it should be. I don't know what is plasmashell doing to consume all that disk and CPU, but when I kill plasmashell process, everything returns to normal. That said, if I try to run it again, everything starts to lag again. All the windows, the mouse, the browser... everything works fine but the plasma things (dock, desktop, app menu...). And if I just wait without killing plasmashell, after a couple minutes it randomly fixes everything and the desktop becomes usable... Again, this whole problem only happens "some times", randomly, which makes it harder to detect what's causing it. *** STEPS TO REPRODUCE 1. Boot 2. Login OBSERVED RESULT The whole plasma session is unusable some times EXPECTED RESULT Everything should be as fast as always SOFTWARE/OS VERSIONS I have this bug since like 2 years ago, so it's probably in older versions too. Linux/KDE Plasma: 5.24.5 (available in About System) KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION This is the output of plasmashell and lsof: https://pastebin.pl/view/515b766e Things I've tried: - Removing plasma cache - Removing all applets - Unmounting all disks but the root one
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.