Bug 613195 - firefox always starts in offline mode
Summary: firefox always starts in offline mode
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox   
(Show other bugs)
Version: 13
Hardware: All Linux
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-09 23:48 UTC by Joe Bayes
Modified: 2010-07-10 00:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-10 00:59:07 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Joe Bayes 2010-07-09 23:48:20 UTC
Description of problem:
Firefox always starts in offline mode, even when the network is working and it was in online mode when it was last used.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Put firefox in online mode
2. quit and restart firefox

Actual results:
"Firefox is currently in offline mode and cannot browse the web" appears in all tabs, and File->Work Offline is checked

Expected results:
Tabs should load whatever they were pointing to when I last quit firefox.

Additional info:
I suspect that this may have something to do with my having "Controlled by NetworkManager" unticked for eth0 in system-config-network. Is Firefox assuming that since there is no "managed" network connection, there must be no network connection at all?

Comment 1 Christopher Aillon 2010-07-10 00:59:07 UTC
Correct.  If you are not letting NetworkManager control your interface because of a failing in NetworkManager, please consider filing a bug against it so we can fix it.

If you don't wish to use NetworkManager at all, you should consider turning off the service completely, via either system-config-services or via chkconfig.

Alternatively, if you need to use NetworkManager for some interfaces, you might consider setting the following preference: toolkit.networkmanager.disable to true.

Note You need to log in before you can comment on or make changes to this bug.