I was running Kubuntu 16.04, then set up the Kubuntu Backports PPA to run newer KDE. In both, `balooctl status` always reports "Baloo Index could not be opened". In ~/.local/share/baloo I have a 293 MB index and 8192 index-lock, both modified recently. I ran `strace balooctl status` and found that shortly before printing this error, balooctl attempts mmap(NULL, 5368709120, PROT_READ, MAP_SHARED, 12, 0) = -1 ENOMEM (Cannot allocate memory) where fd 12 is ~/.local/share/baloo/index. I don't have 5,368,709,120 bytes of RAM :-) Reproducible: Always Steps to Reproduce: 1. balooctl status Actual Results: Baloo Index could not be opened Expected Results: Why can't it open ~/.local/share/baloo/index ? "Could not open Baloo Index at <path>" would be a better error message. Baloo is working somewhat; in Dolphin I can find some files in my home directory by content.
I added a test file and Dolphin's Find by Content can find it, but`balooshow ~/Documents/baloo_test1.txt` also fails with kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of Q*Application: no instance (yet) existing. The Baloo index could not be opened. Please run "balooctl status" to see if Baloo is enabled and working. Under strace this balooshow command likewise makes a failed mmap(NULL, 5368709120, PROT_READ, MAP_SHARED, 5, 0) = -1 ENOMEM (Cannot allocate memory) system call just before it prints this error. Should I delete my ~/.local/share/baloo/index ?
(In reply to skierpage from comment #1) > Should I delete my ~/.local/share/baloo/index ? I ran `balooctl stop`, renamed that file, removed index-lock, ran `balooctl start` and I get the same "Baloo Index could not be opened" error.
Hi, how large is the index you have?
(In reply to Christoph Cullmann from comment #3) > Hi, how large is the index you have? It was 668 MB. I moved it aside and rebuilt, indexing fewer files on my Windows partition, and this problem and other Baloo weirdness went away, see bug 379739. So I suspect I had a corrupt index or Baloo was choking on some file. I kept the old index around in case there's something I can diagnose wrong with it.
It's been a few years and Baloo has gotten many, many bugfixes in that time. Is this still happening to you?
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!
I haven't experienced this problem for a few years, so closing it.
I'm having the same issue on EndeavourOS with Plasma 6.1, indexing is not working at all for me
(In reply to hazelnot from comment #8) > I'm having the same issue on EndeavourOS with Plasma 6.1, indexing is not > working at all for me Do you think it is the same issue? The original post is quite specific with a "Cannot allocate memory" message: > I ran `strace balooctl status` and found that shortly before printing this error, balooctl attempts > mmap(NULL, 5368709120, PROT_READ, MAP_SHARED, 12, 0) = -1 ENOMEM (Cannot allocate memory) > where fd 12 is ~/.local/share/baloo/index. I don't have 5,368,709,120 bytes of RAM :-) This is back from 2016, very likely things have changed in the interim and it would be better to open a new bug (with as many details as you can give. There might be worth comparing Bug 489584)