Bug 447364

Summary:	firefox starts in offline mode after reboot
Product:	[Fedora] Fedora	Reporter:	Randy Zagar <jrzagar>
Component:	NetworkManager	Assignee:	Gecko Maintainer <gecko-bugs-nobody>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	9	CC:	lauri.hahne, mcepl, nsoranzo, walters
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-06-02 12:14:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Randy Zagar 2008-05-19 17:31:19 UTC

Description of problem:
Firefox unable to browse web because "work offline" is checked.

Version-Release number of selected component (if applicable):
fedora 9 3.0-0.60

How reproducible:
always after a fresh boot

Steps to Reproduce:
1. boot system
2. login
3. open firefox
  
Actual results:
unable to open web pages due to "working offline"

Expected results:
open web pages normally?

Additional info:
This could be related to general Network Manager weirdness with respect to wired
networks.

Comment 1 LH 2008-06-01 20:40:22 UTC

I have this same problem. Firefox always defaults to offline mode. This could be
due to network manager thinking I'm offline as I use a static IP for wired
connection and NM doesn't understand this.

Comment 2 Nicola Soranzo 2008-06-02 09:22:48 UTC

(In reply to comment #1)
> I have this same problem. Firefox always defaults to offline mode. This could be
> due to network manager thinking I'm offline as I use a static IP for wired
> connection and NM doesn't understand this.

Yes, this is the diagnosis. Take a look at the upstream bug linked in this bug
report for more info.

Comment 3 Matěj Cepl 2008-06-02 12:14:37 UTC

Two things:
a) for the workaround, follow the advice of Dan Williams at
https://bugzilla.mozilla.org/show_bug.cgi?id=424626#c39
b) this is not firefox, but Network Manager bug -- firefox just does here what
it is supposed to do, IMHO.
c) I think it should be CLOSED/UPSTREAM, as it is being resolved upstream, and
possible fix will come to use as well.

If you disagree, please, reopen, but against NetworkManager.