New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--loop-file (and possibily other) config parameters show no effect in flatpak mpv #23
Comments
Can't reproduce,
showing in the verbose log. Can you try with clean |
Weird. Just tested with a completly fresh environment (also deleted .config/mpv, just to be sure). Can still reproduce it. Search for:
|
Interesting. Found the culprit. The issue is reproduciable while the permission Unsetting the permission |
Is it bug in this extension then? |
As rpm mpv is not showing the same issue it's difficult to say whether it's an issue of the extension or flatpak mpv without a deep dive into the code. Just noticed: the rpm mpv does not provide a mpris connection by default, right? Maybe it's an issue between https://github.com/hoyon/mpv-mpris and https://extensions.gnome.org/extension/1379/mpris-indicator-button/ ? |
Created hoyon/mpv-mpris#55 |
Feedback by mpv-mpris dev @hoyon: |
Can confirm. mpv-mpris 0.6 fixed this issue. Thanks @fastrizwaan and @hoyon. |
Tested on
Flatpak 1.12.2
app/io.mpv.Mpv/x86_64/stable - 2021-10-23 06:59:31
Description
Setting
loop-file=inf
in mpv.conf or providing it as a command line argument does not show the expected effect on the flatpak version of mpv.To reproduce:
mpv.conf
containingloop-file=inf
ORflatpak run io.mpv.Mpv --loop-file=inf <some_file_path>
Diffing the logs of an rpm mpv and flatpak mpv using
-v
shows that the flatpak mpv is doing some parameter resets in the end (which is not shown for the rpm version of mpv).Both rpm and flatpak mpv show:
Only flatpak mpv afterwards shows (which I presume results in a reset of the parameters):
Noticed that on startup flatpak mpv is also loading one additional config file which I was not able to locate:
The text was updated successfully, but these errors were encountered: