You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mediator app wouldn't start when installed into a Chrome/Chromium via snap.
There are several issues with how Chromium is run via snap:
Chromium can't see locally-install pip packages, it doesn't have access to ~/.local. Solution: sudo pip3 install brotab
Native app config is in a different place, e.g.: ~/snap/chromium/1165/.config/chromium/NativeMessagingHosts/brotab_mediator.json. Solution: support that location in bt install (TODO).
Wrong path to binary. It should be something like /usr/local/bin/bt_mediator
The mediator still wouldn't start with the message: "Native app cannot be found" or along those lines.
I couldn't figure out all the issues with the snap-installed chromium and I'll probably will not do that since I removed it and installed from apt repo: sudo add-apt-repository ppa:saiarcot895/chromium-dev. Anyone's willing to dig into it, welcome.
The text was updated successfully, but these errors were encountered:
I'm also fiddling around to find a workaround. Main problem is that Native Messaging Hosts do have dependencies you don't just want to put into the snap. So I don't see a probable solution around there.
Mediator app wouldn't start when installed into a Chrome/Chromium via snap.
There are several issues with how Chromium is run via snap:
~/snap/chromium/1165/.config/chromium/NativeMessagingHosts/brotab_mediator.json
. Solution: support that location inbt install
(TODO)./usr/local/bin/bt_mediator
I couldn't figure out all the issues with the snap-installed chromium and I'll probably will not do that since I removed it and installed from apt repo:
sudo add-apt-repository ppa:saiarcot895/chromium-dev
. Anyone's willing to dig into it, welcome.The text was updated successfully, but these errors were encountered: