This should be fixed in commit 104d2139 [1].
It would be helpfull if you will test this.

[1] https://git.gnome.org/browse/chrome-gnome-shell/commit/?id=104d2139ad19ff067360fc64e1801a6aa2930066

*** Bug 787101 has been marked as a duplicate of this bug. ***

I tried to test your fix, but I still have the problem.

To be sure every thing is OK in my test.

dconf values are defined in the user context (nb. As root, the proxy values are not set, but I guessed, the extension is started with user ownership)

Additionally, following export values are set (using ~/.profiles to be shell independent):
export http_proxy=http://proxy.MYCOMPANY_INTERN_DOMAIN.de:8080
export https_proxy="$http_proxy"
export HTTP_PROXY="$http_proxy"
export HTTPS_PROXY="$http_proxy"
export no_proxy=127.0.*,10.*,localhost,*.MYCOMPANY_INTERN_DOMAIN.de,::1
export NO_PROXY="$no_proxy"

I did not find out how to easily launch the script and send the "checkUpdate" request (request['execute'] == 'checkUpdate').

I assume, that this is dbus management, where I have no knowledges.

For my testing, I therefore started my Firefox every time (which is not optimal, but if the test is ok, I am ok).
→ For further testing, can you provide me some Python Script, which would trigger the event?

Note: Firefox is configured to use the system proxy settings (but I assumed, that the proxy settings are not inherited from Firefox)

> I did not find out how to easily launch the script and send the
> "checkUpdate" request

You can trigger update check by disabling it and enabling it again in Firefox extension options.
Make sure to save settings after you disable update check.

I used the today's master version (containing your modification and using this information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome/Installation#Cmake_installation )

The installed script ( /usr/bin/chrome-gnome-shell ) was correct

(In reply to Yuri Konotopov from comment #4)
> > I did not find out how to easily launch the script and send the
> > "checkUpdate" request
> 
> You can trigger update check by disabling it and enabling it again in
> Firefox extension options.
> Make sure to save settings after you disable update check.

It works easier...

Thank you.

Any Idea, if the Problems comes from my configuration or the extensions?

I tried to export some logs, like proxy values coming from Gio.ProxyResolver.get_default().lookup(update_url)

But I am not a python expert...

Created attachment 362103 [details]
get_proxies.py

Please try to run attached script and post it's output here

Detected proxy: http://http://proxy.ANY_NAME.de:8080
All proxies: ['http://http://proxy.ANY_NAME.de:8080']

http://http://proxy → The problems comes from my configuration. It seems I should not use http:// in dconf. 

Test is successful.

I guess it will solve some other proxy problems, that I have :/

Closing then

I forgot to say thank you :D

Please cherry-pick for Debian, drives me crazy, get these error messages every hour all day long.

(In reply to Frank from comment #11)
> Please cherry-pick for Debian, drives me crazy, get these error messages
> every hour all day long.

https://www.debian.org/Bugs/Reporting

(In reply to Frank from comment #11)
> Please cherry-pick for Debian, drives me crazy, get these error messages
> every hour all day long.

You should:
- As Yuri said, report to your distribution (debian)
- meanwhile, you can help yourself, by installing it manually using the cmake installation (it requires only 10 Minutes to get rid of this messages, until Debian provides the new fix)
→ The HowTo Cmake (https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome/Installation#Cmake_installation) is clear and concise and the system requirements are well listed (apart that git must be installed and, in your case, do not forget to configure your proxy, if you are not used to it)

Sorry, I completely for got, I wrote them some time ago about this… but no response nor implementation yet…