firefox wont connect to net

[vadirajcs]

Binary package hint: firefox-3.0

Browser goes into offline mode thought the connectivity is high.

Experience many times but could not solve the problem.

Why do I feel browser is the problem?
1. Check the connection status - Up
2. Check ping response -> success, host lookup succeeds, dns resolution succeeds, ping returns with 100% success and 0% loss.
3. Check with other app that connect to net, pidgin -> login in to gtalk configured in pidgin -> success.

But browser is in offline mode.

Experienced in FireFox-3.5 also, same behavior.

Checked with firefox running on other Linux Distro, OpenSuSe 11 and OpenSuSe 11.2. Issue not seen.

Checked with firefox running on windows. Issue not seen.

Only seen with ubuntu 9.04

Cleared, caches, cookies and other offline data stored. Still same issue.

Proxy is not set, hence proxy is not the issue here.

Please let me know if you need any thing to address this.

Forced to use other browser due to this problem or sometimes even other linux, quite demotivating as the primary source to connect to net is a problem.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: fglrx
Package: firefox-3.0 3.0.8+nobinonly-0ubuntu3
ProcEnviron:
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.28-11-generic i686

[John Vivirito (gnomefreak)]

Assigned to the "firefox" package since all supported versions of Ubuntu will be going to a non version package as upstream is now doing.

[John Vivirito (gnomefreak)]

I think this is a duplicate of the offline mode bug its a master bug but i dont recall the number off hand

[John Vivirito (gnomefreak)]

Any chance this is related to or the same as bug #191889

[John Vivirito (gnomefreak)]

Are you able to reproduce using the latest firefox packages in the version of Ubuntu you are running? For example Jaunty latest firefox-3.0 is firefox-3.0.18 Jaunty has firefox 3.5.8 please update to these and please see if you can reproduce it again

[vadirajcs (vadiraj-cs)]

I'm not aware of other bug, but some more analysis revealed that
firefox is tightly coupled with networkManager.

If the connection is established through networkManager then firefox works fine. If same connection is established directly,
for example

set connection using ifconfig or establish connection using wvdial. Connection made through these tools are out of NetworkManager and connection status through network manager is offline. Such cases, firefox fails to connect.

Other tools, such as pidgin, or other browser(Chrome) works fine as they are not tightly coupled with networkManager.