google-chrome not working #13
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: ryze/ff2mpv-rust#13
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Firefox can call mpv to play videos, but it cannot work using google-chrome, and there is no error message in the console.
Looks like Chromium browsers require the
chrome-extension://
to end with the leading slash, can you try adding it manually and testing again?Adding '/' at the end still doesn't work.
Can you paste the contents of the manifest as is here in the code blocks?
Could you provide some more information? What distribution you are trying this on, what Chrome version and does this work with the original native client?
ArchLinux(Hyprland)
Chrome: 123.0.6312.122-1
mpv: 1:0.37.0-3
I based on FF2MPV Installation and Google's documentation Configuration
ff2mpv.json
. No other native client can test.Looks like AUR package also writes manifest in
/etc/opt/chrome/native-messaging-hosts/ff2mpv.json
, maybe Chrome is picking up that instead of the one in your home directory? Try editing it.Chrome made a copy of it myself, but I didn't create it.
I would suggest trying with the original manifest and see if it works first, should be
ff2mpv-native-messaging-host-git
in AURGoogle Chrome's problem, chromium work, and lack of
/
at the end.You mean the problem is with your Chrome installation? The only issue that I can reproduce is the lack of leading slash there. Does it work correctly on both browsers after adding it?
Chrome still not working. Chromium works.
I tried changing the path to
/usr/bin/kitty
and successfully started kitty, which proves that Chrome’s NativeMessagingHosts configuration is correct.Same
I tried it on Brave and it works there. I also switched to it