https://bugs.kde.org/show_bug.cgi?id=439909
Piotr Mierzwinski <piotr.mierzwin...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |NOT A BUG
--- Comment #8 from Piotr Mierzwinski <piotr.mierzwin...@gmail.com> ---
(In reply to tagwerk19 from comment #7)
> (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.
Yes I did it couple time, but without effect.
> > ... 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.
OK. So maybe files without permission to read?
If not then I don't know what is the reason this failed.
> 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.
OK. I started all commands you suggested. Below please find result:
$ balooctl monitor
Waiting for file indexer to start
Press Ctrl+C to stop monitoring
File indexer is running
Starting
Checking for stale index entries
Waiting for file indexer to start
Press Ctrl+C to stop monitoring
> > $ 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?
Sorry? What do you mean? I update my system every day, and even couple times. I
have Linux Arch based distribution (Antergos, migrated to Arch repositories).
$ pacman -Q baloo
baloo 5.84.0-1
> 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
OK. I did it and another to start indexing, so:
$ balooctl enable
> and have a cup of coffee... (you will be able to see the files listed as
> they are indexed listed in the monitor)
After some time it was finished and in GUI I found:
"Status Idle, 100% complete [Pause Indexer]"
BTW. Is this button saying "pause" is a bug? Because indexing finished.
And of course this time I was able to find my file in Dolphin :).
> Did I cover everything?
Yes. I think you did.
Big thanks for help. Seems purge was the solution for this issue. But still
don't know why indexing stuck and what files cased this.
--
You are receiving this mail because:
You are watching all bug changes.
