https://bugs.kde.org/show_bug.cgi?id=404121
Bug ID: 404121 Summary: balooctl suspend is not working? Product: frameworks-baloo Version: 5.52.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: pio...@netscape.net Target Milestone: --- SUMMARY Suspend command only works if done before the indexing started! STEPS TO REPRODUCE 1. download several discs of text/pdf and enable indexing its contents for weeks ;) 2. as balooctl monitor shows that text gets indexed tell it to suspend. (3. then restart computer and do the same before anything gets indexed.) OBSERVED RESULT suspend of a file inside of an archive (like inside an iso file) makes baloo finish indexing that file (along with the ~15GB memory allocation it requires for writing to my 36GB database), and right after that the status is switched to resume again, as if I had not suspended anything at all. I can see that suddenly memory-consumption drops to normal and balooctl monitor shows it is now indexing a bunch of new files! the only solution I found is to quickly suspend at system-start -- if I'm too late I need to pkill baloo_file_extractor and baloo_file and likely lose the ability to resume, maybe even add corrupted data that way. EXPECTED RESULT when user presses Suspend in KInfocentre, the state of baloo_file_extractor should be saved to disc and all of its activity, including baloo_file should be stopped immediately to be resumed upon Resume! if the database does not allow that fine-grained suspend, then at least suspend once baloo is in charge again! SOFTWARE/OS VERSIONS Linux/KDE Plasma: gentoo profile: default/linux/amd64/17.0/desktop/plasma/systemd (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION I had this problem for as long as I remember using kde-plasma, i.e. over 2 years or so, started to be noticable after about 1 month of indexing. now status says Indexed 785951 / 806876 files and I'm looking forward to get 100% eventually. but with 6GB physical memory I cannot allow baloo to do its indexing while I make use of the computer since the remaining 9GB of swap-partition-memory is preventing all disc-IO -- even if baloo's indexing would use less cpu-ressources, the unlimited memory-usage is a major slow-down... it's a major bug if suspending the process is not possible, if it just keeps restarting no matter what! only after pkill it really stops, so it must be a bug in baloo and not in systemd or whatever... -- You are receiving this mail because: You are watching all bug changes.