-
Notifications
You must be signed in to change notification settings - Fork 297
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
Doesn't work with Waterfox on Linux even though app already installed #186
Comments
What's the profile directory for Waterfox ? |
/home/user/.waterfox/user.Default User/ |
If you copy ~/.mozilla/native-messenging-host into ~/.waterfox, does it work? |
Do not use the Aur package, use the package we provide: https://github.com/aclap-dev/vdhcoapp/releases Install the tar.bz2 (untar it anywhere you want) and the run Then This is necessary for waterfox to know the existence of the coapp. |
How do you set the profile directory? |
Using the "waterfox -p" command |
And is it recognized if you do not use a custom profile? If not, is it recognized if you create a directory like this: ~/.waterfox/native-messenging-host which recreate the .mozilla directory structure? I'm trying to understand if it's a bug of Waterfox or a bug of our Coapp. |
I tested using a default Waterfox profile (i.e. /home/user/.waterfox/8v5oj8e6.Default User/) and it still does not detect the app which is already installed, same error as custom profile: "Checking companion app returned: An unexpected error occurred". /home/user/.waterfox/native-messaging-hosts/ already exists containing the file: "net.downloadhelper.coapp.json" |
I'll look up waterfox internals. Creating Do you use a flatpak or snap version of Waterfox? |
Using AUR version: waterfox-bin G6.0.6-1 |
There's a path to the binary within /home/user/.mozilla/native-messaging-hosts/net.downloadhelper.coapp.json What's the path, and when you run that binary with |
There is only 1 file within the folder: /home/user/.mozilla/native-messaging-hosts/net.downloadhelper.coapp.json There is no other files or binary in that folder. The only binaries are in the install folder: "/opt/vdhcoapp-2.0.8/" vdhcoapp, ffmpeg, ffprobe Any chance you can run/test it on your end, and/or in a virtual environment Manjaro XFCE? |
Look inside /home/user/.mozilla/native-messaging-hosts/net.downloadhelper.coapp.json grep path ~/.mozilla/native-messaging-hosts/net.downloadhelper.coapp.json This will give you the path of the binary (for example "/opt/foo/vdhcoapp"). Then run that binary with the option --info: |
[linux@user vdhcoapp-2.0.8]$ ./vdhcoapp --info |
This is maybe not the correct place because it's not about Waterfox, but it's a similar issue, and the solution might help others. I'm on Fedora 39 with Firefox (RPM, not snap or whatever), running with multiple profiles. When I updated to 2.0.10 and clicked the "Recheck" button, at first I had issues finding the Companion App. It returned: What I figured out, is that when doing a system-install ( After I symlinked So, to round it up, this worked for me, with multiple Firefox profiles: |
@storm49152 Hm, I'm surprised you had to do that. Did you run the install command as root (you should not)? |
$ ln -s /usr/lib/mozilla/native-messaging-hosts/net.downloadhelper.coapp.json ~/.mozilla/native-messaging-hosts |
If you arrive here because of Google, please look at the troubleshooting section: https://github.com/aclap-dev/vdhcoapp/blob/master/README.md#troubleshooting |
Just had an idea (since I've had so many issues getting it to work mainly with Mozilla-based browsers, and so far it's still not working on the latest Waterfox vG6.0.7: "Checking companion app returned: An unexpected error occurred". I was thinking (if it's possible and to code) in the settings under General > "Companion App", when it states "Companion App not installed", why not add a clickable button there that loads the system file manager which allows the user to manually "point" to the installed Companion app binary file path in their directory, and/or any other necessary files for it to work. That way it can then detect the Companion App files that have already been installed on the system, especially for the many varied Linux distros and other obscure/less common browsers, and also not having to create manual symlinks to get it to work. So the end result would then hopefully be: Found companion app: VdhCoApp 2.0.10 What are your thoughts on this? |
Sadly this is not how browser extension work. The extension doesn't know and can't know where the coapp is located.
I have no idea what's going on with these special version of Firefox, but I believe the bug is on their side, not on the coapp side. They should be looking for the manifest in the mozilla directory, but they're not. |
Ok, thanks for the update & trying to resolve this issue... If there's any other future updates or a fix for this, please post here. Cheers. |
@paulrouget That would be my mistake then: I checked the Bash history, and I installed as root. |
Sorry to revive this. But considering I have essentially the same kind of problem, it felt more appropriate than to start a new issue.
|
@Kromilan Does this help? #195 (comment) |
vdhcoapp-bin 2.0.7-1 [AUR]
waterfox-bin G6.0.6-1 [AUR]
[Linux, Manjaro XFCE]
The text was updated successfully, but these errors were encountered: