STEPS TO REPRODUCE 1. open File Search KCM 2. enable the file indexing 3. click on "Apply" button 4. click on "Pause indexer" button while the file indexing is in progress OBSERVED RESULT the indexer is not paused. If I click on the "Pause indexer" button after the file indexing reaches 100%, the indexer is paused as expected. EXPECTED RESULT the indexer should always be immediately paused after click on "Pause indexer" button SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 Graphics Platform: Wayland
Do you know if this also happened in Plasma 5, Patrick?
Can reproduce on Plasma 5.27.7 too. Operating System: Arch Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Graphics Platform: Wayland
I had a feeling, thanks.
*** Bug 443693 has been marked as a duplicate of this bug. ***
Can confirm on Tumbleweed with 6.2.5 and Frameworks 6.10. The status bar says > Checking for non indexed files, 100% complete There are certainly many files to be indexed as I just have added a new internal drive mounted under /media and changed the indexing to include file contents. Before all of this I have run `balooctl purge`. baloo_file and baloorunner are running in the background. There's no log in journalctl when pressing the button.
I think it kind of works: After leaving the system and returning two hours later, it indeed said "Indexing paused"! It just took a while to change the state! Pressing "Resume Indexing" and "Pause Indexing" _now_ works immediately.
It also seems not "pause-able" if its in the state "Checking for old index entries, X% complete". While it was indexing now and the status bar showed the currently indexed files, I've added a new not-to-be-index folder: Now the "Pause Indexing" button got stuck again and does nothing.
Instead of using the UI in the KCM, I've tried `balooctl suspend` in the cmd line and while the command output was > File Indexer suspended respectively with `balooctl disable` > Disabling and stopping the File Indexer however, baloo_file_extractor keeps running in the background utilizing 30% CPU and slowing down the system, making it significantly lag. After the two commands above `balooctl monitor` says > Press ctrl+c to stop monitoring > File indexer is running > Idle (like 30 seconds later at this point) but the process keeps using up to 40% CPU and 11% (3 GB) res ram, though I'm not sure what it's actually doing now, as I don't hear the HDDs rattling anymore. I had to re-open the FileSearch kcm to get an updated state. It reports now that file indexing has been disabled, but it took a few minutes from suspending / disabling until it actually stopped.
Have you checked if the kde-baloo.service is running? > systemctl --user status kde-baloo I've noticed that the issue seems to be gone for me, since I've managed to control baloo by systemd.
Cannot reproduce anymore. Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.4.80 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.1 Graphics Platform: Wayland