1167969 - New install (2.33.1) on XP sets network.proxy.type to 5 producing "network link was interrupted" error on all URL fetches.

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[K R Perlow]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1
Build ID: 20150321194901

Steps to reproduce:

Trying to figure out why I could no longer port a Seamonkey profile from my Mac to my PC (XP), as I used to be able to up until a month or 2 ago, I removed Seamonkey from the PC and reinstalled it fresh (having removed the Seamonkey directory entirely from C:\Documents and Settings\Application Data\....  The virgin install had the same problem as my ported Mac profile, so I fiddled around on its (brand new) about:config page.


Actual results:

Since I have no proxy server, all URL fetches were quickly timing out with "Network link was interrupted. Please try again."  The odd thing is that I have never used a proxy server on my Mac either, so some Seamonkey update must have tweaked the network.proxy.type value on the Mac in the update process (also to 5).  The Mac code doesn't seem to care about that proxy value--your documentation notes values of only 0 through 4--but the PC code obviously does.


Expected results:

Profiles should port seamlessly, and now they do again since I went into the Mac Seamonkey's about:config and reset network.proxy.type to 0.  But I have no idea how it got flipped (I had never mucked around with the prefs.js file at all).  On the PC I use the generic XP firewall; my XP anti-virus is (and was way before this problem happened) Eset NOD32, though I did update its license recently.

Comment 1

[Philip Chee]

network.proxy.type 5 is PROXYCONFIG_SYSTEM which means use whatever proxy settings your OS (in your case OSX) is using, which is probably none. I don't know about your PC.

As to how it got flipped. There is a online/offline button on the status bar at the bottom of the browser window. Right click on it will bring up a proxy menu. You may have accidentally hit the menu and changed from None to System Proxy. Mind you this is just wild speculation on my part.

Comment 2

[K R Perlow]

Hmmm.  The probable corruption sequence would have started on the PC, flipping the network.proxy.type value on the PC, with the Seamonkey profile then ported to the Mac, which doesn't care about that setting. But when ported back again to the PC, Seamonkey got bollixed up.  Which means that the PC still has this erroneous setting someplace (thus explaining why a virgin install sets it to 5 instead of 0).  I'm trying to track that down now on the PC, and it's odd that it would happen and have no other ill effects, but that's got to be it.  That is, unless your phone's been ringing off the hook for weeks from XP users (and there's still plenty of us out there) whose Seamonkey installs have all been failing.

Last thing I expected was a reply to this issue on Memorial Day weekend.  Thanks--but please, just resolve it "no change" and go home :-)

Comment 3

[Philip Chee]

Closing as WORKSFORME