[dolphin] [Bug 439909] Searching in current directory doesn't work alt all

[bugzilla_noreply at kde.org]

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

--- Comment #7 from tagwerk19 at innerjoin.org ---
(In reply to Piotr Mierzwinski from comment #5)
> Anyway I went to command line and called following commands:
> $ balooctl enable
> Enabling and starting the File Indexer
> 
> .. and after couple seconds this one:
> $ balooctl status
> Baloo File Indexer is not running
> ...
It's possible you need to enable twice... There are times (Bug 435315) that
saying it once is not enough.

> In attachment please find screenshot of search setting with strange message
> looking like a bug...
Hmm. I've seen mention of that elsewhere. I'm not sure of what import it has...

> ... Seems baloo failed (maybe because of broken links what I
> have in home directory), and stopped indexing before has found my newly
> created file ...
Broken links? as in symbolic links pointing nowhere? I think baloo makes a
deliberate choice not to follow links. It relies on a one-to-one mapping
between the full filename and an internal ID (which is built from the device
number of the disc/partition and the inode). A symbolic link could make that a
many-to-one mapping. 

I'd suggest as a next step, open a couple of windows and run
    balooctl monitor
in one. That should show you what "baloo is doing" in terms of files indexed.
In the second try first the
    balooctl enable
and then a
    balooctl check
The latter prompts baloo to scan through the filesystem looking to see if there
are any files it has missed.

> $ balooctl failed
> The following files could not be indexed:
> 
> 
> 
> 
> 
> 
> 
> 
> 
> $ balooctl status
Ooo... Just to make sure I've not missed anything. You've not been running (and
updating) this system for a long time? There is a bug about a fix to the
database sometime back and the need to reindex now it's fixed (Bug 431664). In
this case you'd need to do a
    balooctl purge
and have a cup of coffee... (you will be able to see the files listed as they
are indexed listed in the monitor)

Did I cover everything?

-- 
You are receiving this mail because:
You are on the CC list for the bug.