Firefox in Hardy defaults "Offline"

[RLuck]

Open the terminal (Apllication-->accesories--->terminal) and type "gksudo gedit /etc/dbus-1/system.d/NetworkManager.conf". Then you replace the
<allow send_interface="org.freedesktop.NetworkManager"/> with <deny send_interface="org.freedesktop.NetworkManager"/> (there are three it the text). Then save the changes and reboot. This will not permit firefox (or pidgin) to communicate with network manager and the state will be always online in firefox...

SO Many Thanks for this post
I thought I would go nutz - thinking there must be some way in the preferences of Firefox.

Bob

[IggoOnTour]

i just registered to thank you! A LOT!

[asbesto]

To follow up (although no one will likely read this), I believe the correct way to disable offline mode in Firefox is:

1) Start Firefox
2) In the address bar, type about:config
3) Search for "offline"
4) Toggle (double-click) browser.cache.offline.enable to "false"

Yes, THIS is the correct mode! The other one imploded my network manager and I was not able to connect to any network anymore!

THANK YOU!

[Hobgoblin]

Open the terminal (Apllication-->accesories--->terminal) and type "gksudo gedit /etc/dbus-1/system.d/NetworkManager.conf". Then you replace the
<allow send_interface="org.freedesktop.NetworkManager"/> with <deny send_interface="org.freedesktop.NetworkManager"/> (there are three it the text). Then save the changes and reboot. This will not permit firefox (or pidgin) to communicate with network manager and the state will be always online in firefox...

This hosed the rest of my network connections, when I'm home I want to be able to use my wireless connection.

Changed toolkit.networkmanager.disable in Firefox to true and all is well.

[svc985]

Open the terminal (Apllication-->accesories--->terminal) and type "gksudo gedit /etc/dbus-1/system.d/NetworkManager.conf". Then you replace the
<allow send_interface="org.freedesktop.NetworkManager"/> with <deny send_interface="org.freedesktop.NetworkManager"/> (there are three it the text). Then save the changes and reboot. This will not permit firefox (or pidgin) to communicate with network manager and the state will be always online in firefox...

Thanks a lot Nikitas350 for the advice.

[SwordGreen]

Yeah, it works, Thank you very much.

[pistacoppu]

If you like how NetworkManager works, but you simply want to be able to use FireFox while not connected to a network (i.e. for web development, etc.), you can edit the following special configuration in FireFox (use about:config-- click on link for more info):

toolkit.networkmanager.disable

This will leave NetworkManager alone and let it do it's thing, but FireFox will still function in offline mode.

thank igray
that worked for me, i set the value to true, and firefox is no more offline by default, i have firefox 3.0.5 and ubu 8.10 .
That doesn't not interfere with network manager so your wifi will keep working well.
i use emesene that works anyway, so pidgin may still have problems

[SergeiFranco]

I use kubuntu and this behaviour is bloody stupid.
I don't understand the point of this, as clearly I don't want for browser to decide if I am connected or not.
Every time I reboot, I "loose" connection.
Is there a proper way to disable this stupidity in GTK apps, without affecting network manager operation?

[pratiks19]

open Firefox and type 'about:config' in the address bar, accept the promise, then find and set ....

toolkit.networkmanager.disable = true

it worked for me.

[lnx]

Open the terminal (Apllication-->accesories--->terminal) and type "gksudo gedit /etc/dbus-1/system.d/NetworkManager.conf". Then you replace the
<allow send_interface="org.freedesktop.NetworkManager"/> with <deny send_interface="org.freedesktop.NetworkManager"/> (there are three it the text). Then save the changes and reboot. This will not permit firefox (or pidgin) to communicate with network manager and the state will be always online in firefox...

I have four "allow send_interface=" in the sections:
<policy user="root">,
<policy user="haldaemon">,
<policy at_console="true">,
<policy context="default">

Shall I change all four instances?