https://extensions.gnome.org/ reports native connector not detected #44

Closed
DavidZemon opened this Issue Mar 11, 2017 · 12 comments

Comments

Projects
None yet
4 participants

DavidZemon commented Mar 11, 2017

extensions.gnome.org reports an error:

Although GNOME Shell integration extension is running, native host connector is not detected. Refer documentation for instructions about installing connector.

Ubuntu Gnome 16.10 64-bit
Chrome Version 57.0.2987.98 (64-bit)
chrome-gnome-shell package version 7.1-1
The machine is an HP Spectre x360 (13-ac023dx) dual booting the HP-distributed Windows 10 image and Linux... not sure if that's of any use but I see partitioning info in the log below so thought it might be relevant.

david@balrogJr:~$ google-chrome
[21681:21681:0310/223822.264732:ERROR:configuration_policy_handler_list.cc(92)] Unknown policy: NTPContentSuggestionsEnabled
[21681:21717:0310/223822.299059:ERROR:nss_util.cc(808)] After loading Root Certs, loaded==false: NSS error code: -8018
[21681:21681:0310/223822.373134:ERROR:background_mode_manager_aura.cc(13)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool)
[21754:21754:0310/223822.374285:ERROR:child_thread_impl.cc(762)] Request for unknown Channel-associated interface: ui::mojom::GpuMain
[21681:21713:0310/223824.308017:ERROR:device_id_linux.cc(86)] Could not find appropriate disk uuid.
[21681:21713:0310/223824.308034:ERROR:device_id_linux.cc(89)]   DeviceID=nvme0n1p1, uuid=7243-EA6F
[21681:21713:0310/223824.308038:ERROR:device_id_linux.cc(89)]   DeviceID=nvme0n1p3, uuid=D6F01C94F01C7D45
[21681:21713:0310/223824.308042:ERROR:device_id_linux.cc(89)]   DeviceID=nvme0n1p4, uuid=10D27A1BD27A056E
[21681:21713:0310/223824.308045:ERROR:device_id_linux.cc(89)]   DeviceID=nvme0n1p5, uuid=0C4E68CF4E68B35E
[21681:21713:0310/223824.308049:ERROR:device_id_linux.cc(89)]   DeviceID=nvme0n1p6, uuid=8f60ab1f-6048-4274-8cf1-7d863e1c822d
[21681:21713:0310/223824.308052:ERROR:device_id_linux.cc(89)]   DeviceID=nvme0n1p7, uuid=a2022b34-8358-49d6-a17a-97ae704c06e4
[21681:21713:0310/223824.308056:ERROR:device_id_linux.cc(89)]   DeviceID=nvme0n1p8, uuid=0b8df956-b0c1-422f-8de7-bccd917226aa
[21681:21713:0310/223824.308059:ERROR:device_id_linux.cc(89)]   DeviceID=nvme0n1p9, uuid=ae31926a-a067-43c9-9470-479b353521c8
[21681:21681:0310/223824.383714:ERROR:display_info_provider_aura.cc(31)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const display::Display &, extensions::api::system_display::DisplayUnitInfo *)
[1,4116045568:04:38:25.980538] Native Client module will be loaded at base address 0x00007db200000000
[21681:21751:0310/223846.665039:ERROR:native_process_launcher.cc(130)] Can't find manifest for native messaging host org.gnome.chrome_gnome_shell
[21681:21752:0310/223846.673209:ERROR:native_process_launcher.cc(130)] Can't find manifest for native messaging host org.gnome.chrome_gnome_shell
[21681:21751:0310/223846.681979:ERROR:native_process_launcher.cc(130)] Can't find manifest for native messaging host org.gnome.chrome_gnome_shell
[21681:21723:0310/223846.682536:ERROR:native_process_launcher.cc(130)] Can't find manifest for native messaging host org.gnome.chrome_gnome_shell

jbicha commented Mar 11, 2017

Why are you still using 7.1-1?

I believe the Google Chrome issue was already fixed for Ubuntu 16.10 in December:
https://launchpad.net/ubuntu/+source/chrome-gnome-shell/7.1-1ubuntu0.1

But there's an even newer version available for 16.10 now: 8-2ubuntu4~ubuntu16.10.1

Very interesting. That's the latest apt-get is providing for me. I'll dig deeper tomorrow morning. Maybe I need to change my mirror.

jbicha commented Mar 11, 2017

Open the Software & Updates app (software-properties-gtk).
On the Updates tab, is the Recommended updates option checked?

Owner

nE0sIghT commented Mar 11, 2017

@jbicha

I confirming that there is no update available in yakketty repos at [ru.|de.]archive.ubuntu.com

Owner

nE0sIghT commented Mar 11, 2017

@jbicha

Also provided 7.1-1 version does not contains fix for Google Chrome

@DavidZemon

You could apply workaround described in wiki: symlink or copy all json files from /etc/chromium/native-messaging-hosts to /etc/opt/chrome/native-messaging-hosts.

Or you can use my PPA as temporal solution: https://launchpad.net/~ne0sight/+archive/ubuntu/chrome-gnome-shell

jbicha commented Mar 11, 2017

@nE0sIghT right, 7.1-1 doesn't work for Google Chrome but 7.1-1ubuntu0.1 would.

You're correct that chrome-gnome-shell wasn't published correctly to yakkety-updates. I will try to get that fixed.

@DavidZemon You can manually download the latest SRU for 16.10. Click
https://launchpad.net/ubuntu/+source/chrome-gnome-shell/8-2ubuntu4~ubuntu16.10.1
then click amd64 then download the .deb on that page.

Woohoo!!! It's so nice to finally have my extensions synced across my many devices. Thank you all for this app.

@jbicha, I used the launchpad link to download the deb package and install it. Will it be auto-upgraded next time a newer release is pushed to the repos?

jbicha commented Apr 10, 2017

This should be fixed today. It may take a little bit of a time for your update server to get the install file for chrome-gnome-shell 8-2ubuntu4~ubuntu16.10.1.

@nE0sIghT I believe you can close this bug now.

Owner

nE0sIghT commented Apr 10, 2017

@jbicha Thanks

@nE0sIghT nE0sIghT closed this Apr 10, 2017

hi everyone,
what about having this error open chrome using OpenSUSE 42.2
cant find a topic about

Owner

nE0sIghT commented Apr 18, 2017

@ghanoumessi

This issue is related to Ubuntu only. Open new issue if you having one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment