Open Bug 1182025 Opened 10 years ago Updated 6 years ago

Can't start Thunderbird or SeaMonkey offline using the -offline switch or the profile manager

Categories

(SeaMonkey :: MailNews: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: neil, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [regression:TB41])

Bug 1134596 broke offline startup in general but that's being fixed in bug 1179779. However it also changed the default value of the network.manage-offline-status preference to true, which means that offlineStartup.js tries to override the offline status set by the -offline switch or the profile manager. We can't make the -offline switch clear the manage offline status because that doesn't get set until later in startup, so the simplest workaround would appear to be to override the pref in mailnews.js unless someone has any better ideas?
My bad, the default value of network.manage-offline-status was changed in bug 654579.
Blocks: 654579
Keywords: regression
Whiteboard: [regression:TB41]
Version: unspecified → 41

Does this still fail?
And what about Bug 973314 - thunderbird -offline starts ONLINE (linux-only?) ?

I'm embarrased to say that, not remembering this bug report, I've sometimes asked users to start offline and they reply that it affected their situation (implying that offline worked)

Flags: needinfo?(wls220spring)

As far as I understand this bug has been fixed, or at least the issues are resolved in the latest version of Thunderbird.
I've checked Bug 973314 and updated it accordingly.

I can start Thunderbird in offline mode using the -offline switch.

SeaMonkey starts in online mode when using seamonkey -mail -offline, also when checking "Work offline" when starting with the Profile Manager.

Flags: needinfo?(wls220spring)

Thunderbird side of this ticket has been confirmed working. Passing it off to the SeaMonkey team for their bit.

Component: Networking → MailNews: General
Product: MailNews Core → SeaMonkey
Version: 41 → unspecified
You need to log in before you can comment on or make changes to this bug.