| Summary: | Application launcher + all panels (All plasmashell components) freeze upon typing characters into the launcher | ||
|---|---|---|---|
| Product: | [Applications] marble | Reporter: | gregorystarr00 |
| Component: | general | Assignee: | marble-bugs |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | lemuelsimon32, mikel5764, nate, noahadvs, qydwhotmail |
| Priority: | NOR | ||
| Version First Reported In: | 22.11.90 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/education/marble/commit/10131a6a69347285dcbe42086561df96475fc437 | Version Fixed In: | |
| Sentry Crash Report: | |||
|
Description
gregorystarr00
2022-07-25 01:48:12 UTC
Hmm...so far, I can't reproduce the issue. This requires further investigation. There can be many reasons why the search function would behave like that. It could be hardware (slow & old HDD) or software (rouge KRunner plugin, Baloo(???)). Does searching in KRunner behave the same (ALT+F2)? If so, try disabling the file search plugins. Also, use a system-monitor like HTop or Ksysguard when trying to search again, to get an idea as to which application is abusing CPU or I/O. 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! (In reply to Lemuel Simon from comment #1) > Hmm...so far, I can't reproduce the issue. This requires further > investigation. > > There can be many reasons why the search function would behave like that. It > could be hardware (slow & old HDD) or software (rouge KRunner plugin, > Baloo(???)). Does searching in KRunner behave the same (ALT+F2)? If so, try > disabling the file search plugins. Also, use a system-monitor like HTop or > Ksysguard when trying to search again, to get an idea as to which > application is abusing CPU or I/O. I'm running on a M.2 SSd, so I don't think it's hardware speed. I have Baloo disabled because it was wreaking havoc on my system and using up massive amounts of ram in the past - is that possibly a cause? 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! Re-opening as the user is still active and encounters this bug. (In reply to gregorystarr00 from comment #3) > (In reply to Lemuel Simon from comment #1) > > Hmm...so far, I can't reproduce the issue. This requires further > > investigation. > > > > There can be many reasons why the search function would behave like that. It > > could be hardware (slow & old HDD) or software (rouge KRunner plugin, > > Baloo(???)). Does searching in KRunner behave the same (ALT+F2)? If so, try > > disabling the file search plugins. Also, use a system-monitor like HTop or > > Ksysguard when trying to search again, to get an idea as to which > > application is abusing CPU or I/O. > > I'm running on a M.2 SSd, so I don't think it's hardware speed. I have Baloo > disabled because it was wreaking havoc on my system and using up massive > amounts of ram in the past - is that possibly a cause? Sorry for the late response. Disabling Baloo should render KRunner's file search useless. There has to be another cause. What CPU are using? Also, try disabling KRunner plugins and experiment. (In reply to Lemuel Simon from comment #7) > (In reply to gregorystarr00 from comment #3) > > (In reply to Lemuel Simon from comment #1) > > > Hmm...so far, I can't reproduce the issue. This requires further > > > investigation. > > > > > > There can be many reasons why the search function would behave like that. It > > > could be hardware (slow & old HDD) or software (rouge KRunner plugin, > > > Baloo(???)). Does searching in KRunner behave the same (ALT+F2)? If so, try > > > disabling the file search plugins. Also, use a system-monitor like HTop or > > > Ksysguard when trying to search again, to get an idea as to which > > > application is abusing CPU or I/O. > > > > I'm running on a M.2 SSd, so I don't think it's hardware speed. I have Baloo > > disabled because it was wreaking havoc on my system and using up massive > > amounts of ram in the past - is that possibly a cause? > > Sorry for the late response. Disabling Baloo should render KRunner's file > search useless. There has to be another cause. What CPU are using? Also, try > disabling KRunner plugins and experiment. I have a 8 core Ryzen 7 2700x with 16 gigs of RAM. My laptop is running an i5 8350u. Since then, the problem has stopped on my laptop but is still happening every single time on my desktop - I've taken to launching apps via terminal. Could it be my Nvidia GPU (though that wouldn't seem to make sense.) I've tried reactivating baloo and while it no longer wreaks havoc the problem persists. The problem also continues despite removing all KRunner plugins. What sort of system logs would be helpful? I am still observing this even with the latest Plasma updates. > Could it be my Nvidia GPU
This is unfortunately a possibility.
Are you using Marble runner? Check it in enabled plugins. Git commit 10131a6a69347285dcbe42086561df96475fc437 by Fushan Wen. Committed on 27/11/2022 at 05:42. Pushed by fusionfuture into branch 'master'. plasmarunner: do not install translator in runner QCoreApplication::installTranslator() will cause all QML bindings to be refreshed, which will cause a noticable delay when searching in Kickoff/KRunner. Remove the custom translator and use ki18n instead. M +0 -4 src/plasmarunner/CMakeLists.txt https://invent.kde.org/education/marble/commit/10131a6a69347285dcbe42086561df96475fc437 |