maemo.org Bugzilla – Bug 3712
RSS reader uses proxy settings even when proxy disabled
Last modified: 2011-01-17 21:41:04 UTC
You need to log in before you can comment on or make changes to this bug.
SOFTWARE VERSION: diablo STEPS TO REPRODUCE THE PROBLEM: disconnect from wireless access point. edit the wireless settings to add an http proxy and port. save it. go back in, disable the proxy but leave the host and port completed. fire up the RSS reader application and refresh feeds. EXPECTED OUTCOME: RSS reader will connect directly to the appropriate servers ACTUAL OUTCOME: RSS reader attempts to contact the proxy and fails to update feeds. REPRODUCIBILITY: always EXTRA SOFTWARE INSTALLED: OTHER COMMENTS: I have marked this as medium high because the RSS reader gives NO indication that it is attempting to use a proxy, and I only realised what it was doing when I logged into the tablet and used "netstat -an | grep tcp" and found a bunch of SYN_SENT hanging sockets to the non-existent proxy, a non-technical person would never know why RSS reader was failing!
Paul, is this a duplicate of bug 304? > SOFTWARE VERSION: > diablo That is vague. Please tell us the exact version (4.2008.23-14 or 4.2008.30-2 for example).
my product version is 4.2008.23-14 I am running with all the latest patches, for some reason it hasn't upgraded the version. Linux mytablet 2.6.21-omap1 #2 Wed Jun 11 15:00:15 EEST 2008 armv6l unknown
I had same problem. I enabled the proxy for the Privoxy. After uninstalling Privoxy, I disabled the proxy but I left 127.0.0.1 in the proxy address fields. The RSS *AND* Application Manager failed to connect to the internet until I deleted the 127.0.0.1 from the proxy settings.
(In reply to comment #3) N800 with 4.1.2 (4.2008.36-5) here.
I have updated to the newest release of Diablo 4.2008.36-5, problem still exists AFAICT.
Confirmed on N810/4.2008.36-5. With a proxy set but disabled I can see the requests in my squid logs. I think the real bug may be in the connectivity settings GUI not updating gconf when the "Use proxy" checkbox is switched off: $ gconftool-2 -g /system/http_proxy/use_http_proxy true #998, #3110(?) & #3402 may possibly be different manifestations of the same issue.
Hm, scratch that. GConf *is* updated, I was just looking at the wrong place. Apparently applications are supposed to check /system/proxy/mode (or use Libconic's con_ic_connection_get_proxy_mode) first. Looking at the source, neither osso-rss-feed-reader nor hildon-application-manager do this (don't know about mediaplayer).
is this or the parent bug going to be looked at, or should we simply assume people are going to find this out the hard way and get annoyed and frustrated?
(In reply to comment #8) > is this or the parent bug going to be looked at It currently looks like this only has a low priority for Nokia unfortunately.
DIABLO 5.2008.43-7: 1. Set up some fake proxy in Connection Settings > Advanced 2. In Terminal, run "gconftool-2 --get /system/proxy/mode". Get "manual". 3. Go to Connection Settings > Advanced 4. Disable "Use proxy" 5. In Terminal, run "gconftool-2 --get /system/proxy/mode". Still get "manual". Wrong. Current Fremantle: 1. Set up some fake proxy in Connection Settings > Advanced 2. In Terminal, run "gconftool-2 --get /system/proxy/mode". Get "manual". 3. Go to Connection Settings > Advanced 4. Disable "Use proxy" 5. In Terminal, run "gconftool-2 --get /system/proxy/mode". Get "none". Correct. I also tested this with the User Interface of course and RSS feed reader could access the feeds. Bug 304 is about the RSS feed reader in Fremantle completely ignoring the global Proxy. Hence I could say that testing this bug depends on bug 304, but as the gconf key clearly behaves differently in Diablo and Fremantle I consider this FIXED in the internal Fremantle version. Unfortunately this issue itself described in this bug report is a WONTFIX for Diablo as Diablo is in maintenance mode and Nokia will only provide bugfixes for critical issues if at all. For your interest the Mer project aims to provide a community backport of Fremantle for N8x0 devices. See http://wiki.maemo.org/Mer for more information.
Nope, still not fixed: 1. Configure a proxy for the current internet connection. 2. Start watching the proxy logs on the server. 3. Start RSS reader, refresh a feed or two: logs show requests going through proxy as expected. 4. Disable the proxy for the current internet connection. Verify /system/proxy/mode is now "none" (it is). Optionally, restart RSS reader (makes no difference). 5. Refresh a feed again. Logs still show the requests going through the proxy. 6. Stop the proxy and refresh again. Refresh fails. (In reply to comment #10) > Bug 304 is about the RSS feed reader in Fremantle completely ignoring the > global Proxy. Hence I could say that testing this bug depends on bug 304 Not really, as that one's about not honouring an autoconfig proxy setting (as in <http://en.wikipedia.org/wiki/Proxy_auto-config>). The summary was a bit misleading though.
(In reply to comment #6) > Confirmed on N810/4.2008.36-5. With a proxy set but disabled I can see the > requests in my squid logs. > > I think the real bug may be in the connectivity settings GUI not updating gconf > when the "Use proxy" checkbox is switched off: > > $ gconftool-2 -g /system/http_proxy/use_http_proxy > true > > #998, #3110(?) & #3402 may possibly be different manifestations of the same > issue. > Untill this gets fixed, using command $ gconftool-2 --set /system/http_proxy/use_http_proxy --type bool 0 disables proxy usage. After restarting RSS reader it can update feeds again! Tested on N900 PR1.1.
"In 10.2010.19-1, feed is not added when Proxy connection is enabled and previously added feed contents are not deleted, it is displayed when selected. "unable to add feed, address is invalid" info banner is displayed when user try to add valid feed also. Hence FIXED (The info banner displaying is not correct, it should display about netconnection, but that is another issue).