Gnome 3 Shell Proxy Settings and Gnome Shell Weather Extension Don't Play Well Together

The title pretty much says it all.

Fedora Core 16, and Gnome shell 3.2.2.1.

metadata.json from weather@gnome-shell-extensions:
{

"uuid": "weather@gnome-shell-extensions.gnome.org",
"name": "Weather indicator",
"description": "Adds weather information menu",
"shell-version": [ "3.1.90", "3.1.91", "3.1.92", "3.2", "3.3" ],
"localedir": "/usr/share/locale",
"url": "https://github.com/simon04/gnome-shell-extension-weather"
}

If you set via Network Manager the proxy settings to something other than "none" your weather shell extension will not be able to query the server and the extension will display that is continually reloading. 

Turning off the system proxy (and restarting the gnome shell) fixes the problem.

Some discussion of the issue which seems to be rooted in the gnome shell infrastructure here


If you had started the gnome-shell from a terminal you can see errors of this sort 

S ERROR: !!!     message = '"Argument 'data' (type utf8) may not be null"'
    JS ERROR: !!!   Exception was: Error: Argument 'data' (type utf8) may not be null
    JS ERROR: !!!     lineNumber = '0'
    JS ERROR: !!!     fileName = '"gjs_throw"'
    JS ERROR: !!!     stack = '"("Argument 'data' (type utf8) may not be null")@gjs_throw:0
([object _private_Soup_SessionAsync],[object _private_Soup_Message])@/usr/share/gnome-shell/extensions/weather@gnome-shell-extensions.gnome.org/extension.js:491
"'


as documented here.

https://bbs.archlinux.org/viewtopic.php?id=138463


By the way the WOEID location codes of the form XXXXNNNN (4 letters followed by 4 numbers) can be hard to track down.

Go to (replace your city where it says Boston) and you can get the one you need.

http://xoap.weather.com/search/search?where=Boston





Comments

Popular posts from this blog

Hit failing alternator with a hammer to confirm diagnosis of failing alternator due to bad brushes

alternatives --install gets stuck: failed to read link: No such file or directory

Using SSH, SOCKS, tsocks, and proxy settings to create a simultaneous "dual use" work/home computer