https://bugs.kde.org/show_bug.cgi?id=420939
--- Comment #35 from tagwer...@innerjoin.org ---
(In reply to Scott from comment #32)
> So here is the problem, the above information is not entirely correct. The
> settings in baloofilerc do not control whether full file indexing occurs.
I think baloofilerc is the single source of config information, the GUI updates
it and prompts baloo to reread it. I think the GUI does do some other stuff
like the equivalent of a "balooctl check" when you include other folders.
Beyond that, I'm afraid I don't know.
> ... Once that is enabled (ticked) the four files we spoke about
> yesterday are now more fully indexed and display valid data in the Duration
> column of Dolphin ...
That sounds good news (some good news at least :-)
> Is it possible to increase the values shown in item 3 above?
If I google for the error message, I get hits for ffmpeg.
It seems sensible for baloo to depend on ffmpeg and I also see I've a
"kfilemetadata_ffmpegextractor.so" on my system. It looks as if you are ahead
of me though with video formats, cf Bug 399650. My guess is that you are
running into a similar sort of issue you had before.
I'd say check your files with ffmpeg/ffprobe to see if ffmpeg can read the
metadata. You can install ffmpeg on Kubuntu with "sudo apt install ffmpeg" and
try out ffprobe:
https://trac.ffmpeg.org/wiki/FFprobeTips
Maybe this helps. You've the advantage that you know the metadata _can_ be read
with MediaInfo, ffprobe could help pin down where the issue is.
> As you are aware I have 2 terminal windows open during this process. When I
> unable balooctl the monitor window reports, Indexing: /directory.file.m2ts
> OK, for all 4 files. In the other terminal window error/warning messages are
> printed (the purple prefixed messages in my previous attachments) as shown
> in the numbered items above.
Yes. I've noticed that after you've restarted baloo from the command line (a
balooctl enable or balooctl purge) you get the error messages scrolling up on
your screen.
These are from the "background processes" baloo_file and baloo_file_extractor
and would normally go to a log.
Were you getting these messages when you were running "balooctl purge"? In this
case you wouldn't get the command prompt repeated after the message.
--
You are receiving this mail because:
You are watching all bug changes.
