Red Hat Bugzilla – Bug 481414
Firefox browser will start always in offline mode.
Last modified: 2018-04-11 09:05:49 EDT
Description of problem:
Somehow my Firefox does start always in offline mode. I've tried various methods to get rid of it, but still nothing has changed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start firefox;
2. Check "File->Work Offline"
"Work Offline" is being always set.
No constant offline mode operation by firefox browser.
about:config does not report as "browser.offline" config option being set by default, but as soon as I disable "Work Offline" mode, it will report "browser.offline user set boolean false". Despite that configuration option on next run of Firefox browser will just ignore it and start in offline mode anyway.
Firefox 3.0.5 always starts up in offline mode. I installed FC10 from FC8. The new version of Firefix 3.0.5 starts in offline mode, and always requires the user to click the File --> Work Offline selection in the pulldown window.
$ uname -a
Linux hp1.xnet.com 188.8.131.52-159.fc10.i686 #1 SMP Tue Dec 16 15:12:04 EST 2008 i686 i686 i386 GNU/Linux
The same thing happens with the email system. Evolution 2.24.2 always starts up in offline mode, and it will not remember the email account password. I always have to click File --> Work Online, and then the system asks for the email account password. Clicking the Remember Password checkbox has no effect.
It seems like the Firefox and Evolution offline/online startup issues may be related. By default, the Firefox and Evolution packages should start up in Online mode.
I upgraded to F10 from F9, but I recall that there was no "firefox offline" issue just after that upgrade. It took some firefox runs to develop it, but I may be wrong...
Still what should we do to get rid of that issue?
This bug is strange -- there used to be terrible problems on other distros (namely, Ubuntu) with interaction between Firefox and NetworkManager, but I have never seen it in Fedoraland, and it does work for me.
Do you use NetworkManager? What is the value of toolkit.networkmanager.disable value in about:config?
I don't know how to access the about:config information. How do I do that? My system uses a 56K modem. I did not have this problem when I was running FC8. Under FC7 and FC8 it was very reliable and Firefox and Evolution both always opened up in online mode. If there is anything that you would like me to try please let me know.
[channmw@hp1 ~]$ rpm -q NetworkManager
(In reply to comment #5)
> I don't know how to access the about:config information.
I am sorry -- just write it to the firefox URL box (where you normally have the current URL).
and in the moment when Firefox is offline although your network is up, can we get output of
Thanks a lot.
"toolkit.networkmanager.disable default boolean false"
[root@ragana ~]# /etc/init.d/NetworkManager status
NetworkManager (pid 2155) is running...
[root@ragana ~]# nm-tool
- Device: eth1 ----------------------------------------------------------------
HW Address: 00:23:54:5B:59:4E
Carrier Detect: yes
Speed: 100 Mb/s
Where does it take that I am disconnected? I am connected.
Is that a LAN driver issue?
If to set "toolkit.networkmanager.disable user set boolean true" then firefox does not start in offline mode.
(In reply to comment #10)
> - Device: eth1
> State: disconnected
> Where does it take that I am disconnected? I am connected.
> Is that a LAN driver issue?
> If to set "toolkit.networkmanager.disable user set boolean true" then firefox
> does not start in offline mode.
Yeah, OK, so this is really crystal clear duplicate of that upstream Mozilla bug (see External references for the link). Problem (or characteristic) is that NetworkManager is always “all or nothing” solution—either all your network connections are managed by it or none are. And if you try to go in the middle and use NM just for managing wireless networking (many people tried that) you get into unhappy state, where NM seems to be lying.
So, either use NetworkManager for everything (make sure that all ifcfg-* files for devices you use in /etc/sysconfig/network-scripts/ have line saying NM_CONTROLLED=yes), or check the appropriate checkbox in system-config-network), or if you want to manage network connections manually, make sure that configuration files in /etc/sysconfig/network-scripts/ are correct (either manually or via system-config-network) and run (as root)
chkconfig NetworkManager off
service NetworkManager stop
chkconfig network on
service network restart
That firefox setting (toolkit.networkmanager.disable) just switches off Firefox checking the network status from NetworkManager so you have to handle it manually (by switching File/Work Offline).
See the Mozilla bug for more thorough explanation.