protonscr

[linux] sept 12 update causes error code: -130

steamclosed reviewedSteam client
ValveSoftware/steam-for-linux#2849 · opened 2013-09-13 by akm1970 · updated 2017-09-07 · 7 comments · github
Aakm1970 2013-09-13 github

as of the update on the 12th of September I get error code: -130, failed to load web page (unknown error) on store/community pages, basicly anything using the internal browser. Library page works fine.

Opting out of beta solves the issue, opting back in brings it back.

Aakm1970 2013-09-15 github

seems the new build as of 12th of September tries to use the system settings for a proxy (in KDE that would be: system settings, network settings, proxy) I had this on manually, when I set it to "no proxy" the beta build works fine again. The none beta build seems to not care.

if Steam does not support proxy then why check the system settings and use them if a proxy is set ?

Sscottlu 2013-09-17 github

Yes you're right, there was a change in that build to read proxy settings from gsettings. The rule is look in gsettings and use those proxy settings if present. If not present, use the http_proxy environment variables. The bug that was fixed in the 9/12 build was that Steam (specifically the browser component) was not able to look at the proxy settings in gsettings.

The proxy settings in gsettings are valid for Steam to use. If the settings you are using are not valid, doesn't this affect other programs that need to know proxy settings?

Aakm1970 2013-09-18 github

(using privoxy)

if I set proxy on for http 127.0.0.1 port 8118 inside KDE > network > proxy, and for example use Google Chrome which is set to "Google Chrome is using your computer's system proxy settings to connect to the network." it works fine. If i change the port to 8119 Chrome will give a proxy error. Same goes if I do this using Konqueror.

So for me that means the settings are valid inside KDE

env does not show a http_proxy or HTTP_PROXY

I tried a bit with gsettings, not sure witch keys you use but I don't think KDE sets that at all as its Gnome (could be wrong), if you can tell me which keys, so far tried this (with proxy enabled in KDE):

gsettings get org.gnome.system.proxy.http enabled
false
gsettings get org.gnome.system.proxy.socks host
''
gsettings get org.gnome.system.proxy.socks port
0
gsettings get org.gnome.system.proxy mode
'none'

kde stores its settings in .kde4/share/config/kioslaverc

[Proxy Settings]
NoProxyFor=
Proxy Config Script=
ProxyType=1 (0 if disabled)
ReversedException=false
ftpProxy=
httpProxy=http://127.0.0.1 8118
httpsProxy=
socksProxy=

and for that you need

kreadconfig --file kioslaverc --group "Proxy Settings" --key httpProxy
http://127.0.0.1 8118
kreadconfig --file kioslaverc --group "Proxy Settings" --key ProxyType
1

does remain weird though that Steam still detects that KDE has proxy enabled or disabled, when enabled it does not get the right info though so either KDE does set some gsettings enabled/disabled key or Steam does read part of the kioslaverc file but not all of it ?

anyways if you can tell me what gsettings or other is uses to detect enabled/disabled and what to get the settings I can always try and see on my system what these keys hold

Nneko259 2014-04-24 github

I have the same issue with Gentoo+KDE without any system proxy (at least none in other applications).

Mmmstick 2014-07-18 github

Same problem here when using Arch+KDE. When setting proxies via GNOME, Steam works fine.

Nneko259 2014-07-31 github

Got fixed in the past 2-3 months somehow.

Kkisak-valve maintainer 2017-09-07 github

Closing as this issue appears to have been resolved.

Nothing extracted yet.