https://bugs.kde.org/show_bug.cgi?id=474973

--- Comment #12 from Marco <phoenix_8...@hotmail.com> ---
(In reply to tagwerk19 from comment #9)
> (In reply to Marco from comment #7)
> > Simply, when I ask dophin to search over "my files", it is able to find
> > them. If ask it to search "from here" it does not, precisely the same
> > behaviour baloosearch has from the command line.
> Can you run a:
>     baloosearch -i xxx
> where xxx is a file in your Downloads folder. If I understand it,
> baloosearch works here...
> 
> Repeat with:
>     baloosearch -d ~/Downloads -i xxx
> where baloosearch fails...
> 
> then try a:
>     balooshow -x ~/Downloads/xxx
> and copy the first lines of output into this bug...
> 
> Second question, what happens if you create a new file in your Downloads
> folder, something really minimal like:
>     echo "Hello Penguin" > ~/Downloads/testfile.txt
> can baloosearch find a new/simple file?

Here is the result of running the balooshow -x command after searching in both
ways (which, as you also expected, worked without the -d argument, but did not
with it); I searched for the file "clickhouse" inside the Downloads directory
(which is translated to Scaricati in italian).

2ad424f528e2274 1385046644 44909135 /home/marco/Scaricati/clickhouse
        Mtime: 1697027838 2023-10-11T14:37:18
        Ctime: 1697027838 2023-10-11T14:37:18

Internal informations
Filename terms: Fclickhouse 
XAttr terms: 
Simple text terms: 
Property terms: Mapplication Moctet Mstream 

(It seems baloo has been translated to multiple languages, and I was getting
output in Italian, so I tried to translate to english the output of balooshow).

I also tried creating a simple file "testfile.txt" in the downloads directory,
but the same issue occurs. If it helps, I have disapled file content indexing
to keep the index small and to not overload my system, so the content of the
file should not matter.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to