Created attachment 171150 [details] Multimedia details do not appear unless balooctl6 index is ran manually SUMMARY Baloo doesn't automatically index metadata specific to multimedia files by default, such as a music file's Duration or Artist. As a result, when adding tabs in Dolphin's details view mode for audio or video files, they are blank by default, and will only appear after manually reindexing the files using balooctl6 index. STEPS TO REPRODUCE 1. Create or obtain an audio or video file, then go to its directory in Dolphin and view its Properties (right-click > Properties). 2. Note the file's properties, and ensure it has metadata that can be shown in Dolphin's details view mode, like an audio file's Duration. 3. Switch to the details view mode in Dolphin's main window if not already there, then enable the column for the previously noted metadata. Note that it is blank, despite appearing in the file's properties. 4. Manually reindex the file using balooctl6 index, then reload the directory in Dolphin. Note that the metadata now populates in the Details columns correctly. OBSERVED RESULT Multimedia metadata is not indexed automatically, so Dolphin's details view mode doesn't display it unless action is taken manually. EXPECTED RESULT Multimedia metadata should be indexed automatically, so that it displays in Dolphin's details view mode without manual action. SOFTWARE/OS VERSIONS Linux Kernel Version: 6.9.6-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Adding folders[$e] to baloofilerc per https://community.kde.org/Baloo/Configuration did not resolve the issue. balooctl6 check did not help either.
(In reply to malikth32 from comment #0) > ... Baloo doesn't automatically index metadata specific to multimedia files by > default, such as a music file's Duration or Artist... What happens when ... > 1. Create or obtain an audio or video file, then go to its directory in > Dolphin and view its Properties (right-click > Properties). ... and then check to see what Baloo has indexed with a: $ balooshow6 -x your-multimedia-file.mp3 Is the issue with indexing or Dolphin picking up the indexed metadata?
Viewing the properties of a file in Dolphin, then running balooshow6 -x, returns "No index information found". So this appears to be an indexing problem. After indexing it manually with balooctl6 index, it returns metadata. ...I'm a little confused though, because Dolphin still shows album art properly. Is that processed outside of Baloo?
Also worth checking whether you have content indexing enabled... These are "embedded" properties, part of the file. Baloo will only open the file to find and index them if it has content indexing enabled. I think that a "balooctl6 index ..." always indexes the content. ... I should double check that
(In reply to malikth32 from comment #2) > ... then running balooshow6 -x, > returns "No index information found". So this appears to be an indexing > problem ... A couple of tricks here, you can watch what Baloo is content indexing with: $ balooctl6 monitor and you'll see a stream of files as they are indexed... You can also prod Baloo to go and check for new/changed files with: $ balooctl6 check > ... I'm a little confused though, because Dolphin still shows album art > properly. Is that processed outside of Baloo? ... Good question, no I don't think Baloo's involved here... It could be a separate "thumbnailing" process.
> Also worth checking whether you have content indexing enabled... Setting "only basic indexing=false" in baloofilerc now causes it to index automatically as I enable columns in Dolphin's detail view mode, which is what I expected to have happen by default. > A couple of tricks here, you can watch what Baloo is content indexing with: > $ balooctl6 monitor > and you'll see a stream of files as they are indexed... > > You can also prod Baloo to go and check for new/changed files with: > $ balooctl6 check You can see I did these in my original bug report. balooctl6 monitor did not return anything even when I manually indexed a file with balooctl6 index. balooctl6 check did nothing.
(In reply to malikth32 from comment #5) > ... I did these in my original bug report. balooctl6 monitor did not > return anything even when I manually indexed a file with balooctl6 index ... Sorry, yes, of course. I would say it's a bug that it does not pick up files you index manually, it watches what baloo_file_extractor is doing though and balooctl6 does its indexing independently (In reply to malikth32 from comment #5) > ... what I expected to have happen by default ... Having content indexing enabled by default? I think that happens normally. It would be a distro thing though, how they decide to set up the Desktop.
(In reply to tagwerk19 from comment #6) > Having content indexing enabled by default? I think that happens normally. > It would be a distro thing though, how they decide to set up the Desktop. Ah, got it. In that case, I'll submit a bug report with EndeavourOS (or Arch perhaps, since they use Arch's package repo). (In reply to tagwerk19 from comment #6) > I would say it's a bug that it does not pick up files you index manually, it > watches what baloo_file_extractor is doing though and balooctl6 does its > indexing independently I would be willing to do additional testing regarding this, but I'm guessing it should be a new bug report.
(In reply to malikth32 from comment #7) > ... should be a new bug report ... I think so. It's a "least surprise" thing, I don't imagine it would be a simple thing to implement. All the same, it's worth documenting. I'll close this bug ...