https://bugs.kde.org/show_bug.cgi?id=498686
--- Comment #8 from [email protected] --- (In reply to Fernando Marcelino Muniz from comment #6 and #7) > How do I fill MPV's information there? >From the link I shared earlier, you can submit a new issue report. This will require a github account it seems. 1. Click New Issue 2. Select the option that best fits the issue type. For this, I'd say probably "Request a New Feature", if requesting for an addition to .ts support and playback, or "Request a build problem" if you feel its more of a bug still, and the problem is likely not specific to any platform due to it being file-format related. 3. Fill out the issue form! Additionally, add a link back to this bug report as well, to show there's already been some discussion about this, and some interest in a solution (I'm personally in favor of frame-step support for more file types, for what its worth!). > Or rather, how do I know which version of MPV is Haruna using and its > specifics? If you installed haruna via your package manage (which I'll assume is `pacman` given the platform reported on was Arch), you can check it by querying the installed packages like so: ``` pacman -Qi haruna ``` shows that `haruna` Depends On `mpvqt`. Querying `mpvqt` then shows it depends on `mpv`, as expected, so we just query that directly in the same way to get its info: ``` pacman -Qi mpv ``` Which then will show the version of `mpv`. In my case this is "1:0.41.0-4", with Haruna version 1.8.1. This is more of an Arch Repository packaging schema however, so its best to just go to the source and cross-reference what the latest stable release is to be sure of what to report upstream. In this case, that is currently v0.41.0, so for me I'm reasonably certain that is the version Haruna is using and what to report against. Yours may be different, so its best to double check! If you installed Haruna through some other method, such as the flatpak, then figuring it out may be a bit different. Though Haruna's github also mentions that it will list the dependencies before compilation when using `cmake` so that is another option as well (though probably unnecessary). If you need any more help with filing a report upstream, let me know! -- You are receiving this mail because: You are watching all bug changes.
