Define the information you need
If you need a file’s media properties, first identify the actual file and the question: codec, track language, dimensions or another specific property. A player’s output resolution and the source file’s stored properties are different things. Keep the intended item selected in the playlist.
Choose a local authorized sample for the integration check. A remote reference may have a different access context from a local file, so do not begin by assuming every URI can be handed to another desktop utility. Keep the source path private if it identifies personal material.
Check the documented optional dependency
KDE’s Haruna release notes document a playlist action to open a file in the MediaInfo application when it is installed. Check the Haruna version and whether that separate application is actually available. A menu entry depending on another app can be absent without indicating failed video playback.
Use MediaInfo’s own supported distribution route for the actual desktop if the utility is needed. Retain its identity and version. Do not install a similarly named unrelated download simply to make a context-menu item appear.
Inspect the selected file through the intended action
Use the playlist’s available context action for the known local sample and confirm which file opens in the utility. Similar item titles can otherwise produce a technically valid report for the wrong source. Compare the utility’s displayed filename with the selected sample.
Read the property relevant to the task and preserve its units. A stored video frame rate, an output display rate and an observed playback-rate change are different measurements. Do not assign a quality verdict to a single codec label or assume a filename is a reliable media-property report.
Keep the dependency and result in the report
If the action fails, record Haruna’s version, the selected input type, the installed utility and the exact handoff stage. Confirm whether the utility can inspect the same local sample independently. That separates application integration from a source-access or utility problem.
The expected outcome is a correct-file information view through an understood optional dependency. It does not alter or repair the media, prove source authorization or replace an actual playback test. Review exported reports for private filenames before sharing them with a support destination.
Questions answered
Why can the MediaInfo action be absent while Haruna plays the file?
KDE documents it as an integration with a separately installed application. Player playback and that optional handoff are different capabilities.
What should I verify after the utility opens?
Confirm it received the intended file, then read the specific property and units needed for the task.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.