https://bugs.kde.org/show_bug.cgi?id=364042
Bug ID: 364042
Summary: balooctl status always reports "Baloo Index could not
be opened"
Product: frameworks-baloo
Version: 5.22.0
Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: balooctl
Assignee: m...@vhanda.in
Reporter: skierp...@gmail.com
CC: pinak.ah...@gmail.com
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.
--
You are receiving this mail because:
You are watching all bug changes.
