https://bugs.kde.org/show_bug.cgi?id=420939
--- Comment #20 from tagwer...@innerjoin.org ---
(In reply to Scott from comment #19)
> If I can provide further information please advise.
The issues are:
You don't get as many files indexed as you expect.
A "balooctl purge" hangs
where the files are video format (with subtitles) plus there's a separate issue
with durations not appearing as index metadata
Let's simplify and take a few steps back; apologies if this seems rather
basic...
It's worth temporarily setting up the indexing just for a test folder under
your "home " and copying "test" files across into it one at a time. If you are
running "balooctl monitor" you should see baloo notice a file arrive and index
it.
To be sure that you are starting "clean" you can close down the indexer,
balooctl disable
and check that it has really gone (try "pgrep -l baloo_file" and kill the
process if necessary). Then manually delete the database:
rm ~/.local/share/baloo/index
Run
balooctl monitor
in a separate window and
balooctl enable
Repeat the "enable" if you don't see the monitor say "File indexer is running".
Sometimes it needs to be told twice.
When you copy a file you should see it listed in the monitor and be able to see
the information extracted with
balooshow -x ...testfile...
I would expect that this shows you the embedded metadata (some? all?). You
should be able to see the underlying metadata that dolphin displays as aspect
ratio, frame rate, duration etc.
If you don't get any results, you can prompt baloo to index the file:
balooctl index ...testfile...
which may give you extra information/error messages.
If you are not seeing the metadata for particular file formats (or for some
files and not others), then I think split off this issue and submit separate a
bug. You are likely to need a someone with deep and detailed knowledge of video
formats who can take it on from there :-/
It's also worth noting if the "balooctl index" takes a long time to process.
There's a bug fixed in 5.83.0 where determining the mimetype meant that the
whole file was read. If you are dealing with large video files, that could be a
considerable load. See Bug 398908.
Similarly, check whether the indexer is crashing when you copy the test file or
do a manual index (see if coredumpctl gives you anything). A repeatable crash
would mean installing debug symbols and submitting that as a separate bug.
Any metadata that "balooshow -x" shows you should be findable with baloosearch.
If "things work" with your test files in your home directory and don't work on
your mounted discs, then that another angle to follow up.
Hope this is followable...
--
You are receiving this mail because:
You are watching all bug changes.
