GNOME Bugzilla – Bug 679728
Installing extensions from behind proxy server doesn't work
Last modified: 2013-02-04 12:54:08 UTC
Hello, I try to install gnome-shell extensions from the extension site (by using the On/Off switch), but it does not work. When I switch it to On it asks whether I want the extension installed, i click on Install and then nothing happens. If I refresh the page, the switch is back to Off. I have the gnome-shell plugin installed into the browser properly (I can for example manage my already installed extensions (manually from git) without problem). My OS Ubuntu 12.04, browser is Firefox 14, proxy is set both in Firefox Network settings and in the OS's System settings. All other OS functionalities regarding connecting to internet work (for example wget from terminal works using the proxy). i tried searching for some kind of a log, but haven't managed to find any that would contain stuff from the gnome-shell plugin. Any idea what the problem can be or where I can find some kind of information about what the problem can be? Thank you very much. Cheers, Roman
Try ~/.xsession-errors
(In reply to comment #1) > Try ~/.xsession-errors Hello, I've checked that file, but there is nothing regarding this error in there. I've also put a tail -f on it, tried to install an extension, but nothing came up in it. So either it's not the right one or the plugin is not logging anything...
This is what mine spits out. Please fix this. Many people are jaded already. JS ERROR: !!! Exception was: TypeError: info is null JS ERROR: !!! lineNumber = '83' JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/ui/extensionSystem.js"' JS ERROR: !!! stack = '"([object _private_Soup_SessionAsync],[object _private_Soup_Message])@/usr/share/gnome-shell/js/ui/extensionSystem.js:83 "' JS ERROR: !!! message = '"info is null"'
(In reply to comment #3) > This is what mine spits out. Please fix this. Many people are jaded already. The "info is null" means that GNOME Shell couldn't access the extensions website. Please make sure your proxy settings are set properly in System Settings, not juts in Firefox/Chromium.
I'm using the correct setting for my environment. It is a proxy autoconfiguration url. Even if I set both to a static proxy setting it still spits out the same message.
Dan, any ideas here?
Bueller?
Idea: Epiphany should use the same proxy settings. Does Epiphany work?
Hello, Yes Epiphany works without problems from behind the proxy.
I confirm having the same issue on Ubuntu 12.04. However, even Epiphany did not work for me. I have GNOME Shell 3.4.1 and Epiphany 3.4.1. Firefox is 15.0. The HTTP and HTTPS proxy is defined manually in the system and in Firefox.
Created attachment 223405 [details] .xsession-errors showing log lines by epiphany-browser
(In reply to comment #10) > I confirm having the same issue on Ubuntu 12.04. However, even Epiphany did not > work for me. That is not the same issue then. (In reply to comment #6) > Dan, any ideas here? It works fine for me. I set up a proxy on a different host, pointed my laptop to that proxy, and tried to install an extension, and it worked, and my laptop only created connections to the proxy server, not to extensions.gnome.org directly. Some possibilities: - your proxy server is in some way weird/broken - the error in comment 3 does not mean what Jasper thinks it does, in this particular case - you have some extension installed that is breaking the extension system
What that error message means is that message.response_body.data was null, which means libsoup had some form of error. I haven't seen a case where the error is anything but a proxy error. The only other thing I can think of is an SSL cert failure.
i guess 3.6 will shed some light on things since it has better error handling there...
(In reply to comment #14) > i guess 3.6 will shed some light on things since it has better error handling > there... so... anyone seeing this bug with gnome-shell 3.6?
(In reply to comment #15) > so... anyone seeing this bug with gnome-shell 3.6? Hello, I've tested it and it seems to be working fine in 3.6. However, I couldn't reproduce my original test case with being inside an intranet that accesses Internet through proxy, but just through getting into that company network via VPN and then going through proxy, which worked. Don't know if the situations are really comparable... Maybe somebody can reproduce it from inside an intranet.
I still experience the same issue with gnome-shell 3.6 on Ubuntu 12.10 in an intranet from behind a proxy. Will be happy to provide any debugging information.
If your proxy settings are set manually, make sure the proxy mode is not set to "auto".
Hello, I've retested it with Gnome Shell 3.6 and Ubuntu 12.10 and it seems to work fine from behind the company proxy. In Firefox my proxy is set to automatic script and in system settings the proxy is set to manual with specific proxy servers and ports. I've just managed to successfully install an extension. So for me the issue should be solved. However, I can see that more people had the issue also with Ubuntu 12.10 and Gnome 3.6.
I, too, retested installing extensions in GNOME 3.6 under Ubuntu 12.10 with both Firefox and the system explicitly pointed to a specific proxy, and all worked properly.
ok, sounds like this is fixed in 3.6. not sure what was wrong in 3.4