Web browser integration doesn't work in Chrome 65.0 about gnome-shell-extension-gsconnect

[indaleto]

It's working here too. Thanks...

[andyholmes]

No problem :) In future it will just be installed automatically since it's just a < 1KB file. I guess at the time it made sense to make it a switch and put the links there.

[andyholmes]

It's currently only possible to run the WebExtension in one (running) browser at a time since the native messaging host (connector between Shell and Browser) is currently restricted to a single instance. If only Firefox or Chrome is running when the extension is loaded it should be able to connect, but both can't connect at the same time.

This is a restriction I might lift in future releases of the Gnome Shell extension, but I haven't investigated the consequences of what might happen if two native messaging hosts are running at the same time or if one fails to exit when the browser closes.

You can leave this bug open though, and I'll come back to it when I get a chance.

[nneto]

But even before installing the addon on Firefox, it wasn't working on Chrome, and while Firefox isn't running, it still doesn't work here on Chrome.

[andyholmes]

Could you open chrome://extensions/ then enable "Developer mode" at the top and click "Inspect views: background.html" to see if there are any errors related to connecting to the native messaging host?

[indaleto]

I have this problem with 65.0 chrome version. The message I've found is:
Disconnected from native host: Specified native messaging host not found. onDisconnect @ background.js:266

[andyholmes]

Okay, apparently the native messaging host manifest needs to be installed in different directories for chromium, chrome-stable, chrome-beta and chrome-unstable. I'll have to clean this up later, but this zip should work for you (the WebExtension itself works as-is):

[email protected]

[indaleto]

Thanks for your reply but
Nop, now it gives multiple errors:
Error in event handler for runtime.onMessage: TypeError: Cannot read property 'postMessage' of null at postMessage (<URL>) at onMessage (<URL>) at <URL> background.html:1 Error in event handler for runtime.onMessage: TypeError: Cannot read property 'postMessage' of null at postMessage (chrome-extension://jfnifeihccihocjbfcfhicmmgpjicaec/js/background.js:47:10) at onMessage (chrome-extension://jfnifeihccihocjbfcfhicmmgpjicaec/js/background.js:67:9) at chrome-extension://jfnifeihccihocjbfcfhicmmgpjicaec/js/browser-polyfill.min.js:1:6026

background.js:266 Disconnected from native host: Specified native messaging host not found. onDisconnect @ background.js:266 background.js:64 REQUEST: {"type":"devices"} background.js:42 SEND: {"type":"devices"}

Missing message parameters postMessage @ background.js:45 background.js:64 REQUEST: {"type":"devices"} background.js:42 SEND: {"type":"devices"}

Disconnected from native host: Specified native messaging host not found. onDisconnect @ background.js:266 2background.js:266 Disconnected from native host: Specified native messaging host not found. onDisconnect @ background.js:266 EventImpl.dispatchToListener @ extensions::event_bindings:403 publicClassPrototype.(anonymous function) @ extensions::utils:138 EventImpl.dispatch_ @ extensions::event_bindings:387 EventImpl.dispatch @ extensions::event_bindings:409 publicClassPrototype.(anonymous function) @ extensions::utils:138 dispatchOnDisconnect @ extensions::messaging:378 background.js:64 REQUEST: {"type":"devices"} background.js:42 SEND: {"type":"devices"}

[andyholmes]

Seems to be the same error, could you confirm the native messaging host manifest was installed correctly?

$ ls ~/.config/google-chrome-unstable/NativeMessagingHosts/
org.gnome.shell.extensions.gsconnect.json

If so try to disable then re-enable the WebExtension

[nneto]

I just had to copy the content from the zip and it's working now without errors here.

edit: just to make clear, the problem was the same @indaleto reported: "Disconnected from native host: Specified native messaging host not found. onDisconnect @ background.js:266". After using the zip, I didn't have other problems. I confirmed the native messaging host manifest was installed correctly.

[andyholmes]

That's great, I'll wait for @indaleto to confirm its fixed with that zip then close the bug. Thanks for testing.

[nneto]

One question: now that the extension is working in both Chrome Unstable and Firefox, and I can send links from both of them while both are open, I don't get what you meant with "If only Firefox or Chrome is running when the extension is loaded it should be able to connect, but both can't connect at the same time".

[andyholmes]

Yep, that was fixed in v8+, now it can run as many instances as necessary. It will exit whenever the browser exits, so there's no danger in running multiple instances or zombie processes.

You could run it in firefox, chrome, chrome beta and chrome unstable at the same time if you wanted.

[andyholmes]

I'm closing this as I'm confident it's been fixed in git.

[alcarraz]

I'm having this problem for a while I don't have the ~/.config/google-chrome/NativeMessagingHosts/ folder even though I tried uninstalling and reinstalling the chrome extension.

[andyholmes]

Have you enabled Web Browser Integration in the preferences?

[alcarraz]

oups didn't remember that step, I feel so ashamed , sadly googling for the message didn't provide that.