Closed Bug 456880 Opened 16 years ago Closed 15 years ago

"Browser only" installation: network part corrupt?

Categories

(SeaMonkey :: Installer, defect)

SeaMonkey 1.1 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: bugzillus, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/20080829 SeaMonkey/1.1.12
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.17) Gecko/20080829 SeaMonkey/1.1.12

When installing SeaMonkey 1.1.12 and below in "browser only" mode, there seem to be errors in the network handling which are not present after installing the full package: The browser unintendedly changes from offline to online mode when plugging in a network cable.

Reproducible: Always

Steps to Reproduce:
1. Click on icon to toggle offline mode
2. Disconnect LAN cable or power off the switch or router
3. Connect LAN cable or power on swith or router

Actual Results:  
Within seconds, SeaMonkey switches back to online mode (icon displays online mode).

Expected Results:  
Nothing should happen. Toggling offline/online mode should be left to the user, not to availability of the network connection.

On machines with IBM/Lenovo Access Connections, SeaMonkey immediately toggles online mode when a new location is selected in Access Connections (which should not affect the browser).

Additionally, in about:config, the status of "network.online" does not correlate with the actual state: it always stays as "true", and when manually changed to "false", it stays as "false", no matter how the online status is changed by clicking on the offline icon.

I assume, the network part has been corrupted when trimming down the package for the "browser only" installation.

This is a duplicate of bug 436518, hopefully with a more precise description.
Installing SeaMonkey in "custom mode": If "Mail and News" is not selected, the bug is present. If "Mail and News" is selected, the bug is gone. So obviously there is some basic networking code available in the "Mail and News" package, but not in the basic browser package.
I'm moving this bug to the "Installer" component on the assumption that it means the installer isn't doing its job correctly when Mail&News isn't selected; however, I wonder if "Build Config" wouldn't be more appropriate (meaning some file or function is in some "mail" directory where it shouldn't be).

Since this bug is for Windows, and Windows is the only platform where installers are still being built even for trunk, it might be interesting to determine if trunk builds are also affected. (I can't test it: I'm on Linux.)
Assignee: nobody → installer
Component: General → Installer
QA Contact: general → xpi-packages
Version: unspecified → SeaMonkey 1.1 Branch
> it might be interesting to determine if trunk builds are also affected.

In seamonkey-2.0a2pre as of 2008-09-25, the bug seems gone, but it is always a "full" installation anyway: browser-only install option does not exist, and with custom installation, there is no option to not install the mail/news component.
I can confirm it with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081204 SeaMonkey/1.1.14

It isn't in trunk version.
Status: UNCONFIRMED → NEW
Ever confirmed: true
We will not do any larger changes to the 1.1.x code any more, it is in strict security and stability maintenance mode and anything that was OK to tolerate since the two years of 1.1.x being out now is acceptable for the rest of the lifetime of that series.
SeaMonkey 2.0 doesn't support installing without mailnews any more, so this is WONTFIX now.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
To everybody using the SM 1.1 branch and current or upcoming versions 1.1.15+ with "browser only" installation mode, this bug may still be a severe security issue (pretending offline mode while still being or silently going online), depending on the circumstances of use.

So I am not sure if the WONTFIX status is appropriate, since the SM 1.1 series is still active and will be for an unknown time, although there seems to be no activity to track the issue down for months now.

I am glad though that the bug appears to be gone in the SM 2 series.

A quick fix might be to make "browser only" mode unavailable in SM 1.1
You need to log in before you can comment on or make changes to this bug.