Closed Bug 28771 Opened 25 years ago Closed 25 years ago

Running install destroys network connectivity for NT.

Categories

(SeaMonkey :: Installer, defect, P3)

Product:
SeaMonkey
Component:
Installer
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: jar, Assigned: ssu0262)

References

Details

(Whiteboard: [nsbeta2-] [dogfood-])

I tried both this morning's build, and this evenings. In both cases, after running the Netscape installer "NetscapeSetup" my NT box become useless, and unable to connect to any sites on the net. To repair, I was forced to reboot NT. Details: a) Run NetscapeSetup b) Select typical install c) decline to use a new directory when asked d) notice that the installer hangs. At this point, also notice that a browser can't reach any external pages. Watching the lights on my firewall, I can see that my NT box is no longer even contacting the internet :-(. I was running Sera before the install. After being hosed, I even tried stopping all browsers, disconnecting sera, and continuing. Still, no glory. Then I tried logging out of NT, and logging back in. Still, no glory. I believe this started for me this weekend, and I was expecting this part of the installer to be fixed today... and since it isn't, I decided to file. If I had to guess, I'd say that the installer hogs a pile of outbound connections, and never gives them up when exiting. Alas, I'm no longer a window's guru, and can't really guess that intelligently here :-(. I decided to copy Rick and Troy in case they had clever insight into this issue.
Keywords: dogfood
The only code that deals with making outbound connections (or any connections) to download hasn't changed since 9/13/99. I have a Friday ~4pm build that works fine under NT4. I'm pulling right now. I'm wondering if this could be related to: http://bugzilla.mozilla.org/show_bug.cgi?id=28775
Status: NEW → ASSIGNED
adding Cathleen and Michaell to the CC: list.
I have a build from last night (~12am) and it seems to be working fine under my NT4 (sp3) system. Jar, can you try today's build to see if you still have the problem? And if so, can I take a look at your system?
Putting on PDT+ radar for dogfood.
Whiteboard: [PDT+]
I tried yesterday's 5pm build from sweetlou at home, and everything was still okay on my system. I could browse via seamonkey and Communicator. My network did not seem to be affected.
grace, are you able to reproduce this? If not, I'm going to close this bug as worksforme. FYI: my test case did include Sera running.
I could not reproduce on my NT at work, I can try on my Win95 from home with SERA running and let you know
jar, are you able to reproduce it on your machine?
updating on build downloaded and installed while on SERA build 2000022309
Marking worksforme since no on e can reproduce. jar, can you mark verified or reopen if still a bug with today's build.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
I tried it this afternoon at home on my machine, and it crashed as I described. My *guess* is that it has to do with the dialog about: "You already have a copy installed in this directory, would you like to use something else" (I'm paraphrasing). I answered "no", and then I hung on the download (it said "trying" many times). When I finally "cancelled" the setup, (it took two cancels, each with an "are you sure," followed by one click of the X atop the setup, and its "are you sure" to get out of every thing.). Before I even started to cancel, I was completely locked out of the internet. If you want, I'll blow away my install directory in advance, and see if that works, but I may lose the ability to reproduce. Comments? Thanks, Jim
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Jar, the download problem could attributed to the current network problems people are having when download files from sweetlou. The warning about selecting a different destination path does not come into play until mozilla.exe is run (it's related to having legacy files laying around the same directory). If you want, you can just rename your destination directory and try again. I would also like to take a look at your system if you could bring it in. There should a lab in the building with direct phone lines to dial out, so we can test it here.
you know what. I assume that you have a laptop, but I'm probably wrong. I would still like to take a look at your system though, if I could swing by your place.
The crashing machine is a 200MHz box sitting on a desktop at home (Redwood City). My laptop is doing "ok" by comparison (not reproducing this bug.)
jar, would it be possilbe, if you can bring your home machine in tomorrow? so we can take a look at it? pleeeeease..... :-)
unable to reproduce it in house. I will wait until there's another reproduceable machine to fix this. I'm not sure what to do with the PDT+ flag. I'll mark it worksforme until we see another case pop up.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → WORKSFORME
I can take some calls at home, and try some stuff... but it is a desktop machine... and a pain to transport. I can live with the "worksforme" (from the engineers)
ok
Status: RESOLVED → VERIFIED
Jar was able to reproduce this problem on his laptop which he brought in and showed me. I'm going to attempt to reproduce this on a desktop system in-house. I think that the key requirements are: * WinNT 4.0 w/sp6 * network connected via SERA to the internet. I'm reopening this bug.
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
Status: REOPENED → ASSIGNED
clearing PDT+. I'm still investigating this bug.
Whiteboard: [PDT+]
Please also consider looking at the history of the installer. This used to work fine... and then it broke. It might be that the weekend I first noticed it was just after installing SP6. I looked at the history of my machine, and I think the Service Pack un-install utility is dated 2/26, which suggests that I upgraded *after* having this problem (the bug was opened on 2/21).
Putting on DOGFOOD+ radar.
Whiteboard: [DOGFOOD+]
setting target milestone to M17, also nominating for beta2
Keywords: beta2
Target Milestone: --- → M17
Keywords: nsbeta2
Here is a suspicious incident on win98: ---------------------------------------------- Operating System: Windows 98 Language: English Issue Summary: problem with Dial Up after using Netscape 6 Component: Installation Doing What: Other Severity: Other Can Reproduce: Sometimes Try this URL: http:// Issue Detail: After closing Netscape 6, I sometimes want to go on the net to check my mail hours latter and find that I have a prblem with the Dial up to the net. Re-booting clears the problem up. Email Address: nospam@netscape.com
Keywords: beta2
Hmmm... note that a) I only have trouble with the installer. I have no trouble once it is installed (I have to use devious manual means). b) My problem was actually on NT, not just Win 98. My bet is that the above guy is having dialer problems, and it is probably not too related... but you can never tell. I'd say that IF he was seeing the same problem, then he wouldn't have trouble dialing, rather he'd *think* he was still connected, and his browser would spin (and never even ask for a re-dial).
Whiteboard: [DOGFOOD+] → [dogfood+]
We will try to reproduce this on a third clean machine. If it's still not reproducable, we probably won't be able to fix this problem by PR2.
Putting on [nsbeta2+][6/01] radar. This work must be done by 06/01 or we may pull this for PR2.
Whiteboard: [dogfood+] → [nsbeta2+][6/01][dogfood-]
Due to slip in schedule, moving this bug from [6/01] to [Will be minus on 6/15] for fix deadline.
Whiteboard: [nsbeta2+][6/01][dogfood-] → [nsbeta2+][Will be minus on 6/15] [dogfood-]
Cleaning up status whiteboard by marking beta2 minus (6/15 has passed). I've started to encounter other crashes in Seamonkey, which damage network connectivity if I'm running sera. I would suspect that there is a memory over-write that is trashing sera (I notice that when I bring up the sera app after such a crash, that *all* stats for bytes transmitted etc. are zero... which suggests the app was trashed). IMO, this may prove to be a major bug (now that I've seen it on two distinct machines). ...but that is what beta feedback is for.
Whiteboard: [nsbeta2+][Will be minus on 6/15] [dogfood-] → [nsbeta2-] [dogfood-]
So installer is trashing memory? If this is happening on windows nt, then you have a problem Is installer a 16bit app? [is sera?]. Could you run purify on installer? Could we just abandon installer and do this the right way (tm)? Should this bug be nominated rtm or nsbeta3 or nsserarelnote
"SERA" is the netscape VPN client that runs on Windows and is used to traverse the Netscape firewall. I can reproduce this on two machines, but sadly, there have been no other reports of it :-/. Since it can't be reproduced, it is too hard to debug, and clearly a "low visibility" bug :-(. Bottom line: No way to get it pushed to beta3-plus or rtm-plus-plus. There are too many other highly visible and reproducible problems to tackle at this point. If we get beta feedback suggesting this problem, then we should get some folks working harder on analyzing my machines.
Unsetting missed milestones to aid triage queries.
Target Milestone: M17 → ---
fixed. we're using our own home brewn network lib now in the installer. SmartDownload has been retired. Let me know if you are still encountering this problem. If you still are, we can now fix it properly since we have source code.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Depends on: 66480
Resolution: --- → FIXED
vfy new network lib
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.