[MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online state for networks that are managed outside of network manager.

[chrismine]

Binary package hint: firefox-3.0

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"
Firefox 3.0b3
When I start firefox from the panel it always start in offline mode. I am connected via wireless to a network that is always on. When I want to browse I need to unclick "work offline"

Workaround 1: (since ffox 3.0.1) ->
 set toolkit.networkmanager.disable to false in about:config

Workaround 2: (make NM to be always online) ->
 add a non existing interface to /etc/network/interfaces, like:

iface eth1000 inet dhcp

[Jose Bernardo (bernardo-bandos)]

I can confirm this bug on kubuntu hardy beta (with latest upates 1 hour ago).

[juangaspar (be-webdeveloper-st)]

I have the same bug on Ubuntu Hardy 8.04 (with all updates)

[chrismine (chrisjan-botha)]

I also filed a bug for Evolution for the same behavior. As I had network-manager 0.7 installed Sebastien Bacher asked me to downgrade to the hardy version 0.6.5. The behavior does not occur any more. The bug for Evolution is #191901

[Alexander Sack (asac)]

this was related to network-manager 0.7 which was a preview version. closing the bug.

[Jose Bernardo (bernardo-bandos)]

Still happens here with network manager 0.6.5-0ubuntu17. All I need is to be using a dial up (CDMA) connection for firefox 3 beta 3 to always start in offline mode. I am using kubuntu hardy, network-manager-kde applet version 1:0.2ubuntu1-0ubuntu7

[Daniel Newman (dmnewman)]

Still happens here with network-manager 0.6.5-0ubuntu17 and a USB HSPDA modem (ppp0). However, apart from that problem there is also the fact that I run a web server on this machine, for access from this machine only. This offline mode startup means that firefox never looks for the localhost server - surely it should do this before looking for network access?

[Alexander Sack (asac)]

if its a bug, then its a network-manager one. keeping the task open for it.

[Alexander Sack (asac)]

how is your dial up connection setup? most likely network manager doesn't know anything about it? Can you please post your /etc/network/interfaces and tell me the exact steps you use to dial up.

[Jose Bernardo (bernardo-bandos)]

I do the dial up with the kde network applet, using the "Dial up connections" submenu (guessing at the wording, as here it shows in portuguese). I have a "zapp" script in /etc/ppp/peers and have setup /etc/ppp/pap-secrets.
I'm including my /etc/network/interfaces.

[Caroline Ford (secretlondon)]

I have the same issue and use wvdial to connect using my usb hsdpa modem. I use wvdial as I couldn't get network manager to work.

[Caroline Ford (secretlondon)]

I didn't have this problem using firefox 2. Using network manager shouldn't be compulsory - I'd love to remove it personally..

As this didn't happen using firefox 2 I think this is a bug in the way firefox 3 decides whether we are online or not. I suspect it's trying to be helpful but failing miserably.

[Jose Bernardo (bernardo-bandos)]

Yes, this didn't happen with firefox 2 for me too. But it does happen with konqueror - I have to do "dcop kded networkstatus setNetworkStatus NMNetwork 1" to get it to accept I am not offline.

[Daniel Newman (dmnewman)]

I think it's a firefox bug, not a network-manager one (although I agree network-manager doesn't handle dialup well). As I said earlier, I run a http server on the same machine I'm using firefox from. This has nothing to do with network-manager, but firefox still doesn't do the logical thing and look for a local server before jumping to offline mode.

[sfan (sfan)]

It's not a firefox bug, because the bug is also in evolution. The icon of the network-manager shows me that I'm not connected, but I am. I'm using hardy.

[Daniel Newman (dmnewman)]

This **is** a firefox bug. Firefox should be looking for a http server at its specified home page, either on its own machine or on the network, to decide whether or not to start offline. Even better, firefox should default to starting online and let those who need the oddities of a web browser without web access switch it to offline if they so require.

One of my machines is set with its default home page on its own http server (at localhost), and I find it quite illogical for it to tell me every time it is opened that it can't find the home page - the real problem is that it hasn't looked for it.

This is a firefox bug, as distinct from network-manager's inept handling of dial-up connections.

[dav2dev (dav2dev)]

as i understood it, firefox3 looks for d-bus messages to decide if it is online or offline. These messages are emitted by network-manager, so if nm is unable to recognize an active connection to the Internet, it will send messages that the computer is not connected, and firefox3 will open offline.
Firefox2 doesn't have this problem because firefox2 is much less integrated with linux(and d-bus,in this case).

P.s. sorry for my bad english :)

[Caroline Ford (secretlondon)]

Network manager does seem to respond when I make my ppp0 connection.

Mar 5 15:55:33 celery NetworkManager: <debug> [1204732533.426876]
nm_hal_device_added(): New device added (hal udi is
'/org/freedesktop/Hal/devices/net_computer_0').

And when I close wvdial:

Mar 5 15:53:58 celery NetworkManager: <debug> [1204732438.905809]
nm_hal_device_removed(): Device removed (hal udi is
'/org/freedesktop/Hal/devices/net_computer_0').

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

This is definitely a bug in Firefox. I agree with many of the other posters here. I should not have to rely on NewtorkManager to use Firefox. In fact, sometimes I completely disable NM and override /etc/network/interfaces. So, marking this as a bug in Firefox appears valid. Please don't mark it invalid. This is something that either needs to be turned off by default, as in Firefox 2, or have the algorithm fixed so that it properly detects that you have a network connection. If I drop to a terminal and ping 4.2.2.2 successfully, but Firefox's new algorithm sucks, that's no my fault. Don't try to start bundling this bug with NetworkManager...

[Paul Hannah (pkhannah)]

I'll add my support behind reverting to the 'don't switch to offline mode automatically' method -- very few people want the browser to operate in offline mode, it's potentially a problem for those who think it's online-mode while it's not, and it's very annoying for those who never use it and find themselves with a non-working browser and no idea why.

[Alexander Sack (asac)]

daniel newman, your suggestions are beyond the scope of this bug report. please file a separate bug against firefox-3.0 with ideas on how to make the offline state smarter.

Thanks,
 - Alexander

[Alexander Sack (asac)]

this bug focusses on the problem that network manager exposes "offline" as the current network state even though there is an upped ppp connection.

Can anyone confirm that this ppp feature works with the gnome applet at all?

[Sofa (alexschultze)]

I encounter the same problem with an different configuration. NM is set to "Networking Disabled". This causes FF to go into offline mode every start.

[fmichl (fmichl)]

Using a ISDN connection firefox 3 can't detect it and turns into the offline mode after starting up. I have to change the mode manually.

[mc44 (mc44)]

I don't see how it's a bug in network manager. I have network manager disabled and use /etc/network/interfaces directly to connect to the internet, I'm still online, but firefox assumes I'm not. Assuming network-manager accurately displays the networking status is the bug.

The original bug report (hence the scope of the bug, surely) is nothing to do with ppp but instead wireless connection...

[Paul Hannah (pkhannah)]

Ditto here.

NetworkManager isn't running and still Firefox starts up in offline
mode (note that it isn't the only app that is doing this now, Pidgin
is another example.)

On Mon, Mar 17, 2008 at 5:44 AM, mc44 <email address hidden> wrote:
> I don't see how it's a bug in network manager. I have network manager
> disabled and use /etc/network/interfaces directly to connect to the
> internet, I'm still online, but firefox assumes I'm not. Assuming
> network-manager accurately displays the networking status is the bug.
>
> The original bug report (hence the scope of the bug, surely) is nothing
> to do with ppp but instead wireless connection...
>
>
>
> --
> Firefox's new "Offline Mode" feature cannot properly detect when there is a valid network available for use in many circumstances
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Caroline Ford (secretlondon)]

Epiphany (and apparently evolution) also presume offline too. It's not
just a Firefox thing.

[Alexander Sack (asac)]

if you see this, please attach your /etc/network/interfaces configuration

[Caroline Ford (secretlondon)]

I've set up a serial interface in network tools and then unconfigured
it. Network manager now has "manual network configuration" and seems
to think I'm online all the time.

Interfaces is no different from before, however.

[ichudov (igor-chudov)]

I have this problem too. I have a "Sierra 597E mobile broadband card". I detect it at boot time via lsusb, and start pppd if I detect it. Works great for me. It did not work with NM. Which is fine. I am happy with what I have now (boot scripts and shell aliases).

HOWEVER:

Firefox 3 thinks that I am offline despite the obvious default route etc.

I basically would be happy if I could just turn OFF the offline mode forever. I do not really need it. If I am offline, I do not start Firefox.

[ManuPeng (mvieuxmaire)]

Not like I think it's a big surprise, but it's the same with the **amd64** release of Hardy with all updates. My computer is always connected to the internet using a AVM Fritz PCI card and pon/poff for ppp.
This bugs affects:
-Firefox 3.0 beta 4, although it didn't in 2.0
-Pidgin in Hardy and it didn't work in Gutsy either
-Evolution and it didn't work in Gutsy either

Only about a month left to fix this on time for the final release.

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

On Sat, Mar 22, 2008 at 2:29 AM, ManuPeng <email address hidden> wrote:
> Not like I think it's a big surprise, but it's the same with the **amd64** release of Hardy with all updates. My computer is always connected to the internet using a AVM Fritz PCI card and pon/poff for ppp.
> This bugs affects:
> -Firefox 3.0 beta 4, although it didn't in 2.0
> -Pidgin in Hardy and it didn't work in Gutsy either
> -Evolution and it didn't work in Gutsy either
>
> Only about a month left to fix this on time for the final release.

Agreed. THIS BUG IS A SHOWSTOPPER for a large portion of affected
users. This bug absolutely needs to be fixed or else Ubuntu 8.04 LTS
stands to be a very flawed release...
--
Kristian Erik Hermansen
--
"Only those who dare to fail greatly can ever achieve greatly."

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

SHOWSTOPPER

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

network-manager should NOT be affiliated with this Firefox issue.

[Bshanks2 (bshanks2)]

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b5pre) Gecko/2008032215 Minefield/3.0b5pre
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b5pre) Gecko/2008032215 Minefield/3.0b5pre

On my Debian system, I had the NetworkManager service running, however, my wired network interface was controlled manually (in my case, the relevant entry in /etc/network/interfaces was "iface eth1 inet static", which prevents NetworkManager from managing that interface). Therefore, when using the wired interface, I had network access, however, NetworkManager reports no network devices present (the commandline program nm-tool yielded:

"
NetworkManager Tool

State: disconnected

print_devices(): didn't get a reply from NetworkManager.
There are no available network devices.
").

This caused Firefox 3 to startup in Offline mode, which forced me to manually uncheck File->Work Offline at the beginning of each session.

As a workaround, I now disable the NetworkManager service before starting Firefox (now nm-tool reports
"
NetworkManager Tool

get_nm_state(): didn't get a reply from NetworkManager.

NetworkManager appears not to be running (could not get its state).
").

If NetworkManager intends that it is accurately reporting the "online" status of the computer (does it? or does it intend to only report the state of the connections that it is managing?), then I suppose that NetworkManager has a bug.

However, in any case, Firefox should have a config option that the user can use to tell Firefox not to query NetworkManager upon startup.

Reproducible: Always

Steps to Reproduce:
1. Install NetworkManager
2. Configure things so that NetworkManager does not control any of the active network interfaces (I believe you can do this by adding all of the active interfaces to /etc/network/interfaces, providing each of them with at least one option other than "auto" or "dhcp"). nm-tool should report state "disconnected", as described above.
3. Start Firefox. Observe that File->Work Offline is checked.
Actual Results:
File->Work Offline is checked

Expected Results:
I would expect that if I start Firefox when I am online (able to access remote web pages), and File->Work Offline was not checked at the end of my previous session, that File->Work Offline would not be checked upon startup

I have heard of other people having similar problems in slightly different circumstances (see https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/191889).

Since NetworkManager cannot currently be relied upon to accurately give the online status of the system, I am requesting an option that tells tell Firefox not to query NetworkManager upon startup. I could not find such an option at http://kb.mozillazine.org/Category:Preferences.

[ManuPeng (mvieuxmaire)]

I think, at least, there should be an option in the network manager to manually override it and set it to a fixed "online" state if you choose to. That way, we could set it to "online" once and for all and go on with our business...

That'd be a quick fix on time for the final release, should the responsible developer not have time for the real thing that's been bothering me/us since Gutsy. I mean, I spent an hour yesterday, waiting for an email in evolution, that a friend said he had sent me. Only to finally realize evolution was offline all that time and not fetching my emails. Hehe, there you go again, I've just realized I'm offline again with two emails in my outbox...

[Alexander Sack (asac)]

On Sat, Mar 15, 2008 at 07:50:39PM -0000, Sofa wrote:
> I encounter the same problem with an different configuration. NM is set
> to "Networking Disabled". This causes FF to go into offline mode every
> start.
>

Why are you online with networking disabled?

 - Alexander

[Alexander Sack (asac)]

On Sun, Mar 16, 2008 at 06:00:02PM -0000, fmichl wrote:
> Using a ISDN connection firefox 3 can't detect it and turns into the
> offline mode after starting up. I have to change the mode manually.
>

How exactly is your ISDN connection configured. please attach your
/etc/network/interfaces and your complete /var/log/syslog

 - Alexander

[Alexander Sack (asac)]

On Sun, Mar 16, 2008 at 07:44:34PM -0000, mc44 wrote:
> I don't see how it's a bug in network manager. I have network manager
> disabled and use /etc/network/interfaces directly to connect to the
> internet, I'm still online, but firefox assumes I'm not. Assuming
> network-manager accurately displays the networking status is the bug.

Please post your /etc/network/interfaces and your complete
/var/log/syslog taken _after_ you experienced this problem.

 - Alexander

[Alexander Sack (asac)]

On Tue, Mar 18, 2008 at 01:21:08AM -0000, ichudov wrote:
> I have this problem too. I have a "Sierra 597E mobile broadband card". I
> detect it at boot time via lsusb, and start pppd if I detect it. Works
> great for me. It did not work with NM. Which is fine. I am happy with
> what I have now (boot scripts and shell aliases).
>
> HOWEVER:
>
> Firefox 3 thinks that I am offline despite the obvious default route
> etc.
>
> I basically would be happy if I could just turn OFF the offline mode
> forever. I do not really need it. If I am offline, I do not start
> Firefox.
>

try to setup that ppp connection in /etc/network/interfaces. maybe you
can even use network manager to bring it up and down then.

 - Alexander

[Alexander Sack (asac)]

On Sat, Mar 22, 2008 at 09:29:32AM -0000, ManuPeng wrote:
> Not like I think it's a big surprise, but it's the same with the **amd64** release of Hardy with all updates. My computer is always connected to the internet using a AVM Fritz PCI card and pon/poff for ppp.
> This bugs affects:
> -Firefox 3.0 beta 4, although it didn't in 2.0
> -Pidgin in Hardy and it didn't work in Gutsy either
> -Evolution and it didn't work in Gutsy either
>
> Only about a month left to fix this on time for the final release.
>

Please try to configure your ppp connection in /etc/network/interfaces
or System->Administration->Network.

 - Alexander

[Alexander Sack (asac)]

On Sat, Mar 22, 2008 at 04:24:03PM -0000, Kristian Erik Hermansen wrote:
> network-manager should NOT be affiliated with this Firefox issue.

can you please NOT change bug states unless you know the technical
details? For now this is

 affects ubuntu/firefox-3.0
 status invalid
 affects ubuntu/network-manager
 status incomplete

Thanks,

 - Alexander

[Paul Hannah (pkhannah)]

I just looked in System->Administration->Network -- I can't see how I
can use that as my connection script requires the inclusion of a pin.

On Tue, Mar 25, 2008 at 2:28 PM, Alexander Sack <email address hidden> wrote:
> On Sat, Mar 22, 2008 at 09:29:32AM -0000, ManuPeng wrote:
> > Not like I think it's a big surprise, but it's the same with the **amd64** release of Hardy with all updates. My computer is always connected to the internet using a AVM Fritz PCI card and pon/poff for ppp.
> > This bugs affects:
> > -Firefox 3.0 beta 4, although it didn't in 2.0
> > -Pidgin in Hardy and it didn't work in Gutsy either
> > -Evolution and it didn't work in Gutsy either
> >
> > Only about a month left to fix this on time for the final release.
> >
>
> Please try to configure your ppp connection in /etc/network/interfaces
> or System->Administration->Network.
>
> - Alexander
>
>
>
> --
> Firefox's new "Offline Mode" feature cannot properly detect when there is a valid network available for use in many circumstances
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

On Mon, Mar 24, 2008 at 9:31 PM, Alexander Sack <email address hidden> wrote:
> can you please NOT change bug states unless you know the technical
> details? For now this is

Dude, even if there is buggy code in NetworkManager which causes the
technical issue, it still means this is a functional defect in Firefox
for *relying* on NetworkManager! What don't you get? I think that
many people have voted here to log this as a Firefox issue and not a
NetworkManager issue. I can prove that this is a Firefox bug.

khermans@khermans-laptop:~$ ping 4.2.2.2 -c 1
PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
64 bytes from 4.2.2.2: icmp_seq=1 ttl=243 time=285 ms

--- 4.2.2.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 285.857/285.857/285.857/0.000 ms

Yet, when I launch Firefox, it starts in offline mode. Also, there is
a point at which NetworkManager can become stuck with the two green
balls lit up and the circling blue comet spinning around, but NM never
actually becomes into the "Connection Established" state. I will
attach a screenshot of exactly this scenario. This is a functional
defect in FIREFOX for relying on NetworkManager unless you can
convince us otherwise or link us to the appropriate mailing list
discussion or documentation which describes this as a "Known
Condition" or "Accepted Defect". Dude, this is just plain moronic
though if you ask me. Read my lips. You are going to piss a lot of
Ubuntu desktop users off with this issue. I'm seriously about to
switch back to Debian with no GUI and lynx. Watch the Firefox heads
roll when 8.04 LTS final hits the internets...
--
Kristian Erik Hermansen
--
"Clever ones don't want the future told. They make it."

[Jose Bernardo (bernardo-bandos)]

My ppp connection is configured in /etc/network/interfaces (check the copy above, on comment 9), and I dial using kde network manager applet. Still, it makes no difference - most times when I am using ppp firefox 3 starts in offline mode.

[Mozilla (mozilla)]

confirmed
I would propose to add a (hidden) pref to disable NM status use.
(The openSUSE Firefox 2.x has that feature but the FF3 code is different so we need a new patch)

[Marcia-mozilla (marcia-mozilla)]

This sounds like a dupe of a bug I filed where I noticed in a Linux VM I was starting up in Offline mode, Bug 419736.

[Mozilla (mozilla)]

It's most probably a bug. Feel free to dupe that one but the summary of the other one is not really helpful ;-)

It's known that if NetworkManager is running but is not actually handling every online connection it tells Firefox that it is offline.

[Mozilla (mozilla)]

(In reply to comment #3)
> It's most probably a bug.
                       ^^^ dupe that is.

[Marcia-mozilla (marcia-mozilla)]

*** Bug 419736 has been marked as a duplicate of this bug. ***

[Swistak (swistakers)]

I agree that this bug is very annoying. It should be fixed before hardy release.

[Alexander Sack (asac)]

On Tue, Mar 25, 2008 at 05:49:39AM -0000, Kristian Erik Hermansen wrote:
> for *relying* on NetworkManager! What don't you get? I think that
> many people have voted here to log this as a Firefox issue and not a
> NetworkManager issue. I can prove that this is a Firefox bug.

Its mostly you who still claims this. If you want a firefox issue,
open a new bug. this one deals with the fact that network manager
could do better pretending that nm is online.

>
> Yet, when I launch Firefox, it starts in offline mode. Also, there is
> a point at which NetworkManager can become stuck with the two green
> balls lit up and the circling blue comet spinning around, but NM never

If you have a problem with NM spinning all the time, open a
network-manager bug too. All your comments just don't belong
here. So please contribute constructively, for instance posting the
information i asked for.

 - Alexander

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

I posted output from the ping command, a screenshot showing the
nmapplet issue, and ff starting in offline mode. If I haven't proved
the bug yet, then I guess I will just give up trying. I asked you to
post a link to the technical discussion here, but you have failed to
do that. So, why don't you follow up and show some constructive data
for this bug...

On 3/26/08, Alexander Sack <email address hidden> wrote:
> On Tue, Mar 25, 2008 at 05:49:39AM -0000, Kristian Erik Hermansen wrote:
> > for *relying* on NetworkManager! What don't you get? I think that
> > many people have voted here to log this as a Firefox issue and not a
> > NetworkManager issue. I can prove that this is a Firefox bug.
>
> Its mostly you who still claims this. If you want a firefox issue,
> open a new bug. this one deals with the fact that network manager
> could do better pretending that nm is online.
>
> >
> > Yet, when I launch Firefox, it starts in offline mode. Also, there is
> > a point at which NetworkManager can become stuck with the two green
> > balls lit up and the circling blue comet spinning around, but NM never
>
> If you have a problem with NM spinning all the time, open a
> network-manager bug too. All your comments just don't belong
> here. So please contribute constructively, for instance posting the
> information i asked for.
>
>
> - Alexander
>
> --
> Firefox's new "Offline Mode" feature cannot properly detect when there is a
> valid network available for use in many circumstances
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Sent from Gmail for mobile | mobile.google.com

Kristian Erik Hermansen
--
"Clever ones don't want the future told. They make it."

[Ben (benc)]

Another "me too". I connect via a GPRS Bluetooth modem, so I have no hope of configuring it via the GUI to placate NetworkManager.

It's important to note that this ruins `prism` completely. When a Prism application is started it checks whether you're online using this method, and when it finds that you're not, suggests unchecking File > Work Offline. Of course, Prism applications don't have a File menu...

Is there any kind of workaround available? I will quite happily wait patiently for a proper fix, but in the meantime I'd like to be able to work online. :-)

[Dan Williams (dcbw)]

Each distro handles ignored devices differently. Even though NM would know the MAC address of the device that it is told to ignore, there's no way NM could know whether or not that device is up and active, precisely because you've told NetworkManager to ignore that device.

NM 0.7 will help this because it will work for a lot more users (static IP, network before login, etc).

However, if you are making NetworkManager ignore certain devices, then you cannot expect NetworkManager to know anything about those devices, much less whether that device is active and has an IP address and is therefore online. I'd suggest turning off NetworkManager in that case, and then FF should just thing you're online.

[Caillon (caillon)]

Yeah, what Dan said. If you're going to tweak the default settings to be outside of the use case, there's going to be more than simply Firefox which is going to be affected. Other system services are moving to use NM to determine on/off state, and you're expected to disable NM if you aren't going to use it for every device.

I'd recommend a release note reminding people that they should disable the NetworkManager service if they are managing network connections by hand.

[Mozilla (mozilla)]

Basically I agree and with NM 0.7 that's probably almost no issue anymore.
But earlier versions of NM weren't able to manage 3G and all other dialup things.
So people had NM running for their WiFi/cable devices but used other tools to connect with their 3G devices for example. That was a major use case the last two years.
So inventing a hidden pref wouldn't harm and wouldn't be too hard as well.
(I'm not talking about ignoring special devices but just disabling NM status support for special cases)

[Dtownsend (dtownsend)]

I'm seeing probably a person a day find their way to IRC and complain that their firefox starts in offline. Myself I could not figure out how to make ubuntu use the networkmanager which it installs by default work so I had to uninstall it. This is somewhat unintuitive and I think we should do something about this for Firefox 3.

[ManuPeng (mvieuxmaire)]

Actually, I'm gonna have to agree with Kristian Erik after all.
You see, at first, since Pidgin, Evolution and Firefox 3 were concerned by that offline problem, leading all three applications to start offline on my (and others) PC, I thought a central piece of code had to be responsible, the network manager. But now, I realize that other applications take a more easy-going approach, like the weather applet, it never bothers me with online or offline, it just tries to access the URL where it gets its data from, and done, should no connection exists, it displays "- -".
Google Earth? Same thing, it doesn't ask the network manager for its piece of mind, it attempts to connect to the google earth stream-server and done!

So I tend to agree with Kristian Erik, an application shouldn't rely on the network manager only, especially if it fails at detecting some connection types. It's not much, but it gets VERY annoying to have to click 2-3 extra times every time you start some applications, or even 8 times or so with Pidgin, because I have to disable my yahoo, AIM and MSN account, before re-enabling them in order for Pidgin to override the offline mode and connect to the respective servers. The clicking has an annoying cumulative effect.

[koresho (koresho-seshra)]

I have this issue as well. I am using GnomePPP on Ubuntu Hardy, and every time that I try to start Firefox 3b4 it is offline-mode checked.
Suggestion: have it ping a web server. Handle offline like firefox 2.

[Dan Williams (dcbw)]

I get people all the time asking "Why doesn't NetworkManager see my network device?". Every single time it's because that person is using Ubuntu and they have configured that device in "Manual" mode, which is an Ubuntu specific hack and causes me no end of trouble upstream.

I can't help what stupid choices distributions make. The NetworkManager in Fedora, SUSE, and other distros just works when used with FF3. If this is worked around, you understand you're working around _Ubuntu_, not NetworkManager.

[Dtownsend (dtownsend)]

I couldn't get ubuntu to connect in the networkmanager mode (whatever it is), and I have also heard complaints from Fedora users.

Sure we might be doing something to work around a problem in a distribution. If that distribution represents a large enough portion of the user base I think that is a reasonable things to do, and I know Mozilla have done similar things in the past (disabling IPv6 where certain platforms were broken). I do not know what the figures are, I can only say I am seeing this issue crop up frequently.

[Dan Williams (dcbw)]

Part of that is because Ubuntu ships many quite horrible-quality drivers that simply don't work with wpa_supplicant and NM, because they don't support WEXT properly. I laud their efforts to make as much hardware work as possible, but unfortunately the _quality_ of that support for many drivers just sucks.

If you're using out-of-kernel drivers (ubuntu has in the past had 4 different _stacks_ in their kernel, including net80211, linux-wlan-ng, vendor drivers, etc not to mention shipping ndiswrapper) then there's not much that _anyone_ can do to guarantee the quality of those drivers, and every time somebody asks why their card doesn't work when it uses an out-of-kernel driver, I can usually find 3 or 4 major errors in the driver's WEXT conformance.

Yes, Ubuntu has a large user base and it's probably something FF has to work around given that. But many of the reasons that NM doesn't work for people using Ubuntu are specifically because of bad choices Ubuntu has made when packaging NetworkManager (often for ndiswrapper and madwifi) and when stuffing bad quality drivers into their kernel packages.

Doesn't help the users of FF though since you obviously can't blame them for the distro they use.

[Kai Engert (kaie)]

I run into this problem on Fedora, when I'm in a hotel with no ethernet and no wireless, and use kppp to connect to the internet using a mobile phone. Maybe I should be using some other software for doing the PPP connection, that network manager is aware of? However, that would require that I migrate all the configuration information for various access points into another software.

Am I expected to stop the NetworkManager service when I use kppp?

[Simone Tolotti (simontol)]

I've found how to bypass the offline issue.
Configure the wired connection disabling "roaming mode" and select static IP, you could use IP adress like 192.168.0.1 and netmask 255.255.255.0.
After reboot NM is switched to online and you can use all the applications that take care of nm status (FF-3,pidgin,evolution, etc.).
Unfortunately after disabling roaming mode the connect/disconnect menu items in nm-applet disappears.
You could manage your dialup connection (if you have one) with "sudo pon ppp0" and "sudo poff".

[Simone Tolotti (simontol)]

Please mark this as confirmed and at a higher priority 'cause it's a blocker for everyone who has a dial-up or a "not always-on" connection.
Until NM and nm-applet doesn't take care of connected interfaces other than eth or wlan it's a big problem.

[Ryan Waldroop (ryan.waldroop)]

I found this bug while searching for a way to disable offline mode in about:config in Firefox. Now I realize that Pidgin does the same, and I have to manually re-enable all 9 of my accounts.

Is there an easy hack for network manager to always report as online? Simone Tolotti's looks like it will work, but I use WIFI about half the time, and my cellular bluetooth (bnep0) connection the other half of the time, so changing my network configuration all the time seems kinda ridiculous.

Of course, it looks like the best thing to do would be to have effected programs ping a site first, rather than checking the NM.

[Guimenez (guimenez)]

No dought that is NM

I use vodafone mobile connect card driver for linux and its the same thing. I think that the NM need to find if theres any open connection like PPP, if so NM need to says that is connect.

That its the main problem

[Lealcy B. Junior (lealcy)]

I'm using a manually configured network connection (trough my local LAN). I've fully connectivity with Internet but Firefox 3 beta 4 continues start in "Offline mode".

I'd confirm this bug.

[Vinicius Jacques (blackmoon)]

I have this bug on Firefox 3 Beta 4. I'm using a full updated Ubuntu Hardy Heron Beta.

[HelloWorld (tue-gmx)]

I use firefox 3b4 with kubuntu 8.04 -> same problem, use wvdial for dialup network (hsdpa over usb-modem mc950d)

firefox always starts offline, but when I start firefox with -p and make a flag by "start work offline", firefox starts online

[Dan Taylor (slash)]

I can also confirm this bug in Hardy 8.04 Beta.
Affects pidgin, and firefox

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

The ubuntu firefox people still won't admit that this is a bug. Mark
my words. It will be the scar on the face of hardy and be present for
the next 3 years, pissing many people off and perhaps convincing some
of them that linux is again not ready for the desktop. This bug
requires high priority attention...

On 4/4/08, Dan Taylor Jr. <email address hidden> wrote:
> I can also confirm this bug in Hardy 8.04 Beta.
> Affects pidgin, and firefox
>
> --
> Firefox's new "Offline Mode" feature cannot properly detect when there is a
> valid network available for use in many circumstances
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Sent from Gmail for mobile | mobile.google.com

Kristian Erik Hermansen
--
"Clever ones don't want the future told. They make it."

[ManuPeng (mvieuxmaire)]

It apparently just got fixed via the network manager...

I just got a monster update going, of about 200MB, and although the updated kernel just won't boot, the network manager got out of my way when using the older kernel. It's either a new network manager, now 0.6.6 or a new capiutils and such package, no idea, but it does work now.
Pidgin, Evolution and Firefox 3 finally all start in online mode and man, isn't that great now that it does :-)

Now to complain about that new buggy 64 bit kernel, version 2.6.24-15.

Try and update everything, I'd like to know if it also works for you guys now.

Manu

[ManuPeng (mvieuxmaire)]

I confirm, it is working now. Did something get updated? Or was I too dumb to make it work?
With kernel 2.6.24-12 and network-manager 0.6.6, this is what I did for a ppp connection using ppp0:
1) Start System->Administration->Network
2) Unlock, switch to root priviledges
3) Start by editing the properties of a "Wired connection"
4) Connection Settings, change "Configuration" to "Automatic configuration (DHCP)"
5) Click Ok
6) Activate/Check the "Wireless connection"
7) I think it's called "Dialup", the one with a blue phone on top of a modem. The name seems to change after it's been configured. Anyways, hit the properties for that.
8) In the "General" tab, check "Enable this connection"
9) Select "Connection type" is "PPPoE"
10) Fill out "Account data" with the data you received from your ISP
11) In the "Modem" tab, select "Ethernet interface" is "eth0"
12) In the "Options" tab, check both "Set modem as default route" and "Use the internet service provider nameservers"
13) Click Ok
14) Activate/Check the "Point to point connection" entry in the main dialog underneath "Wired connection". Both should be checked now.

At this point, I close and the network manager applet shows I'm now online. Pidgin, Evolution, Firefox, everything just starts in online mode.
Now, this is what works for me and hopefully works for all ppp users out there, think AVM cards and such. I'm not saying I have the workaround of a lifetime, but this is how I got it working and I'm sharing it here for you to try and use it as a starting point.

Hope that helps!
Manu

[Ryan Waldroop (ryan.waldroop)]

This still doesn't fix the problem if Network Manager doesn't recognize your
connection. I followed the directions at
http://ubuntuforums.org/showthread.php?t=598890 to set up a bluetooth PAN
connection to my WM6 phone. Recently, Hardy released a new bluetooth and
bluez-utils package that did not include the "pand" command, which I need to
set up my bluetooth connection (bnep0). I'm running my bluetooth stuff from
another repository as described in
https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/192043

I am currently connected to the internet, yet Firefox, Pidgin, etc. still
reports as offline because of NM.

[ichudov (igor-chudov)]

I agree totally. I had to downgrade to FF2 because of this. This is BAD BAD BAD. At the very least, there ought to be an option disabling offline mode, or being able to set "online" flag for NetworkManager.

i

[ManuPeng (mvieuxmaire)]

Yeah, that was also my suggestion in a previous post on 2008-03-23, there should be a way to force the network manager to tell everyone it's online, even if it isn't. I mean, my problem is somehow fixed, but I know your pain, I was pissed off during the past weeks.

I usually have way over 20 tabs opened in Firefox, I'm a tab-person :-) and it crashed onc,e which is OK because it's still a beta. The problem is, when it restarted, it of course did so in offline mode. Sure it remembered my 20+ tabs, but it failed to reload them because Firefox thought it was offline. Ensued a fun time of setting Firefox to "online mode" and clicking each and every single tab and reloading each and every single one of them.
It was good, we should do that more often, not frustrating at all :-)

[jarda (hercikj)]

Maybe I found solution to this problem:
http://www.suseforums.net/index.php?s=05dc21d4abc10176b96866dc7a1497a3&showtopic=43981&pid=221062&mode=threaded&show=&st=&#entry221062

"Knetworkmanager is still a little bit funky when it comes to accurately co-ordinating KDE's network online/offline status.
If you want, you could also disable the Network Status Daemon in Personal Settings -> KDE Components -> Service Manager. This will keep KDE from tracking network interface status, and hence all KDE apps will assume an active connection, rather than querying for online/offline status."

[Simone Tolotti (simontol)]

The bug title should be changed 'cause it's not related to Firefox.
I've seen that the bug is still in "incomplete" status, what kind of info the developers needs?
Clearly the problem is that NetworkManager doesn't take care of connected interfaces.
If you have a "wired" card (ethernet) you should disable the "roaming mode" for it and enable static IP or DHCP.
After this NM think that the card is connected and stays online.
Otherwise if you keep wired connection in roaming mode you can manage other interfaces (ppp0 in my case) but even if connected NM stays in offline mode due to the fact that the wired one is offline.

@jarda: Your "trick" only works in KDE and not for all.

[Dtownsend (dtownsend)]

*** Bug 427501 has been marked as a duplicate of this bug. ***

[Konrad Paumann (kopa)]

I'm affected by this bug too. It is really annoying and may be a real pain in the ass for the average user. In Europe (especially here in Austria) internet connection with GPRS/UMTS becomes quite ubiquitous. As long as NetworkManager doesn't manage ppp connections reliably it isn't wise to let it control online status of whole system.
I read NetworkManager 0.7 should bring some enhancements in that area. Why is 0.6.x in Hardy? Fedora 9 will ship 0.7?!
For the moment (until NM 0.7) it may be better for applications (Firefox, Pidgin, etc.) to not rely on the dbus online-offline status controlled by NM.
If a developer needs more information I would be happy to provide it.

[shafin (mahdee-jameel)]

I am also having this problem after upgrading to Hardy.
So many people are having this problem,there must be a fix somewhere.

I use a EDGE modem to connect to the ineternet. PIDGIN always started in offline mode,even in Gutsy,but I have not thought about it that way,I just reconnected every time pidgin started.

However,there is a very important piece of inforation: When I used firefox 3 in Gutsy,it didnt have this problem,only after upgrading to Hardy,the problem with firefox started, so it probably is related to some hardy upgrade.

Oh,and BTW,is there any toolbar button to get FF out of offline mode?then I'd save me one extra click each time.

[Beltzner (beltzner)]

As I'm understanding things, this issue won't hit even a majority of Ubuntu or Fedora users, as they have to be doing pretty special things to their network configurations. Is there a workaround that we can relnote?

[shafin (mahdee-jameel)]

Finally got over it!!!!
I disabled roaming mode for wired connections from the Network manager and then enabled automatic configuration(DHCP) option.

Now firefox starts in online mode.

[Ryan Waldroop (ryan.waldroop)]

Awesome! Thanks for that post Mahdee Jameel!

I just went through quite a few updates, and now bnep0 and pan0 are showing up in network manager. Changing these from roaming mode to dhcp appears to have fixed my problem, both for Firefox and Pidgin, and with minimal configuration effort. When I want to use WiFi, I simply Enable Wireless Networking, and when I want to use my cell phone over bluetooth, I disable Wireless, and NM assumes I'm connected!

Thanks so much to the Ubuntu team and everyone who has helped with this!

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

On Mon, Apr 7, 2008 at 12:37 PM, Ryan Waldroop <email address hidden> wrote:
> I just went through quite a few updates, and now bnep0 and pan0 are
> showing up in network manager. Changing these from roaming mode to dhcp
> appears to have fixed my problem, both for Firefox and Pidgin, and with
> minimal configuration effort. When I want to use WiFi, I simply Enable
> Wireless Networking, and when I want to use my cell phone over
> bluetooth, I disable Wireless, and NM assumes I'm connected!
>
> Thanks so much to the Ubuntu team and everyone who has helped with this!

The problem for most people is that dynamic addressing via DHCP may
not be a "solution" for this bug...
--
Kristian Erik Hermansen
--
"Clever ones don't want the future told. They make it."

[Vinicius Jacques (blackmoon)]

Thanks for that post Mahdee Jameel! [2]

Now Firefox is fixed.

[Ryan Waldroop (ryan.waldroop)]

@Kristian: true, DHCP may not be a solution, but you could also set a static IP, or set up DHCP for one of your little used connections, or maybe you could create a new connection.

If none of those work, it may be best to create a location profile in Network Manager, though this would require changing the Location bar in Network Manager whenever you switched from phone to WiFi.

[Dtownsend (dtownsend)]

(In reply to comment #15)
> As I'm understanding things, this issue won't hit even a majority of Ubuntu or
> Fedora users, as they have to be doing pretty special things to their network
> configurations. Is there a workaround that we can relnote?

The only workaround I could find was to uninstall the NetworkManager.

[Darryl Moore (darryl-moores)]

I found this issue only appears with my most recent kernel upgrade. 2.6.24-15 causes firefox to misbehave this way as well as killing my sound drivers and HAL. When I reboot under 2.6.24-14 everything works great. I think this latest kernel is really really buggy.

[vince (vince06fr)]

I have this on the computer bug from my father and I do not use "NetworkManager" the connection is done automatically without the support of "network manager" so i think it's a firefox bug...
Usb modem sagem fast 800 installed using the forum french (http://doc.ubuntu-fr.org/modem_sagem_fast_800)
last version of Hardy Heron with the 2.6.24-16-generic kernel

[frenchy82 (cartes)]

Hello,

The same thing here
I'm using Ubuntu 7.10 with sagem Fast 800

Firefox 3 allways start with offline mode.
 I've nether had any problem with firefox 2

[ld (ld-dubois)]

Hi,

In my case, I've got problem with nm-applet which cause problem in firefox.

And in fact, it was :
saa7134 which cause problem in hal which cause problem in network, and next firefox go offline.

I blacklist saa7134 like this :
 echo 'blacklist saa7134' | sudo tee -a /etc/modprobe.d/blacklist

restart, and no more problem ( hal, network, firefox )

Laurent

[Darryl Moore (darryl-moores)]

Yes, I found the same issue with saa7134 here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/214474

I think these are both the same bug

[Russ Dill (russ-dill)]

Please put some option somewhere in firefox3 to ignore dbus online/offline mode. I use network manager to connect to my dialup connection, but in 0.6.6, it seems to be a second class citizen. It connects, but network manager ignores it from a "connected to the internet standpoint. The dialup support in 0.6.6 is rudementary.

If hardy isn't going to ship with network manager 0.7.0, then provide the option not to trust network manager.

[Oleksii Balinskyi (abalinskiy)]

Allright, I guess people who have DHCP address have solved the problem. But what if I have static IP address?

[Ryan Waldroop (ryan.waldroop)]

If you have a static IP address, then simply set it using network manager the same way I described above.

[Simone Tolotti (simontol)]

Setting up a wired interface with dhcp or static IP is simply a workaround.
The problem is that NM don't see active interfaces like ppp0.
I hope that someone here will listen to my prayers and will mark this bug as Confirmed -> In progress -> Fix released.

[qoiwejqioejqio (qioeujqioejqioe-deactivatedaccount)]

I can confirm this bug on hardy RC, using a pppoe connection. Network-manager says "No network connection" and I BELIEVE that this causes firefox to automatically switch to offline mode.

[qoiwejqioejqio (qioeujqioejqioe-deactivatedaccount)]

Yeah, just as expected, when i 'apt-get remove network-manager' firefox started with offline mode switched off.

[Jens-Christian (beauman)]

@ManuPeng: Thanxs for your post, it worked for me: firefox and evolution start online!! -beauman-

[Alexandre Fiori (fiorix)]

please check #220497

[Stas Sușcov (sushkov)]

The bug persists in official release.
I'm having a speedtouch modem from my ISP for connecting to the web, and more than this, after I install speedtouch-gn package, it also crashes my nm when I'm trying to edit my network interfaces...

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

I knew that this bug would continue to be a problem. A possible
solution may perhaps be to add asac's ppa repository to your apt
sources and upgrade to network-manager 0.7. Give is a try...

On 4/26/08, Stanislav Sushkov <email address hidden> wrote:
> The bug persists in official release.
> I'm having a speedtouch modem from my ISP for connecting to the web, and
> more than this, after I install speedtouch-gn package, it also crashes my nm
> when I'm trying to edit my network interfaces...
>
> --
> Firefox's new "Offline Mode" feature cannot properly detect when there is a
> valid network available for use in many circumstances
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Sent from Gmail for mobile | mobile.google.com

Kristian Erik Hermansen
--
"Clever ones don't want the future told. They make it."

[Sia Neriman (sia-neriman)]

i use FF3 with Hardy released and is standard Workoffline mode.
##i use Hwawei modem to internet connect with Vodafone driver card for linux.
is a firefox3 """BUG" because the epiphany and ff2 worked perfect.

best regards

[Indicava (indicava)]

I am running into this with Hardy final release, FF3b5 and NM 0.6.6u5 when using a Kyocera kpc650 modem.

The only info I can add to this discussion is when I ran into this issue with Evolution, changing it to on-line mode in the file menu, wouldn't fix it, it showed the connected icon at the icon but wouldn't refresh my exchange connection.

That is probably an Evolution bug, but in my opinion it should contribute to the urgency of fixing this. The workaround described above works, but it annoys for so many reasons, even if just for the fact that the tray applet now shows no indication if my wired interface is plugged in or not.

[r0bb3d (r0bb3d)]

Hi,

I don't use network manager at all, disabled it and I have a custom script edit the /etc/network/interfaces when needed and have it restart networking.

This is a conscious choice because of many different networks I connect to which don't support dhcp and I have all settings for these networks pre-configured in this little script.

So I think it's very strange and just wrong for Firefox to assume everyone uses network manager. Please Firefox developpers, just add an option somewhere to force Firefox in online mode every time it starts. Offline mode is completely useless to me and this is so annoying im really tempted to switch browsers or downgrade to old Firefox.

Im running Ubuntu Hardy 8.04 with all updates and FF 3.0 beta 5

Thanks!

[robert shearer (bdaggg)]

I have the offline default problem using FF3.0 beta 5 and Kppp in Hardy so installed FF2.
FF2 works fine but get this... if I close FF2 after using it online and then open FF3/5 it connects as it should and does not default to offline. If I then close it and reopen it it defaults to offline.

[Brian Cardarella (bcardarella)]

I am currently using a Frankling Wireless CDU-680 broadband mobile card with Hardy x86 32-bit. FF default to "Work Offline" despite the fact that my computer is clearly "online". I establish a ppp connection with wvdial. It seems some genius at Ubuntu tied FF directly into Network Manager. Thanks alot whoever you are. Please fix.

[Guildofghostwriters (guildofghostwriters)]

I had already uninstalled network manager prior to noticing this bug because it didn't manage my wireless dongle well, and am using RutilT wlan manager but still get this bug so it's not restricted to NM.

[flexR (partner55105605)]

after updating to 2.6.24-17-generic (and recompiling the rt73 wireless drivers) this annoying situation returned.
More important: FF doesn't remember the settings, so after reopening FF, it is set 'work offline' again, even if there is another FF window still open.

[flexR (partner55105605)]

 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-

removing Network-manager solves the problem.

(apt-get remove network-manager)

[r0bb3d (r0bb3d)]

That indeed is the magic solution, tnx flexR! I feel stupid somehow for not having tried that :-) Anyway, happy time!

[Kim Alvefur (zash)]

If this is a bug in firefox, then where is the bug for network-manager? Since nm wont consider the computer online when connected with modem there must be a bug there.

[polyvotis (polyvotis)]

I confirm that the problem persists. I am using wvdial and firefox always starts offline even when I am connected. Even if this is a bug in NetworkManager, it is also a bug in Firefox and I can't see how you can deny it - why should Firefox depend on nm to run?

I also want to ask the following question: Suppose we didn't have this problem and firefox could see when we are online. Suppose we started firefox while being offline but then connected to the network. Would firefox automatically switch to `online' mode? If not, this is very inconvenient because many times you may happen to open firefox forgetting that you're not connected, and connect afterwards. Why would you have to manually tell firefox to go online then? I think there should be an option that firefox always starts online.

[bharathy (avilayabharathy)]

Hardy Heron 32 bit fully updated on Acer 5920.

Problem persists.

[bharathy (avilayabharathy)]

Network manager 0.6.6

[bharathy (avilayabharathy)]

Observation: If I boot the laptop and connect wireless Firefox starts in off-line mode. If I switch off the wireless and reboot and connect via LAN Firefox starts in on-line mode.

[Sokraates (sokraates)]

This is deffinitely a nm bug, since the whole system is affected. Not only Firefox, but also Konqueror and even "ping" from the CLI believe the machine was offline, once NM looses conection. I'm using Kubuntu Hardy.

I made a little experiment: I started my wireless connection and also my Huawei220 USB modem. NM (actually knetworkmanager) picked up the wireless and I surfed the web.

Then I disabled the wireless through the hardware button. The only internet connection I now had was through my USB modem. But since NM was slow to understand that the wireless has been disconnected, I could surf around 30 seconds through my USB modem. Then NM updated the status of the wireless and *boom* the internet connection was gone.

So the system seems to depend on nm reporting a valid connection. I don't know whether this is NM's or Ubuntu's fault.

[Matt Brannock (heisroot)]

I can also confirm this bug. I Chat and PPP to connect to the internet over my EVDO cell phone. I cannot use NetworkManager to properly configure my connection (my phone requires unusual initialization strings), so I use a custom script and a connection in /etc/network/interfaces which allows me to type "sudo ifup ppp0" and get a connection. However, NM does not recognize any internet connection, and thus GAIM connects (but says "Waiting for network") and Firefox starts in offline mode.

NM lists my script, called 1xevdo, under dial-up connections, but for whatever reason, it does not run properly (I think it is ignoring certain parts of my initialization strings).

NM either needs better support for this application, or a way to manually set its network-up status. I use a DHCP-based wired ethernet connection on multiple networks, so a manual configuration in interfaces is not a viable solution. I have Internet access, but NM doesn't know it.

[Simone Tolotti (simontol)]

Are 103 comments enough to mark this bug as "Comnfirmed"???

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

On Sat, May 10, 2008 at 9:42 AM, Simone Tolotti
<email address hidden> wrote:
> Are 103 comments enough to mark this bug as "Comnfirmed"???

I have the power to confirm this bug, but some Ubuntu employees reset
it when I do as they do not consider it a bug. If you yell loud
enough, perhaps you can get them to reverse their opinion...
--
Kristian Erik Hermansen
--
"When you share your joys you double them; when you share your sorrows
you halve them."

[Matt Brannock (heisroot)]

On a whim, I once again tried connecting to my CDMA connection via bluetooth using NM-applet-->Dial-Up Connections-->Connect to 1xevdo via Modem. This time, it worked! However, NM still does not recognize that it does not have a connection, and thus applications such as Firefox continue to start offline. I have attached the relevant syslog from a connection using this method, and a corresponding disconnection. NM seems to be giving a warning that it cannot activate the dial-up service, even though the connection is successful.

Is there a way to have it provide more verbose output about why this fails, and is it the cause of my problem?

I have also attached my /etc/network/interfaces file, as well as the scripts located in the /etc/ppp/peers directory I use to connect. Normally, I use "sudo ifup ppp0" to connect via bluetooth, and usually, the NM method above does not work (though it seems to be now).

I would like to get this sorted out, please let me know of any additional information which I could provide.

Attached as pastebin: http://pastebin.com/f2670b6ad

[Michael W. (michael-weisberg)]

Maybe I'm just looking/asking for the wrong thing, so I'll be plain about it:

I use a Verizon AirCard 620 that, because of complex command requirements and a password, can not be programmed to use the "standard" ppp scripts in NetManager. I connect, I use a script that sets up the modem, kills dhcpd, and calls pppd with /etc/ppp/peers/verizon as the parameter file. Since NetManager (which I use for connecting to wired and WiFi networks) does not control the connection, several other applications (Firefox, Pidgin, etc) all start in "Working Offline" mode.

For my own use what I have been doing is setting the wired connection to non-roaming, and a bogus fixed IP to force NM into allowing other apps to appear as "online." This is OK for me, but prevents my ability to recommend Ubuntu for wider distribution to a non-technical audience. Is it possible to provide either or both of:
 A) A check box that would allow a "Forced Online" state, and would report to downstream apps that a network is connected, and/or
 B) A programmatic way of setting "Forced Online" and "not Forced Online" for inclusion into scripts.

This is becoming a major headache for me, as I can not deploy any new machines to clients (with 8.04) until this is resolved.

[Sebastien Bacher (seb128)]

that's not a bug due to the applications, there are only using the network-manager informations, why did you open those tasks? closing this one

[Sokraates (sokraates)]

I made further experiments and partially solved the problem:

Start the (UMTS) modem, start Firefox, select "File" -> "Work Offline". "Work Offline" should now be unchecked and Firefox should now work properly.

Interestingly, most of the rest of my system reacted on this change, too. Adept and Evolution both work. Konqueror, on the other hand, still refuses to recognize the connection through the modem.

[Alexander Sack (asac)]

this is not a firefox bug; anyway, i ack that this is somewhat a bug in that firefox devs decided to use network-manager. Thus, wontfix (not invalid).

[wm-ubuntu (wmichae)]

I'm running kubuntu 8.04 and firefox 3 both fully updated. When I'm using my wired connection everything works fine, but when I disconnect my wired connection and enable my wireless connection firefox switches to ofline mode, and konqueror refuses to work. However I can still ping and ssh from a command prompt, the package manager is also able to find the wireless internet. Does anyone have any suggestions as to how I can get firefox and konqueror to recognize my wireless connection. I'm using the wireless assistant to manage that connection.

[Sokraates (sokraates)]

As written above, in Firefox select "File" -> "Work Offline". "Work Offline" should now be unchecked and Firefox should now work properly. For Konqueror I don't know a solution.

Do you use a "regular" wireless (wifi) or a wireless UMTS modem? A wifi-connection should be picked up by network-manager and you shouldn't have this problem in the first place.

[phoenix12345 (nchristy08)]

It's not a serious bug, but it sure is annoying. I use a ADSL connection with a Thompson Speedtouch 330 and have no network connection.

[John Vivirito (gnomefreak)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Added [MASTER] to summary since people have been marking bugs to a
different bug that is a dup of this.
- --
Sincerely Yours,
~ John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFILLLKqig4QTwcPCoRAsQkAJ9gWDGYNLhdMu539L7JxfRhaCawlwCfWvgF
5L+S08KBwnPFd5RDd/lg2oU=
=Siah
-----END PGP SIGNATURE-----

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

I just wanted to say "I told you so". I kicked and screamed about this bug for a while before the official Hardy release, but no one would listen. Now, I assure you that the comments to this bug will continue to grow onwards for the 3 years Hardy is supported on the Desktop, which is pretty ridiculous. Firefox is becoming the effective "Operating System" for constant web browsing folks addicted to web 2.66666..., and there is no reason Firefox should depend on Network Manager. I thought the one thing that set Linux apart from Windows was the decoupling of components and not forcing people to use certain packages if that is not necessary. Ubuntu has taken a turn for the worse in this specific decision with Firefox, and let's just hope it doesn't continue to happen in the future. We have too much to lose as a community. Let's keep the progress going and not start to build another Microsoft :-)

[bendis (bendis)]

Hi!

I believe that most of these problems (n-m + dial-up => offline) are tightly related to this bug: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/147119. The network-manager just fails to detect wheather a modem connected successfully or not. Please fix the bug #147119 - the fix is really trivial and patches were provided almost two months ago. It will surely help a lot of users...

Regards,
Bendis

[James Ward (jamesward)]

One other part of this bug which has not been mentioned here is that when you connect via dial-up you can't use NetworkManager to setup a VPN.

Also, I've heard that NetworkManager 0.7 fixes these problems.

[John Vivirito (gnomefreak)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

James Ward wrote:
| One other part of this bug which has not been mentioned here is that
| when you connect via dial-up you can't use NetworkManager to setup a
| VPN.
|
| Also, I've heard that NetworkManager 0.7 fixes these problems.
|
AS i understand n-m 7 wasn't stable for Hardy release or was just stable
at time and we wouldnt have had time to add it. Network-Manager .7
should be in Intrepid barring any problems,

- --
Sincerely Yours,
~ John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFILbOJqig4QTwcPCoRAq7UAJ9HzphIHtbSZspFWZdav+XvsJy9aACcD/dH
+1RxT068XSpm6x1Qp3HrzKo=
=swpd
-----END PGP SIGNATURE-----

[trollord (trollenlord)]

In case you feel Ubuntu developers are neglecting this important bug, switch to Fedora. Their Network Manager is configured to automatically handle grps/umts connections properly, including making sure the applications also are in online mode. Mostly all you have to do is to plug in your whatever modem and off you go.

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

On Sat, May 17, 2008 at 4:35 AM, trollord <email address hidden> wrote:
> In case you feel Ubuntu developers are neglecting this important bug,
> switch to Fedora. Their Network Manager is configured to automatically
> handle grps/umts connections properly, including making sure the
> applications also are in online mode. Mostly all you have to do is to
> plug in your whatever modem and off you go.

Which versions of Fedora support this feature properly?
--
Kristian Erik Hermansen
--
"When you share your joys you double them; when you share your sorrows
you halve them."

[Simone Tolotti (simontol)]

Fedora9 has NM0.7 ... not tested yet...
Foresight 2.0 has it too, I've tested it and working great with my 3g usb modem.

[Christian Mannß (christian-mannss-de)]

I have the same problem. I use my internal UMTS modem of my Dell notebook to connect to the internet by using umtsmon. Applications like Firefox, Evolution and Pidgim always starts in offline mode, mybe transmission (but this could be an other problem)

[hce (hce)]

I confirm this bug. depending on where I connect fromI use both network manager (for ethernet and wireless), and a custom udev script that brings up pppoatm automatically when the ADSL USB modem is connected (aetra modem, ueagle-atm driver - see http://atm.eagle-usb.org/wakka.php?wiki=UEagleAtmUdevEn).
network manager fails to detect that the ppp connection is up, and as a consequence evolution and firefox start in offline mode. yes, this is a nm bug, not mozilla or evolution's.
as I sometimes use it, uninstalling network manager is not an acceptable solution for me either.
it should just recognize that a ppp interface is up, even if it does not manage it, and set status to online.
at most, it could require the user to configure a certain interface as "not managed by nm but valid for online status".

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

SOLUTION:

Add Alexander Sack's PPA repository to your /etc/apt/sources.list:
deb http://ppa.launchpad.net/asac/ubuntu hardy main
deb-src http://ppa.launchpad.net/asac/ubuntu hardy main

Then update and install latest package. Let us know if it works for you...
--
Kristian Erik Hermansen
--
"When you share your joys you double them; when you share your sorrows
you halve them."

[Matt Brannock (heisroot)]

I've installed the update to NetworkManager, and have lost the "Dial-up connections" option in the contextual menu. I've tried configuring dial-up using "Manage Connections", but this does not work. My present "sudo ifup ppp0" still works to bring up the connection, but NM doesn't recognize the connection and Firefox still starts offline.

How can I get back the (previously working) contextual menu? This might get NM the proper dbus signals to know it's connected via PPP.

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

On Wed, May 21, 2008 at 3:33 PM, Matt Brannock <email address hidden> wrote:
> I've installed the update to NetworkManager, and have lost the "Dial-up
> connections" option in the contextual menu. I've tried configuring dial-
> up using "Manage Connections", but this does not work. My present "sudo
> ifup ppp0" still works to bring up the connection, but NM doesn't
> recognize the connection and Firefox still starts offline.
>
> How can I get back the (previously working) contextual menu? This might
> get NM the proper dbus signals to know it's connected via PPP.

I'm not sure how to get back the contextual menu, but if you want to
revert to the previous version of NetworkManager, then these are the
steps involved:

* remove network manager
* purge apt cache
* remove the PPA lines you added to /etc/apt/sources.list
* update your apt sources
* install old network manager
--
Kristian Erik Hermansen
--
"When you share your joys you double them; when you share your sorrows
you halve them."

[Simone Tolotti (simontol)]

Do not use asac's ppa nm-0.7 packages!!!
They works even worse than 0.6.6 and removing them is not easy (at least for a newbie).
Probably packages are very old (20080121) and they really needs to be updated!
Foresight : NetworkManager=0.7.0.r3332-0.1-1
Fedora9 : NetworkManager-0.7.0-0.9.3.svn3623
I've tried both Foresight 2.0 an Fedora9 and NM works great and out-of-the-box for me.
I know that we'll have the same features in Intrepid, but I hope that in the meantime someone will provide working backport/ppa packages. Thanks!

[Ernst (ernst-gumpinger)]

I am experiencing the same problem using wvdial to connect with my 3g usb device. NM states that there is no connection.
I am using Firefox 3.0b5.

[Lorenzo-colitti (lorenzo-colitti)]

Please fix this. NetworkManager 0.6 is not able to monitor the state of PPP interfaces and NetworkManager 0.7 has not been released yet.

As a result, Firefox is broken out of the box for everyone that uses PPP (both a standard dialup modem and an ADSL modem directly connected to the computer) and also has NetworkManager installed - which they are likely to have a) because it's installed by default by many distros or because they use it to manage their Ethernet connections. And worse, to fix it you need to unset the "File->work offline" checkbox *every time it starts up*. This is a terrible user experience. If offline detection isn't perfect, there should be a way to enable it.

Setting priority to major and attempting to renominate as blocker since it breaks Firefox for all dialup users and is very irritating to work around.

[Lorenzo-colitti (lorenzo-colitti)]

> If offline detection isn't perfect, there should be a way to enable it.

(and of course I meant a way to disable it)

[João Neves (jneves)]

Dan William's suggestion that the users should disable NetworkManager is not valid.

In my case I use NetworkManager to manage ethernet and wireless. But I also have a UMTS modem and no way for NetworkManager to deal with it AFAIK. I use NM for ethernet and wireless, and also use nm-applet to start the UMTS connection.

I believe this is a valid use case, particularly in my country where UMTS modems are usual.

So, yes this bug is annoying and the workaround (disabling NM) is not valid for me.

Thanks.

[Mike Connor (mconnor)]

We're not going to block on this, sorry. Its an edge case, and caillon's comments still seem to make the most sense. Its not that it isn't a valid use case, but we're doing what all NM-enabled apps are doing. You can manually force online if needed, but it seems like this is a NM issue to address in time.

[Lorenzo-colitti (lorenzo-colitti)]

I disagree that "everyone with a dial-up modem or PPPoE or PPPoA connection that also uses an app (networkmanager) that's installed on most distros by default" is an edge case. Updating summary accordingly.

For these users, is not a question of them tweaking the NM config, it's something that's broken out of the box. And since NM 0.7 has not been released, it's not fair to tell them to use it.

If someone volunteered to write a patch to have a hidden pref do this, would it be considered for inclusion?

[João Neves (jneves)]

Mike, Firefox is the only app in Ubuntu I've found with this behaviour. Could you give me an example of another one?

[João Neves (jneves)]

Just in case someone is missing the point: do you have any idea how painful it is to go thru 30 tabs having to refresh each one of them just because Fx3 tried to be smart and started in offline mode?

Thanks.

[Beltzner (beltzner)]

(In reply to comment #23)
> If someone volunteered to write a patch to have a hidden pref do this, would it
> be considered for inclusion?

It would definitely be considered. I don't know that code, so it's hard for me to intuit if that's something that's easily preffable or not in ways that aren't potentially harmful to the rest of the product.

While I (and mconnor, trust me) do understand the pain that this causes a subset of the Linux using audience, I want to stress that Firefox is doing what the operating system tells us: in this case, the operating system reports that there is no network connection, and we obey. It is indeed unfortunate that the operating system is misinforming us, and I'd be happy to do what I can as interim fixes as long as it's not in ways that remove a useful feature (automatic online/offline detection) for the vast majority of our users.

This will not block the final ship of Firefox 3.

[Beltzner (beltzner)]

dcamp: should this be here, or Core::Networking?

[Shaver (shaver)]

A minimal patch to add a hidden pref for users (or, one hopes, their distros) to use to disable NM events would be welcome. Even if it didn't make it into 3.0, it sounds like we'd want it in 3.0.1, and Ubuntu might take it on their side more eagerly given that it seems to be pretty much limited to the lies that Network Manager tells us on their setup.

Joao: right click a tab, "Reload All Tabs". :)

[Shaver (shaver)]

Marking wanted-firefox3+ based on discussion with Beltzner; any such patch would need to be very prompt, though.

[Alexander Sack (asac)]

On Thu, May 22, 2008 at 08:32:34AM -0000, Simone Tolotti wrote:
> Do not use asac's ppa nm-0.7 packages!!!

Confirmed. I will publish updated 0.7 packages soon. Until then,
please dont use or advice to use them ... at least not for this bug.

 - Alexander

[Nicola Soranzo (nsoranzo)]

(In reply to comment #26)
> While I (and mconnor, trust me) do understand the pain that this causes a
> subset of the Linux using audience, I want to stress that Firefox is doing what
> the operating system tells us: in this case, the operating system reports that
> there is no network connection, and we obey. It is indeed unfortunate that the
> operating system is misinforming us, and I'd be happy to do what I can as
> interim fixes as long as it's not in ways that remove a useful feature
> (automatic online/offline detection) for the vast majority of our users.

Just to point out, it's not the operating system reporting that, it's NetworkManager...

[Mozilla (mozilla)]

Created an attachment (id=322620)
patch

Tentative patch as base for discussion.
This first try keeps everything in place (dbus connection, NM listener) but just does not update the network status.
I wasn't sure about the pref name. There might be better suggestions.
And I wonder what to do if the pref-service is not available for some reason (probably at startup).

[Roc-ocallahan (roc-ocallahan)]

This patch looks good to me. The pref-service should be available here.

I'm not sure about the pref name.

Seems to me that NetworkManager itself should have a setting "some devices not currently managed" (either manually configured or automatically detected), and if that is true then it shouldn't send StateChange signals since it doesn't know what the true current state is.

[Roc-ocallahan (roc-ocallahan)]

(In reply to comment #30)
> Just to point out, it's not the operating system reporting that, it's
> NetworkManager...

Excuse me while I go postal here, but this kind of nonsense is why people hate developing apps for Linux.

[Alexander Sack (asac)]

(In reply to comment #10)
> I get people all the time asking "Why doesn't NetworkManager see my network
> device?". Every single time it's because that person is using Ubuntu and they
> have configured that device in "Manual" mode, which is an Ubuntu specific hack
> and causes me no end of trouble upstream.

This is not really true. Manual mode devices blacklisted for network manager will make NM always expose the "online" state.

The problem here is not our ifupdown blacklisting, but ppp, which isnt really supported by network manager 0.6.6.

[Alexander Sack (asac)]

(In reply to comment #12)
> Part of that is because Ubuntu ships many quite horrible-quality drivers that
> simply don't work with wpa_supplicant and NM, because they don't support WEXT
> properly. I laud their efforts to make as much hardware work as possible, but
> unfortunately the _quality_ of that support for many drivers just sucks.
>
> If you're using out-of-kernel drivers (ubuntu has in the past had 4 different
> _stacks_ in their kernel, including net80211, linux-wlan-ng, vendor drivers,
> etc not to mention shipping ndiswrapper) then there's not much that _anyone_
> can do to guarantee the quality of those drivers, and every time somebody asks
> why their card doesn't work when it uses an out-of-kernel driver, I can usually
> find 3 or 4 major errors in the driver's WEXT conformance.
>

I agree that there is a bunch of crappy drivers out there.

However, most drivers you referred to in your blog appear to be drivers for old hardware that dont have a modern replacement. Should we just drop support for them completely in order to stop network manager from misbehaving?

> Yes, Ubuntu has a large user base and it's probably something FF has to work
> around given that. But many of the reasons that NM doesn't work for people
> using Ubuntu are specifically because of bad choices Ubuntu has made when
> packaging NetworkManager (often for ndiswrapper and madwifi) and when stuffing
> bad quality drivers into their kernel packages.
>
> Doesn't help the users of FF though since you obviously can't blame them for
> the distro they use.

IMO, the network manager online state is not reliable by design and probably its main use case is to provide a way to fast-fail attempts to connect to a network resource.

Thus, I think that network-manager could tune its heuristic to always expose "online" when there is a route to any network.

What do you think?

[Roc-ocallahan (roc-ocallahan)]

We have to interpret NM_STATE_DISCONNECTED as "you definitely can't connect to the internet" and NM_STATE_CONNECTED as "maybe you can" ... since you could have a link to a router that's not connected to anything else. I hope NetworkManager agrees.

[Alexander Sack (asac)]

(In reply to comment #31)
> Created an attachment (id=322620) [details]
> patch
>
> Tentative patch as base for discussion.
> This first try keeps everything in place (dbus connection, NM listener) but
> just does not update the network status.
> I wasn't sure about the pref name. There might be better suggestions.
> And I wonder what to do if the pref-service is not available for some reason
> (probably at startup).
>

I am fine to pull this in as a quick fix. Just curious, why a hidden pref?

[Mozilla (mozilla)]

(In reply to comment #37)
> I am fine to pull this in as a quick fix. Just curious, why a hidden pref?

It doesn't need to be that hidden IMHO. Adding a default value of false to the prefs should be fine. It should be "hidden" in the sense of not having any UI though. If noone cares for the pref name I'll keep it and add the default pref in the next patch.

[Dan Williams (dcbw)]

If NetworkManager is not able to control your default your (and the 0.6 that Ubuntu includes isn't capable of doing so for things like mobile broadband or PPPoE, which 0.7 fixes) then you should turn NetworkManager off and use your normal distro network config scripts.

NetworkManager is appropriate for cases where it is able to control the default route. If it is not, then you should turn it off for that machine.

If Firefox doesn't assume that when the NM dbus service is not around, that the machine is online, then FF needs to be fixed to assume so. But when the NM service is around, then it is assumed that NM is managing the default route, and thus can be asked for authoritative network status. If you have made your primary network device "managed" rather than roaming mode (an Ubuntu-specific patch to NetworkManager) then you aren't using a configuration supported or cared about by upstream NetworkManager developers. In that case, turn off NetworkManager.

[João Neves (jneves)]

Dan, interesting point-of-view, but it fails in real life.

My two main internet connections are a UMTS modem and wifi. NM is great for wifi, and it seems absurd to me that I should change my present "pick the wifi network from NM list" to 1) start NetworkManager, 2) start nm-applet and 3) "pick the wifi network from NM list" everytime I change from UMTS to wifi.

As 0.7 is not out, the mistake is on Firefox by assuming that NM is able to manage all network connections. The fact that it can manage somethings well and others not at all, doesn't mean it's not useful and shouldn't be on. It's just Firefox's assumption that is wrong.

Thanks for a great program.

[Dan Williams (dcbw)]

João: yes, that sucks. But in your case, NM 0.6 is simply not capable of correctly managing the UMTS card. It's just not built for that. I maintain that FF is correct in assuming that when NM is running, NM reports accurate status. If NM is not able to correctly control the default route of your primary device, then you should not be running NM. It doesn't matter if NM can easily control the wifi, because that's only a _part_ of the total connectivity of your laptop. Until your distro updates to 0.7, there are other tools that will probably work better for you because they are limited to just controlling the wifi (wifiradar, etc).

[Lorenzo-colitti (lorenzo-colitti)]

Sorry for spamming this bug, but Dan, I disagree. The facts are:

- Firefox 3 uses NetworkManager to determine whether it's online
- The current version of NetworkManager (0.6) does not support PPP connections
- Some of Firefox's users use PPP
- NetworkManager is installed by default on many distros

Given the above, if we look at it from Firefox's perspective, NetworkManager is not a 100% reliable way of finding out if there is an Internet connection, because there is a class of users for which it fails. These users won't know what the problem is and won't know that they need to disable NetworkManager. And the distros can't disable it for them because they don't know if the users need it for other connections like Ethernet or wifi. So adding a pref to Firefox to allow it not to trust NetworkManager is a reasonable idea.

The pref can default to off (i.e., use NetworkManager), and distros who ship the current version can turn it on in all.js. When NetworkManager 0.7 is released, they can disable it again. Everybody wins.

If NM 0.7 was out now, I'd definitely agree with you. But I think saying that this Firefox feature should only work on an unreleased version of NM is not a reasonable position.

When do you expect NM 0.7 will be released?

[Dan Williams (dcbw)]

Some distros probably turned on NM 0.6 by default before it was ready for the majority of that distros userbase. We didn't turn NM on by default in Fedora until Fedora 9 mainly because we felt that only NM 0.7 covered enough use-cases to be turned on by default (PPP for example).

I can't help what distros that I don't have control over do with NM, that's Open Source at its best (or worst). The distro's users have to deal with the consequences of that distros decisions.

I don't personally have a problem with FF having this preference. I'm simply correcting mistaken viewpoints and impressions that people and distros have about NM.

[Caillon (caillon)]

(In reply to comment #42)
> If NM 0.7 was out now, I'd definitely agree with you. But I think saying that
> this Firefox feature should only work on an unreleased version of NM is not a
> reasonable position.

Hm, if you don't use "unreleased" software, how do you even know about this bug? I don't remember the Firefox 3 release announcement yet. ;-)

Maybe the real thing we should fix is to just bump the NM requirement in configure to require an 0.7 build for this support to be built.

[Shaver (shaver)]

(In reply to comment #44)
> Maybe the real thing we should fix is to just bump the NM requirement in
> configure to require an 0.7 build for this support to be built.

That sounds pretty tempting. RC2, and therefore in all likelihood FF3, closes in 48 minutes. Let's get this done if we're going to do it. (Reviews, testing, tests in suite, approval request with risk profile.)

[Lorenzo-colitti (lorenzo-colitti)]

> Hm, if you don't use "unreleased" software, how do you even know about this
> bug? I don't remember the Firefox 3 release announcement yet. ;-)

That's different! We're developers ;-)

[Mozilla (mozilla)]

(In reply to comment #44)
> Maybe the real thing we should fix is to just bump the NM requirement in
> configure to require an 0.7 build for this support to be built.

I still would vote for the simple "ignore" patch.
- NetworkManager isn't a compile dependency at all currently
- I still have to see that NM 0.7 works in real life for every connection type

[Lorenzo-colitti (lorenzo-colitti)]

(In reply to comment #44)
> Maybe the real thing we should fix is to just bump the NM requirement in
> configure to require an 0.7 build for this support to be built.

Sounds like a fine plan to me. I'll start looking, but there's no guarantee I can figure out how to do this in 32 minutes, I don't even have a local copy of the tree...

[Shaver (shaver)]

If you think that we should take that patch, you should ask for review on it.

[Mozilla (mozilla)]

(From update of attachment 322620)
Asking someone for review. (That's what I love about the mozilla project. The roulette about finding the correct reviewer (within a few minutes) if one doesn't do it daily) IIRC, sr is not needed for toolkit?

[Lorenzo-colitti (lorenzo-colitti)]

Created an attachment (id=322828)
Disable DBUS support if libnm_glib 0.7 is not present

If libnm_glib >= 0.7 (and therefore, networkmanager 0.7) is not present, don't enable DBUS support.

[Lorenzo-colitti (lorenzo-colitti)]

(From update of attachment 322828)
Who can review this? Pinging Chris since it was his idea, but perhaps someone else is qualified too?

[Reed Loden (reed)]

(In reply to comment #51)
> Created an attachment (id=322828) [details]
> Disable DBUS support if libnm_glib 0.7 is not present
>
> If libnm_glib >= 0.7 (and therefore, networkmanager 0.7) is not present, don't
> enable DBUS support.

Do we know if the mozilla.org build machines have NetworkManager 0.7? If not, they'll need it before this patch can land.

[Lorenzo-colitti (lorenzo-colitti)]

This patch silently disables DBUS if networkmanager 0.7 is not present, so that shouldn't be an issue. I think there's a bug in the patch though, checking now.

[Reed Loden (reed)]

(In reply to comment #54)
> This patch silently disables DBUS if networkmanager 0.7 is not present, so that
> shouldn't be an issue.

Sure it is an issue, as it would disable DBUS support for me, as I use mozilla.org builds.

[Caillon (caillon)]

(From update of attachment 322828)
You could simply combine the two things into one PKG_CHECK_MODULES call. E.g. PKG_CHECK_MODULES(MOZ_DBUS_GLIB, dbus-glib-1 >= $DBUS_VERSION NetworkManager >= $NM_VERSION)

[Caillon (caillon)]

(From update of attachment 322828)
also, since we don't use the glib interface, we probably really do want to use NetworkManager.pc, not libnm-glib.pc

[Lorenzo-colitti (lorenzo-colitti)]

I don't have NetworkManager.pc. Was this added in NM 0.7?

[Caillon (caillon)]

No... that's been around since the start of the project. It should be in the main -devel package.

[Shaver (shaver)]

Not taking this now, will relnote the interaction with PPP and look at a patch for 3.0.1 when the domain experts (roc, campd) are around.

[Lorenzo-colitti (lorenzo-colitti)]

Created an attachment (id=322833)
Disable DBUS support if NetworkManager 0.7 is not present

Take two: check for NetworkManager.pc instead of libnm_glib.pc, properly define MOZ_DBUS_ENABLED, properly print results, and run the check in only one statement.

[Roc-ocallahan (roc-ocallahan)]

(In reply to comment #39)
> If Firefox doesn't assume that when the NM dbus service is not around, that the
> machine is online, then FF needs to be fixed to assume so.

When NM is not around, FF assumes you're online. (Of course! Otherwise we'd be total dunces.)

[Roc-ocallahan (roc-ocallahan)]

(From update of attachment 322620)
I'm not sure why you didn't just ask me for review.

[Roc-ocallahan (roc-ocallahan)]

I still think the best solution is what I alluded to in comment #32. NetworkManager can detect whether it's managing the interface for the default route. When it isn't, it should not send StateChange signals.

[Mozilla (mozilla)]

Agreed. My patch is just a quick workaround to make Firefox usable on systems where NM might be misconfigured/misplaced or whatever.
I also think that NetworkManager should know when its managing the default route or not but that's not to be discussed here probably.
I also _guess_ that there might be rare situations where even NM 0.7 doesn't manage the network connection even if it's running. So personally I think the configure check isn't a good idea anyway and it's a compile time switch whereas that has nothing to do with the version which is actually running at runtime.

[PearZoo (peter4)]

Best thing I even did was remove network-manager and install WiCD. There is just no comparison, network-manager has always, in my opinion been the poor cousin of WicCD.

Install instructions here:

http://www.ubuntugeek.com/wicd-wired-and-wireless-network-manager-for-ubuntu.html

Good luck

[fusspilz (reinhard-scherer)]

Thanks PearZoo,
WicCD was a painless solution for me on kubuntu,
I hope it makes the way into the ubuntu repositories.

[antistress (antistress)]

My father has a RTC connexion (serial modem 56K) and Firefox 3b5 on Ubuntu 8.04, whereas gnome-ppp handles the connexion, and Firefox always starts in offline mode.
I've desactivated network-manager on startup (from preferences menu) but it didn't fix the problem
Uninstalling network-manager from synaptic solved the problem.

Then for me the solution was :
uninstall network-manager
Make use of gnome-ppp to handle the internet connexion

Note that i've also tried to connect through System>Administration>Network
The connexion was ok but Firefox couldn't make use of it to access to internet

[Peter (nitep)]

The bug is in firefox and evolution. Thunderbird starts off online.

[hce (hce)]

>The bug is in firefox and evolution. Thunderbird starts off online.
this only means that thunderbird does not read online status from nm.
the problem is that nm does not recognize network connections that it does not manage, and pretends to be offline even if there is a perfectly working internet connection .

[Beltzner (beltzner)]

The summary doesn't really reflect the current solution, and I think that while a preference would help as a workaround, it isn't really a solution (the solution is that we should make sure we're getting the right signals for the OS).

So I spun out bug 437453 for adding a preference for turning on/off automatic online/offline. Let's keep working on Linux/NM specific solutions here, and the workaround there.

[Alexander Sack (asac)]

upstream will land a hidden pref that you can use to disable network manager ... to mitigate this.

[catsophie (yanlin-p)]

I confirm this bug on Fedora 9.0/Firefox 3.0b5. I have set network:online to be 'true' in the about:config page, totally useless.

[Alex (alex-mercurio)]

me too Firefox 3 begin with offline on Ubuntu 8.04

[Mozdev (mozdev)]

I have an additional fringe case on this one where I'm running a local web server for field order entry on a few hundred laptop computers. I NEED network manager because it is easy for my users to understand. But I have the problem that they are not always online and connect to localhost to place their orders. Firefox is always starting out in offline mode and I would like to be able to force it to ignore network manager so that they can still use the system. When they update Firefox to 3.0 I'm going to have a lot of confused people and phone calls to deal with.

[Roc-ocallahan (roc-ocallahan)]

Wolfgang's patch should help with that.

Wolfgang, can you land this in mozilla-central or do you want me to do it?

[Mozilla (mozilla)]

(In reply to comment #68)
> Wolfgang's patch should help with that.
>
> Wolfgang, can you land this in mozilla-central or do you want me to do it?

I'd like (to try) to land it ;-) (using HG the first time)

[Mozilla (mozilla)]

(From update of attachment 322620)
Landed in mozilla-central

[Bipin Thite (bipinthite)]

Same issue is here also.
I'm using Ubuntu 8.04 (Hardy Heron) with Firefox-3.0b5. I connect to the internet via dial-up mobile-phone-modem and with gprs subscription. Whenever I launch Firefox it always starts in Offline mode, and it doesn't matter whether I'm connected to the internet or not, it does the same, always.

[Alexander Sack (asac)]

(In reply to comment #61)
> Created an attachment (id=322833) [details]
> Disable DBUS support if NetworkManager 0.7 is not present
>
> Take two: check for NetworkManager.pc instead of libnm_glib.pc, properly define
> MOZ_DBUS_ENABLED, properly print results, and run the check in only one
> statement.
>

I dont think that this should be determined at compile time. If you want to turn of network manager support based on what NM version is running it should be figured at _runtime_.

Dan, is there a way to request version information of NM through DBus?

Personally, I think that we should take Wolfgang's patch for now.

[Eric Lee Elliott (eric-eric-elliott)]

Firefox3 is now staying on line in one computer. Network Manger
has been removed. Network Manager was problematic in general. NM
would not leave ethernet port off. NM would not consistently use
only one preferred wlan port.
Without NM, kppp still does my Internet connection and FF3 is
always on line. Still using ATT cellular modem, Sierra AC875 to
access Internet.

Updated Kubuntu, KDE4, 32 bit Intel & Intel 945 system.

Next I will remove NM from 64 bit Athlon system and install FF3.

I fear I am one of many that have or are converting to using KDE
software rather than Mozilla.

[Lorenzo-colitti (lorenzo-colitti)]

I agree. The compile-time hack is just a hack so that at least distributors can turn it off. Wolfgang's approach is better.

[Nitesh Mistry (mistrynitesh)]

Updated to the final release of Firefox 3 from Synaptic. Still the problem persists. Also the Network manager shows "No network connection" even when I am typing this online. It used to be so even at the time of Gutsy, but FF2 didn't bother me. The problem also shows up in Pidgin. Hope anyone does something about this, without arguing whether it is a Firefox problem or NM.

[Marcia-mozilla (marcia-mozilla)]

*** Bug 434785 has been marked as a duplicate of this bug. ***

[Marcia-mozilla (marcia-mozilla)]

*** Bug 435725 has been marked as a duplicate of this bug. ***

[forza (rumfisken)]

I also have installed the Opera 9.5 browser and it connects without any problem. Firefox 3 is a different story. I have to got to: File -> Work offline to get online yet Opera 9.5 goes online with no problems whatsoever. It is not as fast as firefox 3, though.

Opera for 32 bit (k)ubuntu:

http://www.opera.com/download/index.dml?opsys=Linux%20i386&lng=en&ver=9.50&platform=Linux%20i386&local=y

Opera for 64 bit (k)ubuntu:

http://www.opera.com/download/index.dml?opsys=Linux%20x86_64&lng=en&ver=9.50&platform=Linux%20x86_64&local=y

I know installing another browser is not an optimal solution...

[Nitesh Mistry (mistrynitesh)]

I installed Wicd as mentioned earlier in this report by PearZoo which automatically removed network manager and its gnome front-end... and now all the apps are working fine

[Henry Wertz (hwertz)]

     I've found a kludgy "fix" for this (that doesn't just involve removing nm, since it's wireless and wired handling are nice). In my case, I have a Inspiron 2200 with wifi set via ndiswrapper (which works fine) and an aircard (Verizon PC5740) which worked except for the "Offline mode" problem. So it's the case where if I don't have wifi, and dial via CDMA, I get the "Work Offline" stuff going on.

     So, if I go into /etc/dbus-1/system.d/NetworkManager.conf, I inserted in line 18 (all on one line):
<deny send_interface="org.freedesktop.NetworkManager" send_member="state"/>

     (That's in the 'policy at_console="true" ' section of the file in case yours is arranged a little differently for whatever reason.)

     This file seems to be checked on-the-fly, I could change this and see an immediate effect on firefox (although I rebooted to check for side effects).

     Consequences:
     This blocks firefox and any other app's attempt to get the online/offline state from NetworkManager, which makes it (and probably any other apps that try to check NetworkManager) decide Networkmanager is not there and assume online state. It ALSO blocks nm-applets access to this though...
     Since nm-applet can't get the online/offline state from NetworkManager either, it doesn't show online state properly (it'll show the exclamation mark while the network is up and running fine for static IP wifi and ethernet)... For regular ol' DHCP wifi, it does still show the signal bars (since blocking "status" doesn't block wifi signal strength info).
     Also, under "manual configuration" the "Roaming mode" text changes to "This network interface is not configured", and the checked "Roaming mode" checkboxes change to uncheckd "Enable this connection" checkboxes. But the interface seems consistent and to behave itself. Problem solved as far as I'm concerned, until I got to NetworkManager 0.7!

[Beltzner (beltzner)]

(In reply to comment #70)
> (From update of attachment 322620 [details])
> Landed in mozilla-central

And? Do we know that the bug fixes the problem and isn't causing any other regressions?

We'll take a well tested patch here, but I'm not sure we'll say that it totally blocks the first branch release. Very much wanted, though.

[A-sloman (a-sloman)]

Bug 436815 – offline mode turn on/off -- includes reports that seem related to this.I have had to disable NetworkManager to make Firefox 3 usable on my linux PC (running Fedora 9).

The problem is NOT restricted to Ubuntu as suggested in Comment #10

It seems that (1) NetworkManager is at fault in giving wrong information, (2) The Fedora people are at fault in turning on NM by default in Fedora 9, and (3) the Firefox people are at fault in making FF trust NM without allowing mechanisms to override that trust.

The combined consequence of those three faults is that I have wasted several hours in the last few days fighting this problem, until I discovered I could fix it by turning off NM, which I don't need on a PC connected by cable to the router using static addresses. From several other bug reports I think many other people are suffering.

I completely agree with this in comment #25 "Just in case someone is missing the point: do you have any idea how painful it is to go thru 30 tabs having to refresh each one of them just because Fx3 tried to be smart and started in offline mode?" I keep much of my work in multiple tabs in FF.

This terrible behaviour, including being required to refresh each tab manually, forced me back to using FF2 for a while, until I discovered that I could restart FF3 in online mode if I (a) start FF2, then (b) kill it then (c) start FF3 !! (I have no idea why this works, but it may be a clue for a fix.)

Painful, but not nearly as painful as having to restart all my tabs manually.

I've removed the need for this procedure by disabling NM, but, as indicated above, some people need NM (e.g. on laptops used with different connections in different places). So FF3 should either not trust NM, or should provide a way to users to override that trust.

It would not be so bad if the 'work offline' button had an option: 'go online and restart all tabs and windows'. (also suggested in Comment #28, I see.)

Good software designers provide ways of helping users mitigate the effects of faults in other software instead of simply blaming the other software.

Thanks.

[Alexander Sack (asac)]

On Sat, Jun 21, 2008 at 08:54:27AM -0000, Henry Wertz wrote:
> I've found a kludgy "fix" for this (that doesn't just involve
> removing nm, since it's wireless and wired handling are nice). In my
> case, I have a Inspiron 2200 with wifi set via ndiswrapper (which works
> fine) and an aircard (Verizon PC5740) which worked except for the
> "Offline mode" problem. So it's the case where if I don't have wifi,
> and dial via CDMA, I get the "Work Offline" stuff going on.
>
> So, if I go into /etc/dbus-1/system.d/NetworkManager.conf, I inserted in line 18 (all on one line):
> <deny send_interface="org.freedesktop.NetworkManager" send_member="state"/>
>
> (That's in the 'policy at_console="true" ' section of the file in
> case yours is arranged a little differently for whatever reason.)
>

Do you have more than one login session running when you see this
issue?

 - Alexander

[Sylvain Pasche (sylvain-pasche)]

*** Bug 441484 has been marked as a duplicate of this bug. ***

[Sylvain Pasche (sylvain-pasche)]

*** Bug 441491 has been marked as a duplicate of this bug. ***

[Henry Wertz (hwertz)]

>Do you have more than one login session running when you see this
>issue?
Nope.. just one session. Without my kludge, It's just like what Daniel Newman etc. have described where the CDMA aircard is a PPP link, and NetworkManager0.6x apparently doesn't track PPP state. If I use wifi, or ethernet, firefox is online. If I don't have a wifi or ethernet connection, and use PPP only, firefox decides I'm offline.

     With the kludge, as I say, nm-applet doesn't show proper status for ethernet or static IP wifi (or PPP) (the machine DOES get online, nm-applet just doesn't show it.) For normal wifi, nm-applet doesn't show the DHCP swirl but otherwise does operate fully (shows access point list, joins access points, shows signal strength, etc.) And, at all points, firefox shows online status as the UNIX gods intended 8-).

[Peter (peterroots)]

Well I have just upgraded to kubuntu Hardy which has the fully fledged firefox3 packages.
FF3 starts in offline mode for me when connected via a speedtouch usb modem. I connect to it using pon/poff as NM does not recognize any modem is plugged in.
Habitually I have always closed the NM applet before trying to use pon as kmail will not notice my pop3 account to send mail but will collect via smtp if NM applet is running.
I don't want to remove NM as when I have to use cable or wireless this works well (or at least it did in 7.10 - not in a position to test this for a month or so)

[Peter (peterroots)]

oops! brain not switched on today - re comment above, I got my pop3 and smtp back to front. just to put is straight I can send via smtp but not collect via pop3 (kmail thinks it can't see the pop3 server).
Interestingly, today I found out how to add ppp to my interfaces file and now I can connect using NM - right click, dial up connections but although this gives me internet FF3 still starts in offline mode and I still can't collect mail! shutting NM then lets me collect mail and continue to use the internet but FF3 still starts in offline mode.

from this I would say there is a problem in FF3 but also one in NM

[Simone Tolotti (simontol)]

If you want to try nm-0.7 you should add dalbers' ppa following this guide:
http://ubuntuforums.org/showthread.php?t=797059

Working great for me!

[Simone Tolotti (simontol)]

If you want to try nm-0.7 you could add dalbers' ppa following this guide:
http://ubuntuforums.org/showthread.php?t=797059

Working great here!

[Peter (peterroots)]

Thanks Simone but just before I read your fix I managed to get my system working, after and lot of googling and fiddling. It was dead simple once I found out what to do (but aren't most things, once figured out?)

I tinkered with /etc/network/interfaces
my original was like this

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

and now it is like this

auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

iface ppp0 inet ppp
provider tiscali

iface eth0 inet dhcp

iface eth1 inet dhcp

I can select tiscali from the network manager right-click dialup connections and hang up later instead of pon tiscali / poff
I can see and connect to wireless when a signal is around and I guess I will be able to plug a cat5 cable and get a network if one was to hand.

FF3 now knows it is on line and starts accordingly. Kmail sends and receives mail fine. skype and kopete work fine (always did but nice to know I've not messed them up).

[Beltzner (beltzner)]

(In reply to comment #75)
> (In reply to comment #70)
> > (From update of attachment 322620 [details] [details])
> > Landed in mozilla-central
>
> And? Do we know that the bug fixes the problem and isn't causing any other
> regressions?
>
> We'll take a well tested patch here, but I'm not sure we'll say that it totally
> blocks the first branch release. Very much wanted, though.

Can I get an answer here? Can someone on Linux/3.1apre builds confirm that this helps not hinders?

[Jonathan Blow (jon-number-none)]

Also having this problem. Ubuntu 8.04, FIrefox 3. Using an EVDO modem over ppp. Only one login session.

I am about to try Henry's fix (blocking Firefox from performing the query) but I wanted to post first before I have to close all my browser windows.

This is absolutely a bug in Firefox, regardless of whether there is a bug in Network Manager. Firefox should be reality-based when it comes to making this decision: it should look at the actual routing tables and what they are doing, not asking some high-level app.

It's annoying to see this bug still not set to status Confirmed when it is so obviously broken, and so many people are experiencing it. I understand why earlier posters to this thread would be angry with the response.

[Jonathan Blow (jon-number-none)]

I also want to point out that what's in config files should be irrelevant. Why is Firefox checking network config files? It should just check the actual network.

[Jonathan Blow (jon-number-none)]

Confirmed, Henry's fix works for me.

[Todd-cooper (todd-cooper)]

I am having the same problem on fedora core 9 with an docking bay ethernet that sometimes does not come up when the machine boots.

[Beltzner (beltzner)]

(From update of attachment 322620)
a=beltzner

[Alexander Sack (asac)]

On Fri, Jun 27, 2008 at 06:05:34PM -0000, Simone Tolotti wrote:
> If you want to try nm-0.7 you could add dalbers' ppa following this guide:
> http://ubuntuforums.org/showthread.php?t=797059
>

Remember: if you use that package you have to take care on your own
that you get the real NM 0.7 once it comes out. I cant look at PPA
versions to ensure that you will be auto upgraded.

Use the edge.launchpad.net/~network-manager PPA instead!!!

The applet should be there in a few ... everything else should already
be available.

 - Alexander

[Beltzner (beltzner)]

MU+ but not blocking1.9.0.1 anymore - if the patch lands (when the tree clears (on the log on the bottom of the sea)) in time that's fine, if not, it'll wait to 1.9.0.2.

[João Neves (jneves)]

Mike, just to say that it does fix the wrong behavior for me (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.1pre) Gecko/2008063004 GranParadiso/3.0.1pre). Opening Firefox 3.0 in the same system (with another profile) exhibits the same behavior described in this bug.

Thanks to all,
João Miguel Neves

[Simone Tolotti (simontol)]

@Alexander:
I'm glad to see that ~network-manager PPA was updated.
At the time I've added dalbers' ppa to my sources.list, ~network-manager PPA was stuck at svn20080121.
Hope you'll keep it updated in the future. Thanks.

[Alexander Sack (asac)]

On Mon, Jun 30, 2008 at 05:25:30PM -0000, Simone Tolotti wrote:
> @Alexander:
> I'm glad to see that ~network-manager PPA was updated.
> At the time I've added dalbers' ppa to my sources.list, ~network-manager PPA was stuck at svn20080121.
> Hope you'll keep it updated in the future. Thanks.
>

The PPA will track intrepid for for hardy. so yes, it should be
regularly updated now. Please be double sure that you have all the
packages replaced by the one from ~network-manager as all versions are
lower than the one in dalbers ppa.

 - Alexander

[Reed Loden (reed)]

Checking in toolkit/system/dbus/nsNetworkManagerListener.cpp;
/cvsroot/mozilla/toolkit/system/dbus/nsNetworkManagerListener.cpp,v <-- nsNetworkManagerListener.cpp
new revision: 1.3; previous revision: 1.2
done

Still needs to be made non-hidden.

[Mozilla (mozilla)]

Created an attachment (id=327557)
unhide pref

I think that's all what's needed to "unhide" the pref

[Mozilla (mozilla)]

Checking in all.js;
/cvsroot/mozilla/modules/libpref/src/init/all.js,v <-- all.js
new revision: 3.759; previous revision: 3.758
done

[Rick Gatewood (george-gatewood)]

I can also confirm this problem with Firefox 3. I had to downgrade my uncle's computer to Firefox 2. He uses dialup and never had any problem before. Firefox 3 always starting offline was really confusing him.

I hope this gets fixed soon. It is really tough for folks who have to use a modem anyway and this just makes it worse!

[TJ Wilson (tjwilson1)]

*** Bug 442750 has been marked as a duplicate of this bug. ***

[ichudov (igor-chudov)]

I have a solution that I think is as near perfect as it gets. It is very simple.

The problem: I need NetworkManager for connecting my laptop to wifi and ethernet. However, it messes me up when I am on PPP.

The solution: kill Network Manager before running pppd and revive it after, e.g.:

#!/bin/sh
killall NetworkManager
pppd my_isp
NetworkManager

I run the above script whenever I need to connect via PPP. I never run pppd alone outside of this script.

That gives me a basically 100% correct behavior at all times. If I stop PPP, or pull out my broadband modem card, pppd stops and NetworkManager starts and is ready to serve me. When I am on PPP, NetworkManager is not bothering me with incorrect behavior.

I have been very happy in the last few days and think that it should work for just about anyone.

i

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

Another solution might be to write a firefox addon to always disable
offline mode at startup. Notice that firefox already does this when
you are asked if you would like to upgrade to a new addon revision.
It is quite ridiculous that we must resort to fixing this issue via a
custom firefox addon. I still want to strangle the person who thought
is would be a nice idea to make firefox rely on
networkmanager...*rolls eyes*

On 7/1/08, ichudov <email address hidden> wrote:
> I have a solution that I think is as near perfect as it gets. It is very
> simple.
>
> The problem: I need NetworkManager for connecting my laptop to wifi and
> ethernet. However, it messes me up when I am on PPP.
>
> The solution: kill Network Manager before running pppd and revive it
> after, e.g.:
>
> #!/bin/sh
> killall NetworkManager
> pppd my_isp
> NetworkManager
>
> I run the above script whenever I need to connect via PPP. I never run
> pppd alone outside of this script.
>
> That gives me a basically 100% correct behavior at all times. If I stop
> PPP, or pull out my broadband modem card, pppd stops and NetworkManager
> starts and is ready to serve me. When I am on PPP, NetworkManager is not
> bothering me with incorrect behavior.
>
> I have been very happy in the last few days and think that it should
> work for just about anyone.
>
> i
>
> --
> [MASTER] "Offline Mode" feature fails to detect proper online state for
> networks that are managed outside of network manager.
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Sent from Gmail for mobile | mobile.google.com

Kristian Erik Hermansen
--
CISSP, CEPT, CREA, CEH, Linux+, A+, QGCS, ACSA, this is getting ridiculous...
http://kristian-hermansen.com

[Xtc4uall (xtc4uall)]

is this going to land on trunk too?

[Mozilla (mozilla)]

It already landed on trunk. It's not closed because it's not supposed to be the final solution as I understood.

[helios (martin-lichtvoll)]

I also stumbled across this really annoying bug. I use network manager for WiFi at times, but I do not - at my full intention - use it for eth0 yet. I use Debian with guessnet to set a static IP if it detects my home routers IP and MAC address. Granted I could install a DHCP server on my ASUS WL-500g Premium with Debian Etch - and I think I will...

... but actually I really dislike being patronized by computer software. I like to use Network Manager for Wifi, I like to use other setup software for eth0 at my *own discretion*, and I like to use Firefox (at times).

If Network Manager could not control all interfaces it should be honest about offline and online status:

1) If there is a way to still determine reliably whether the machine is off- or online it should be implemented.

2) If not, Network Manager should be honest about it and stop pretending that it nows better than me. It should simply say: Well there are interfaces that I do not control, I have no frigging clue about online state. Go figure. Then thats up to my own decision whether I want to live with that limitation or install a DHCP server on my ASUS router.

I really do not agree with Network Manager insisting on an "all or nothing" scenario. IMHO there are valid reasons for *not* managing all interfaces with Network Manager and NM should support such scenarios as good as it can.

Until either such a solution is implemented in Network Manager, Firefox should give me a way of not using it instead of insisting "I know better than you, the user".

[helios (martin-lichtvoll)]

Sorry, sounded a bit harsh I guess. I understand that a patch to disable NM online detection is on the way.

[Jonathan Blow (jon-number-none)]

What exactly is the point of Offline Mode in the first place? Is it worth all the trouble it is causing?

Maybe we should file "Existence of Offline Mode" as a bug.

[Henry Wertz (hwertz)]

---^ I second Jonathan Blow's idea.. having apps behave differently if they think they are online or not is just not "UNIXey". IMHO, they should do what they are told, and just find out they have "no route to host" if there in fact isn't one.

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

BEST POSSIBLE WORKAROUND by my ridiculous addon:
http://www.kristian-hermansen.com/code/disable.offline.mode/disable.offline.mode.html

Just install the Firefox extension I developed and you will never see the "Offline Mode" problem again. Email me if you have any problems with this XPI. Enjoy... :-)

[Alexander Sack (asac)]

On Sun, Jul 06, 2008 at 01:00:27PM -0000, Kristian Erik Hermansen wrote:
> BEST POSSIBLE WORKAROUND by my ridiculous addon:
> http://www.kristian-hermansen.com/code/disable.offline.mode/disable.offline.mode.html
>
> Just install the Firefox extension I developed and you will never see
> the "Offline Mode" problem again. Email me if you have any problems
> with this XPI. Enjoy... :-)

Real fix to disable network manager in firefox will land in 3.0.1
update - which probably will land soon. stay tuned. Ill keep you
updated.

 - Alexander

[Peter (peterroots)]

Glad to hear a firefox fix will appear soon. Using ppp with knetworkmanager is a big improvement and it would be nice to remove the eth0 eth1 descriptions from my interfaces file to let nm look after them and show the online status on the task bar - this would be possible, once ff3 is fixed, if it were not for the fact kmail is affected by the same issue. As I mentioned previously I can send but not receive mail if nm is running and I am using ppp unless my interfaces file says my eth interfaces are dhcp (or I would guess a fixed ip). In this case mail (and ff3 work) but the task bar nm icon always shows a cable network connection and does not indicate the ppp state.
Please don't give up on nm just because ff3 gets to work properly
Thanks for your efforts on ff3 alexander
peter

[Thom Pischke (thom-pischke)]

A firefox fix will be nice (using Kristian's extension now), but what about pidgin and the other apps consulting network manager?

I don't much care HOW this gets fixed, but I hope to see a no-user-action-required fix come through soon, for all apps. I just wasted 2 hours trying to figure out why I had a nice modem connection through gnome-ppp but no internet in my apps before I finally stumbled onto this issue.

Definitely an embarassing bug for an LTS release.

[junk123 (junk123-deactivatedaccount-deactivatedaccount)]

Also having this issue with a Verizon USB720, thankfully I quickly figured it out in Firefox.

[wpshooter (joverstreet1)]

How will we know when ALL of this has been fixed ?

I have my sister waiting for a computer that I have told her that I would configure for her use on a dialup ISP basis (she has no access to broadband) and now I can not get the thing to work.

This is sort of embarrassing !!!

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

On Sat, Jul 12, 2008 at 4:46 AM, wpshooter <email address hidden> wrote:
> I have my sister waiting for a computer that I have told her that I
> would configure for her use on a dialup ISP basis (she has no access to
> broadband) and now I can not get the thing to work.
>
> This is sort of embarrassing !!!

Just use my temporary Firefox solution until they get the update into Ubuntu...
http://www.kristian-hermansen.com/code/disable.offline.mode/disable.offline.mode.html
--
Kristian Erik Hermansen
--
CISSP, CEPT, CREA, CEH, Linux+, A+, QGCS, ACSA, this is getting ridiculous...
http://kristian-hermansen.com

[.cobnet (mattias-campe)]

I just installed Ubuntu 8.04 on the computer of somebody. They are using a Speedtouch 330, so I stumbled across usb-adsl-modem-manager (https://launchpad.net/usb-adsl-modem-manager).

Although usb-adsl-modem-manager makes sure that you can connect to the internet, Firefox is always in offline mode, so the user needs to go to the File-menu to switch off this mode. This could be a problem with usb-adsl-modem-manager, firefox or the network-manager.

As I couldn't use the bug reporting tool of usb-adsl-modem-manager, I send those on the top contributors list a mail (see https://launchpad.net/usb-adsl-modem-manager/+topcontributors).

[.cobnet (mattias-campe)]

Kristian Erik Hermansen, I tried your disable.offline.mode add-on, but then I couldn't use Firefox anymore. Eg. when I type a URL and hit enter, Firefox does nothing. These same with the search bar. When I uninstalled the add-on, everything worked again (except for that annoying offline mode that I needed to manually switch off).

[MarcS (marc-schmitzer)]

@.cobnet, Kristian Erik Hermansen: I've had the same problem with the disableofflinemode add-on. Though I could get Firefox to work by checking and unchecking the offline mode item in the file menu.
So apparently the add-on removed the check mark from the item, but didn't really disable the offline-mode.

[CharlieMorrison (charlie2)]

unsubscribe <email address hidden>

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

No, my addon works in firefox 3.0 for sure :-). I have tested it and
additionally others on this thread have said it works as well. It
does not merely modify the check mark! It sets various internal
firefox variable states to disable the offline mode. If it hasn't
worked for you, then I am unsure why, but this is exactly the reason I
said long ago that depending on networkmanager for internet
connectivity is ridiculous. This bug does not only affect firefox,
but the only fix in the pipeline is for fiefox 3.0.1. Other apps will
still be affected even after that becomes available, so a "real fix"
is still missing. I have been harping on about this for months.
Since no one cared to fix the real problem, I developed a workaround
which does at least work for some people. I don't know why it fails
for you, but ensure you are running firefox 3.0 final, not the
original shipped 8.04 beta version. I also tested with backports
enabled...

On 7/13/08, MarcS <email address hidden> wrote:
> @.cobnet, Kristian Erik Hermansen: I've had the same problem with the
> disableofflinemode add-on. Though I could get Firefox to work by checking
> and unchecking the offline mode item in the file menu.
> So apparently the add-on removed the check mark from the item, but didn't
> really disable the offline-mode.
>
> --
> [MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
> state for networks that are managed outside of network manager.
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Sent from Gmail for mobile | mobile.google.com

Kristian Erik Hermansen
--
CISSP, CEPT, CREA, CEH, Linux+, A+, QGCS, ACSA, this is getting ridiculous...
http://kristian-hermansen.com

[Samuel-sidler+old (samuel-sidler+old)]

(From update of attachment 327557)
Does this need landing on mozilla-central as well?

[Mozilla (mozilla)]

(From update of attachment 327557)
That's already in mozilla-central. As written somewhere above this bug is still open because of comment #66

[Mh+mozilla (mh+mozilla)]

The fix sounds awful... isn't there a way to some detection at runtime ? Because if you happen to build with NM 0.7 and somehow users are using 0.6 (which can happen on distros), you're back to where you started...

[Mozilla (mozilla)]

I guess that's why that fix never was considered really. The currently implemented one for 3.0.1 (cvs trunk) and 3.1 (hg) is the static preference which is at least a band-aid.

[John Vivirito (gnomefreak)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

CharlieMorrison wrote:
> unsubscribe <email address hidden>
>
You need to unsubscibe yourself from bug reports please see the menu on
left hand side of bug report where it says unsubscribe

- --
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIey4Yqig4QTwcPCoRAiLHAJ4s6BjFHfsixKMJs4tDXCi45aBhkQCeM3rU
KryyZiiUDSym7dWhCH/DxJg=
=rVV5
-----END PGP SIGNATURE-----

[launcspad (weblev-deactivatedaccount)]

Firefox 3 AND Evolution AND Pidgin starts offline. No, Pidgin is looking for a connection. What I have to do is to disconnect and connect again (Pidgin). At Firefox (and Evolution) the File -> uncheck Work offline solves the problem.

Firefox 2 did not have this problem.

I use HSDPA USB modem. When connected via LAN, no problem, everything is online.

Skype recognizes the Internet correctly independent of the connection type. (Altough I don't like this program.)

Sorry, I'm not patient enough to flick trough the whole conversation. If someone has a quick solution, please show me!

[Pavol Klačanský (pavolzetor-deactivatedaccount)]

i have USB modem with chip conexant, offline mode in liferea, firefox, evolution

my interfaces:
auto lo
iface lo inet loopback

auto dsl-provider
iface dsl-provider inet ppp
pre-up /sbin/ifconfig nas0 up # line maintained by pppoeconf
provider dsl-provider

auto nas0
iface nas0 inet manual

[Karl Fischer (kmf)]

This bug is Fixed,
https://bugzilla.mozilla.org/show_bug.cgi?id=424626

[forza (rumfisken)]

This bug is NOT fixed.

Just installed 3.0.1 and the same offline mode bug. Checked the version number to make sure it was 3.0.1 and not just 3.0.

Thats it for me. I've had enough of firefox and I am looking for a better browser without this bug.

[launcspad (weblev-deactivatedaccount)]

I think this is not a firefox-bug as more online softwer have this error. (Such Pidgin, Evolution.)

Skype, "Hálózatfigyelő" (network usage icon) and Weather forecast in the panel-add-on menu recognizes if I'm online.

In my network manager icon I always see an orange triangle with "!" in the middle, independet of I'm connected or not.

I use Hungarian Vodafone HSDPA with Huaweii E220 USB modem, Ubuntu 8.04 and Firefox 3.

[xtsbdu3reyrbrmroezob (xtsbdu3reyrbrmroezob)]

You can use seamonkey instead. I understand why you are upset. I
yelled and yelled long before ubuntu hardy was released, but no one
fucking listened to me. I told them that this bug would be the bane
of the lts release. It is absolutely ridiculous to base network
connectivity on a tool that does not function. For most people these
days, firefox is their OS. You break that and you piss a lost of
people off. However, they decided to break more than firefox it
seems. The only way to fix this bug is to agree that relying on NM to
query online status is not sufficient. All apps that rely on NM
should be changed to use a more reliable status query api...

On 7/17/08, forza <email address hidden> wrote:
> This bug is NOT fixed.
>
> Just installed 3.0.1 and the same offline mode bug. Checked the version
> number to make sure it was 3.0.1 and not just 3.0.
>
> Thats it for me. I've had enough of firefox and I am looking for a
> better browser without this bug.
>
> --
> [MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
> state for networks that are managed outside of network manager.
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Sent from Gmail for mobile | mobile.google.com

Kristian Erik Hermansen
--
CISSP, CEPT, CREA, CEH, Linux+, A+, QGCS, ACSA, this is getting ridiculous...
http://kristian-hermansen.com

[Mozilla-hachi (mozilla-hachi)]

Someone marked my other bug, 441491 (https://bugzilla.mozilla.org/show_bug.cgi?id=441491) as a duplicate of this bug, and now that they're filed together it needs to be included in this discussion.

When using the profile manager, you can pick 'Work offline' or leave it unchecked, which is a user input decision. Despite that choice firefox will still consult network manager and change your decision even if you didn't want it to.

Effectively, if you are using network manager properly and are online, starting firefox and choosing 'work offline' will still land you online and loading the pages over the network, even though you actively tried to tell firefox not to do this.

[launcspad (weblev-deactivatedaccount)]

This bug still exist in FIREFOX but doesn't appear in SEAMONKEY.

This bug still exist in PIDGIN but doesn't appear in AMSN.

Planning to change to SeaMonkey.

[Alexander Sack (asac)]

launcspad: yeah, thats because its a NM bug :) ... anyway, 3.0.1 lets you set a preference called toolkit.networkmanager.disable ... so if you dont want the NM online state to be considered in firefox go to about:config, and set that preference to true.

[Alexander Sack (asac)]

i added two workarounds to the summary. The first is for firefox, the second should make NM to always expose "online" as state.

Could someone please verify that those work and comment here?

[Willian (wiltave-zipmail)]

I agree...
I'm having the same bug.

[Alexander Sack (asac)]

On Thu, Jul 17, 2008 at 11:41:51AM -0000, forza wrote:
> Thats it for me. I've had enough of firefox and I am looking for a
> better browser without this bug.
>

These kind of statements dont make a difference and dont contribute
anything here. Please keep them out of bugs.

 - Alexander

[launcspad (weblev-deactivatedaccount)]

Alexander: the second workaround did not work. The first (about: config) I don't know how. Please tell me more details! (Step-by-step.) Thanks!

[Alexander Sack (asac)]

On Sun, Jul 20, 2008 at 07:07:11PM -0000, launcspad wrote:
> Alexander: the second workaround did not work. The first (about: config)
> I don't know how. Please tell me more details! (Step-by-step.) Thanks!
>

Please post your /etc/network/interfaces file for the (not-working)
2nd-workaround attempt.

for 1 you go to about:config (in firefox location bar); and use the
right mouse button somewhere in the config table you will see to say "
New -> Boolean".

Then you use the preference name i said and say "true".

For that to work you need to be sure to use firefix 3.0.1. you can
check the version by running

dpkg -l firefox-3.0

on a terminal or in firefox in Help -> About.

 - Alexander

[heimlicher (heimlich)]

on 3.0.1 the bug is present. ff still starts in offline mode.

I use umtsmon to establish a ppp connection over umts, networkmanager is not involved. Distro is suse 10.3

[launcspad (weblev-deactivatedaccount)]

The Firefox workaround works! Thanks a lot, now starts my Firefox ONLINE with USB modem.

My /etc/network/interfaces file is:

auto lo
iface lo inet loopback
iface eth1000 inet dhcp

# And this 3 lines are followed by lines with "#" at the beginning -- I think, these are only comments.

[Kombainerkinoman (kombainerkinoman)]

ff 3.0.1, patch works incorrectly. With VPN-connection firefox always starts offline.

debian lenny

[Lorenzo-colitti (lorenzo-colitti)]

The patch is working correctly. To fix this problem, you need to go to about:config and set the pref "toolkit.networkmanager.disable" to true.

[Kombainerkinoman (kombainerkinoman)]

Really works, thanks.

Ебанулись на отличненько :)

[helios (martin-lichtvoll)]

Is this patch included in Firefox 3.0.1? I updated to iceweasel 3.0.1-1 in Debian. And I have toolkit.networkmanager.disable set to true. Network Manager from network-manager 0.6.6-2 Debian Package is running.

Still Iceweasel insists on offline mode after startup.

Previously I used the following hacks I have been recommended to try on debian-user-german mailinglist:

prefs.js:user_pref("browser.offline", false);
prefs.js:user_pref("offline.statup_state", "4");

Especially the later one appeared to work with iceweasel 3.0~rc2-2, but it didn't work anymore with 3.0.1 and I removed those two entries.

I will file Debian bug report, too. I think this gotta be fixed *before* Debian Lenny release. Current behavior IMHO is absolutely ridicolous.

[helios (martin-lichtvoll)]

I found related upstream bug report for Network Manager:

http://bugzilla.gnome.org/show_bug.cgi?id=418745

I also filed Debian bug reports that Iceweasel does not seem to respect toolkit.networkmanager.disable set to true in my case:

http://bugs.debian.org/491822

And about the behavior of Network Manager which IMHO is not helpful for users wanting to configure the network their way and using Network Manager for just some interfaces. Or scenarios where Network Manager simply does not support all connections:

http://bugs.debian.org/491826

I hope a good solution can be found that offers simplicity, but also does not force all-or-nothing concepts on users with a strong desire of choosing themselves which software they let manage a certain interface.

[Roc-ocallahan (roc-ocallahan)]

As I mentioned way back in comment #32, the correct solution is to fix NetworkManager so its StateChange signals are reliable. If there is no way to make its StateChange signals reliable, then it shouldn't send any.

I actually think we should disable this feature by default until NetworkManager is fixed.

[helios (martin-lichtvoll)]

I fully agree, Robert, but then thats something for upstream of Network Manager to handle. Apart from the part to at least be able to disable Network Manager support in Iceweasel for now. I have not been able to with Debian's Firefox variant Iceweasel. See: http://bugs.debian.org/491822

Upstream has its own bug report about this issue:

http://bugzilla.gnome.org/show_bug.cgi?id=418745

See my comment there

http://bugzilla.gnome.org/show_bug.cgi?id=418745#c13

[A-sloman (a-sloman)]

(In reply to comment #104)
> As I mentioned way back in comment #32, the correct solution is to fix
> NetworkManager so its StateChange signals are reliable. If there is no way to
> make its StateChange signals reliable, then it shouldn't send any.

The best solution is NOT to rely on any particular tool for managing network connections, but to specify a protocol that can be used by ANY tool that is properly designed.

Hard-wiring a link to something as specific as Network manager, in a tool that is as widely used as Firefox seems to me to be quite misguided.
Compare email: I can use all sorts of email tools to communicate with all sorts of different email servers, because there are well defined protocols.
It would be totally wrong for any widely used tool to assume that everyone uses Thunderbird for reading and sending email, for example.

The great benefit of the unix/linux philosophy is that if protocols are properly designed, users and developers of particular packages can have a lot of freedom in choice of particular tools, interfaces, etc.

E.g.I have not found NetworkManager at all useful, though in some contexts I do find wlassistant useful for connecting with wireless services that don't use wpa. For wpa I prefer to use my shell scripts to launch wpa_supplicant. For static wired connections at home I use yet another mechanism.

As far as I can tell from documentation for NM on the internet, not even the developers (RedHat) expect it to be universally used on linux: it will not meet everyone's needs. So Firefox should not attempt to force people to use it.

If firefox is going to try to take action depending on what network channels happen to be working then it should interrogate the network interfaces, not a tool that only some people use.

> I actually think we should disable this feature by default until NetworkManager
> is fixed.

It should be permanently disabled since there will never be a guarantee that everyone uses NM.

I doubt that NetworkManager will *ever* have the universal role that would justify Firefox relying on it. So, at most this dependency on NM should be an option that can be turned on by people who like to use it. It should not be on by default.

I am not a networking expert just a user: I use linux all the time, in a variety of contexts and have mechanisms that work fine, without ever requiring NM. Firefox should not force me to start using NM if it does not do what I want. If I accidentally turn NM on Firefox should ignore it unless I specifically request it to use NM.

[Roc-ocallahan (roc-ocallahan)]

(In reply to comment #106)
> Firefox should not force me to start using NM if it does not do what I
> want.

We're not forcing anyone to start using NM. If NM is not running, Firefox behaves exactly as if this feature was disabled.

If someone produces a protocol for communicating network status that's more widely deployed than NM, and doesn't require polling, and doesn't rely on unstable or Linux-only kernel interfaces, we'll use it. Let me know when that happens.

[msmalin (msmalin)]

The 'iface eth1000 inet dhcp' trick didn't quite wok for me, but I'm not entirely sure I have the same issue. I'm using Ubuntu 8.04 with a wireless connection (Intel 3945), and I use Opera rather than firefox, and what I've been experiencing is when I boot Ubuntu, the network manager applet shows "Networking Disabled" - I can't view SSIDs, it doesn't give me the option to create a network or manually configure a network, nothing. I run "sudo dpkg-reconfigure network-manager" and it starts behaving normally.

So, it almost seems that whenever I shut down the laptop, something isn't getting cleared up, and when I boot it back up, whatever didn't get reset is jacking up the configuration so that it thinks networking is disabled.

[cubbie (lees-safe-mail)]

I have Linux Mint Elyssa which is based on Ubuntu Hardy. I use dial-up modem with serial to usb connector. There wasn't a way for me to create a connection via Network Administration Tool>Network Settings as there is no ttyUSB0 choice (there is in KPPP) so I use wvdial to connect to the internet. That means I'm not always connected. Hello, there are some of us that still use dial-up.

Firefox 3 gives me the same offline mode problem.

I fixed it by purging
network-manager, which also purged network-manager-gnome.

Now Firefox 3 starts up as it used to in previous versions without any problems. I decided to remove network-manager as it states in the description for this utility "NetworkManager attempts to keep an active network connection available at all
times." Well, that may be all well for cable and wireless connections, but not for dial-up. I also didn't like to see it in my panel with the little red x, as it never found a connection for when I would use dial up. So, it's partly a problem with NM as well.

[John Vivirito (gnomefreak)]

cubbie wrote:
> I have Linux Mint Elyssa which is based on Ubuntu Hardy. I use dial-up
> modem with serial to usb connector. There wasn't a way for me to create
> a connection via Network Administration Tool>Network Settings as there
> is no ttyUSB0 choice (there is in KPPP) so I use wvdial to connect to
> the internet. That means I'm not always connected. Hello, there are
> some of us that still use dial-up.
>
> Firefox 3 gives me the same offline mode problem.
>
> I fixed it by purging
> network-manager, which also purged network-manager-gnome.
>
> Now Firefox 3 starts up as it used to in previous versions without any problems. I decided to remove network-manager as it states in the description for this utility "NetworkManager attempts to keep an active network connection available at all
> times." Well, that may be all well for cable and wireless connections, but not for dial-up. I also didn't like to see it in my panel with the little red x, as it never found a connection for when I would use dial up. So, it's partly a problem with NM as well.
>
>
Doesnt linux mint have their own bug tracker?

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

[Springnuts (simon-springnuts-orangehome)]

Hi Alexander

Thanks for suggestions.

Sadly neither workaround works for me. Probably as I am using an Orange linebox - using the method described here http://www.orangeproblems.co.uk/phpBB2/viewtopic.php?p=19235&sid=2975a93d5718ea39cf1a04afd0de8d98 as the livebox is odd. My Hardy Heron is still waiting for the livebox key (it does not realise it is already connected) - which may be why it thinks it must be offline. Confused? I am!

Regards

Springnuts

[Stevemozbug (stevemozbug)]

First time user of bugzilla today, apologizing for any resulting
rough edges.

424626 is described in the Release Notes for 3.0.1 as having been
fixed, but, it has not been fixed as far as I can observe on my system
(details below).

As best I can tell the present "fixed 1.9.0.1" status of 424626,
is/was the basis for the 3.0.1 ReleaseNotes wording.

A couple days ago I installed Ubuntu 7.0.4 i386 (Desktop) from scratch
using a CD sold by linuxcentral. Then, used synaptic etc. to obtain
and apply all updates. Hence, 'uname -a' now says "2.6.20-17-generic
#2 SMP Thu Jul 10 00:05:43 UTC 2008 i686 GNU/Linux".

Subsequently downloaded and installed Firefox 3.0.1 manually; because
the native Ubuntu mechanisms do not understand that any Firefox rev
higher than 2.* might exist and warrant downloading/installation.

I am at home, using a dialup land line connection to my ISP, and ppp
(via 'wvdial'). There is no other computer, telephone or network
gear in my home. The linux is "out of the box" except for installing
the aforementioned up-to-current-revs patches. I don't know whether
NM is running, nor how to determine whether it is running. I am a
"simple end user" when it comes to linux.

When I startup Firefox, it is in Offline mode. I am forced to uncheck
the "Offline" box in the menu, else Firefox will not be able to access
internet sites. This behavior, I believe, is exactly the unwanted
behavior described in the Summary line for 424646. That is why I say,
it has not been fixed.

If "you" (the maintainer(s)) understand that the unwanted behavior
is still occurring, please amend the ReleaseNotes and the underlying
status code for 424646, to reflect that the bug has not been fixed.
Or let me know where/how to file an issue directly to someone who
maintains the release notes, if that is the usual mechanism for correcting them.

It appears, though, that possibly the maintainer(s) may be declining to
fix the bug under the premise that "it does not deserve fixing" -- or
however you might summarize that kind of argument -- and that leaving
users in the situation of working around the bug by either unchecking
the Offline box, or editing about:config (too dangerous for an
simple end user?) may be the most advisable approach for now.
I don't happen to agree with that view. But even if you hold that view,
I don't believe it is possible to justify calling the bug "fixed".
It has not been fixed!

[Tyler Downer (tyler-downer)]

If this bug is fixed, can we get confirmation, and change resolution of FIXED? @Steve, I am referencing your bug, Bug 449054

[Jo-Erlend Schinstad (joerlend.schinstad-deactivatedaccount)]

I'm also using a CDMA connection using PPP and Firefox always starts in offline mode. This is extremely annoying, but not really a big problem. However, this also means that no Prism-applications work at all, because it also starts in offline mode, and doesn't have a way to switch.

[Alexander Sack (asac)]

On Tue, Aug 12, 2008 at 12:09:08PM -0000, Jo-Erlend Schinstad wrote:
> I'm also using a CDMA connection using PPP and Firefox always starts in
> offline mode. This is extremely annoying, but not really a big problem.
> However, this also means that no Prism-applications work at all, because
> it also starts in offline mode, and doesn't have a way to switch.
>

we have builds for NM 0.7 in ~network-manager PPA .... you could try
that to connect to CDMA.

if you try, please report your findings like outlined here:

 http://www.asoftsite.org/s9y/archives/149-Network-Manager-0.7-bug-reporting-+-3G-hardware-testing.html
 - Alexander

[Stevemozbug (stevemozbug)]

(In reply to comment #109)
> If this bug is fixed, can we get confirmation, and change resolution of FIXED?
> @Steve, I am referencing your bug, Bug 449054
>

In reply to comment #109 about bug 424626 and comments #1 and #2 about bug 449054 (which seeks to get the documentation to reflect the fact that this bug has not been fixed):

Subsequent to filing 424626 about the bug behavior being observable under
Ubuntu 7.0.4, I have installed Ubuntu 8.0.4 and updated it to where 'uname -r' says " 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux".
Likewise updated all other items that are understood by the update manager
as being available to grab and install.

Same buggy behavior is still observable, there, for Firefox 3.0.1.

Had to install Firefox 3.0.1 manually, as the native Ubuntu mechanism does not yet understand that 3.0.1 exists.

[Phuah Yee Keat (ykphuah)]

I have hacked network-manager to check every second whether any interface is up or not, besides the loopback interface. It worked perfectly for my ppp connection. Both firefox and pidgin starts up with the proper state, and even get notified when my ppp connection dies.

Comments welcomed.

Note that trying out NM0.7 will not solve my problem, as I am using bluetooth DUN and NM0.7 does not supports that yet.

Cheers.

[Hg42 (hg42)]

I agree with Steve that applications should use (established!) protocols and standards to talk to the OS. They shouldn't try to rely on software which is far from a stable and complete state. INstead they should use the right level of protocols.

Network manager is just a tool, to ease connecting to the outside world, but it is much too high level to get a reliable statement from it if a connection to some sites is possible or not.

If NM controls the default route, it is even possible to connect to some sites via non-default routes, e.g. to allow only some sites for children etc.

So IMHO asking NM is wrong.

I think to detect complete isolation from outer network you can only ask the same level of APIs you are using to communicate.
If NM would ask this same low level API it might be reasonable to ask NM instead, but you should have a guaranty that it does work this way.

I strongly believe that automatisms should be nearly perfect and well tested before you drop them as a default on users. Especially if they cannot be disabled. Microsoft has often made this mistake and I have already spent a lot of time to these kind of problems. I don't want to see this behaviour in linux.

I am mainly using linux, because I don't want to be forced to do things the way the producer thinks. I am probably not in mainstream, so this is very important for me.

As someone else already wrote, FF3 makes an automatic decision about the offline state and overrides the user's choice. I don't think it is even necessary to have this automatic behaviour.

Instead FF3 could ask the user if he wants to go offline, when a minimum count of connection attempts failed. Then a user gets the chance to correct the network state before continuing. This way he doesn't need to reload all those tabs, just because the network fails for a moment. Also, if there are tabs which failed to load and the user disables offline mode, FF3 could reload those tabs itself (or ask before).

[Roc-ocallahan (roc-ocallahan)]

Created an attachment (id=336272)
disable NM by default

Clearly NetworkManager can't be trusted, so we have to disable this by default. If distros feel that their NM can be trusted, they can turn this back on.

This sucks, but there is nothing else we can do right now. The Linux platform just has no efficient, reliable way to get this information.

[Roc-ocallahan (roc-ocallahan)]

(In reply to comment #111)
> Network manager is just a tool, to ease connecting to the outside world, but
> it is much too high level to get a reliable statement from it if a connection
> to some sites is possible or not.

NetworkManager claims to offer such an API. If there's a way to use lower-level APIs to get the information, it could use those APIs to make its API reliable. If there is no way to make its API reliable, it shouldn't offer the API.

[Alexander Sack (asac)]

could you plese minimize your patch (e.g. the .orig files are included for instance).

Do you also check whether the interface has an IP assigned?

[Alexander Sack (asac)]

NM 0.7 should fix most use cases. But i admit that there are still missed cases, which i am in favour of forcing NM to interpret as online as as any _unmanaged_ device has an ip.

[Phuah Yee Keat (ykphuah)]

Here you go:
1. its a quilt patch
2. using libnl (using existing structures from nm-netlink-monitor.c)
3. minimal changes
4. checks for POINTOPOINT in the flags (this can be easily removed, but I guess most of us have problems with ppp devices)
5. only handle unmanaged devices
6. utilize the modem_active flag within the data class.

Cheers.

[RarSa (rarsa)]

I don't understand why there is still an insistense on this bug being an edge case.

There are many situations where NM has to be disabled or ignored. PPP, rutilt, manual configuration (static IP).

I find that relying on an optional component is quite heavy handed.

Work Offline should be a user option. not automatically set up.

Alternativelly there should be an option (not hidden) where the user can check if he/she wants to rely on the NM for connectivity.

Having it always check the NM is missguided. This is a bug.

[Roc-ocallahan (roc-ocallahan)]

(In reply to comment #114)
> I don't understand why there is still an insistense on this bug being an edge
> case.
>
> There are many situations where NM has to be disabled or ignored. PPP, rutilt,
> manual configuration (static IP).

Not sure about PPP, but the other situations are edge cases. However, breaking things by default for those cases is not acceptable, so I'm planning to disable NM usage by default.

> I find that relying on an optional component is quite heavy handed.

1) There is no "non-optional" component capable of doing what we need. That is a weakness of the Linux (or GTK if you prefer) platform.
2) We don't rely on NetworkManager in order to operate. All we rely on is that IF it is present, it tells us the truth. Unfortunately it doesn't; that's just a fixable bug in Networkmanager and not our fault. Of course since the bug isn't fixed, it is our fault to trust NetworkManager, so we should stop doing that.

> Work Offline should be a user option. not automatically set up.

No, it's very useful to have it work automatically. We have that for Windows and people want it on all platforms. I'm 100% sure that when we turn this off by default for Linux, people will start to complain that Firefox doesn't have feature parity on Linux and so obviously Mozilla hates Linux.

> Alternativelly there should be an option (not hidden) where the user can check
> if he/she wants to rely on the NM for connectivity.

Most people who need that would never find it.

> Having it always check the NM is missguided. This is a bug.

Now that I know more about the state of NetworkManager, I agree.

[Hg42 (hg42)]

I don't understand, why offline mode should be switched automatically...

What is the benefit of doing this automatically?

I think most people are always online and therefore don't want firefox to go to offline mode silently. Loosing connection is usually unintentionally and shouldn't be punished by reloading all pages etc.

I think it is irrelevant, whether you ARE online (or don't), but instead it is relevant if you WANT to be online (or don't).
I assume, network-manager doesn't tell your intention but only tells the current online state, intentionally or not.

So, as a conclusion, this information doesn't tell the right thing and therefore shouldn't be used.

Feel free to correct my assumptions...

[Roc-ocallahan (roc-ocallahan)]

Pushed f2f2446cf2de.

[Roc-ocallahan (roc-ocallahan)]

(In reply to comment #116)
> What is the benefit of doing this automatically?

It's very convenient when a machine loses or acquires network access often.

> I think most people are always online and therefore don't want firefox to go
> to offline mode silently.

Not true at all. Mobile people with laptops frequently transition between online and offline. It's stupid to have to manually tell Firefox when this is happening when the system already knows.

> Loosing connection is usually unintentionally and
> shouldn't be punished by reloading all pages etc.

We don't reload all pages when changing online/offline state.

> I think it is irrelevant, whether you ARE online (or don't), but instead it is
> relevant if you WANT to be online (or don't).
> I assume, network-manager doesn't tell your intention but only tells the
> current online state, intentionally or not.

An application that can either work locally or contact a server, such as an offline-enabled Web email application, needs to know whether you ARE online, not whether you WANT to be online, in order to choose the best strategy for saving email, for example. The same goes for Firefox choosing whether to try to load pages or just get them from the cache. Knowing whether you "want" to be online is not useful at all.

[Hg42 (hg42)]

> Mobile people with laptops frequently transition between
> online and offline. It's stupid to have to manually tell Firefox when this is
> happening when the system already knows.

ok, I understand and accept this use case

Then we have two different situations, which require two different switches in the UI.

> We don't reload all pages when changing online/offline state.

that's exactly the problem I'm referring to here. When firefox goes online again I have to reload all relevant pages manually, because cache contents doesn't help me in many cases (think of bug-trackers, bank accounts, etc.).

So, in my use case (always wanting to be online with unwanted interruptions) firefox should inform me when failing to load a page and should NOT go offline but instead should try to load the missing page again when the connection comes back. In this case the "WANT a connection" state is relevant and after that also the "HAVE a connection" state.

so we have four situations:

connection firefox
WANT HAVE action
 x x load page from net
 x - wait for connection, perhaps load page from cache and inform user
 - x load page from cache?
 - - load page from cache

the WANT state could be the inverted offline flag in firefox

[Matti-mversen (matti-mversen)]

*** Bug 434941 has been marked as a duplicate of this bug. ***

[Alexander Sack (asac)]

thanks for your patch. I would like to consider this. Just one comment for now:

+nm_device_other_update_ppp (NMData *data,
+ gboolean is_connected)

isnt that a new function which should be declared in some header?

Is it only ppp that causes issues? I think the most failsafe way would be to say that once we have an interface with an IP, we are "not-offline". You think you could extend your 0.6 patch accordingly?

Further, we need a similar approach for NM 0.7. The other heuristic we could use would be to add a new "non-offline" state (MAYBE_OFFLINE), which is used instead of online if there is any unmanaged device. Combining this with the IP-is-set heuristic above, could make offline state more accurate even.

Feel free to ping me in #ubuntu-mozillateam or -devel to get all this sorted out and landed in intrepid (and hardy for 0.6.6).

Thanks a lot.

[Alexander Sack (asac)]

all this is still not a firefox issue. upstream backedn out NM support in development head. but once we have the proposed patches in upstream NM tree, we hopefully can enable that feature everwhere again.

[Alexander Sack (asac)]

i would like to get a solution for NM in intrepid and hardy.

[Alexander Sack (asac)]

milestoning NM intrepid task for 8.10 final.

[Alexander Sack (asac)]

options we have for pidgin are a) drop NM support and b) wait for fixed NM. Obviously i prefer b). keeping task open anyway.

[Mackenzie Morgan (maco.m)]

It's not just with ppp. I use iwconfig and dhclient to connect to WEP networks due to some outstanding bugs with iwl*+NM+WEP, and Firefox and Evolution are in Offline mode when I do that.

[Phuah Yee Keat (ykphuah)]

Changes to the previous patch:
- the function nm_device_other_update_ppp is changed to nm_device_update_unmanaged and defined in the header file
- now it monitors all unmanaged devices instead of just ppp devices
- now it checks whether the unmanaged device have an IP address before signaling as online
- added a new flag unmanaged_active (mimicking modem_active) that store whether we are online or not
- (untested) handle cases where there are more than one unmanaged devices and one of them is online. (This becomes an issue after I switched to netlink)

[Phuah Yee Keat (ykphuah)]

Sorry for two patches in quick succession. After some thought and testing, this is a better patch.

[Shellster (pwd-manager)]

I found an easy solution to the problem. Just remove the network manager package and the associated gnome package. Then your network setting will rely solely on /etc/network/interfaces like that ought to.

[Eric Lee Elliott (eric-eric-elliott)]

On Monday 06 October 2008 16:57:29 Shellster wrote:
> I found an easy solution to the problem. Just remove the network
> manager package and the associated gnome package. Then your network
> setting will rely solely on /etc/network/interfaces like that ought to.

I found an easy solution, revert to Firefox 2.

[Mackenzie Morgan (maco.m)]

Neither of those is anything close to a solution. Removing network manager breaks things for people that sometimes use the command line and sometimes use network manager (like me). And changing Firefox versions won't do anything about Evolution's "Work Offline" issue, now will it?

[Ryan Waldroop (ryan.waldroop)]

I just upgraded to Intrepid and NM 0.7 works wonderfully for me. It
automatically detects my Bluetooth Pan (no more hacking around to set it up!
:-D ) and everything starts online as it should. Only problem is it is not
detected as a Mobile Broadband connection, but who cares as long as I get
proper results (i.e. - I'm recognised as online)?

IMO, Network Manager 0.7 needs to be backported to Hardy by the 8.04.2
release, if not sooner.

[Alexander Sack (asac)]

we still need some code for NM 0.7 that makes NM online when any unmanaged device has an IP. see bug 279737 which is more a less a dupe of this.

[Alexander Sack (asac)]

Phuah, you think we could start with porting your patch to NM 0.7 and if that works well try to get your patch into hardy?

[Tom Kirby (tc-kirby)]

I'm getting this problem in Intrepid with NM 0.7. This might be because I have the following setup:

eth0: wired Ethernet, always connected
eth1: used for a wireless device that is currently unplugged

Will this be fixed before Intrepid comes out?

[Eduard Wulff (mail-eduard-wulff)]

confirmed here in intrepid when connecting via wvdial with my mobile

3.0.3+build1+nobinonly-0ubuntu1

[Alexander Sack (asac)]

(intrepid) network-manager fix committed to 0.7 packaging branch (rev 2933). See Related Branches section of this bug.

[yamo (stephane-gregoire)]

Hi I'm using intrepid and I think I have a little bug on Network-manager it said that I'm not connected and so firefox is offline and seamonkey doesn't matter of network manager and let me get my mail go on internet ....

Applet NetworkManager 0.7.0

 lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu intrepid (development branch)
Release: 8.10
Codename: intrepid

 uname -a
Linux ubuntu 2.6.27-7-generic #1 SMP Fri Oct 10 03:55:24 UTC 2008 i686 GNU/Linux
yamo@ubuntu:~$ n

You have made a great work on Intrepid Ibex :)

[Launchpad Janitor (janitor)]

This bug was fixed in the package network-manager - 0.7~~svn20081008t224042-0ubuntu2

---------------
network-manager (0.7~~svn20081008t224042-0ubuntu2) intrepid; urgency=low

  * more ifupdown compatibility: we maintain /var/run/network/ifstate
    in network manager dispatcher script. This fixes a bug in the
    nfs init script that uses /var/run/network/ifstate to determine
    whether all required devices are properly up.
    - update debian/network-manager-dispatcher.script
  * fix LP: #191889: [MASTER] [WORKAROUND] "Offline Mode" feature fails to
    detect proper online state for networks that are managed outside of
    network manager; we fix this by using NM_STATE_CONNECTED when unmanaged
    devices exist.

 -- Alexander Sack <email address hidden> Sat, 11 Oct 2008 14:25:55 +0200

[Jonathan Blackhall (johnny-one-eye)]

I see that indeed it was fixed. However, now I'm unable to access network manager (it doesn't show up in the system tray or System->Administration). Is this permanent? Or will we eventually be able to control the ethernet devices using NM?

[Alexander Sack (asac)]

jonathan, nm manager should be in the tray. maybe relogin. if that doesnt work, please ensure that NetworkManager process is running.

However, if you have configurations in /etc/network/interfaces and you want NM to manage them you have to turn on managed=true in /etc/NetworkManager/nm-system-settings.conf.

This is an experimental mode in intrepid though.

[Jonathan Blackhall (johnny-one-eye)]

Logging out didn't help. I tried reinstalling network-manager and
network-manager-gnome, it prompted me to restart, which I did, and still
nothing. I went to my Sessions Preferences and the Network Manager Applet
was listed there with a command "nm-applet --sm-disable"

I checked my System Monitor Processes and nm-applet appears to be running,
but just to try I killed it and ran sudo nm-applet --sm-disable. Still
nothing.

I thought that network manager was different than nm-applet actually, but I
wasn't sure. If that's the case, I don't know how to start network
manager. I checked Services and Session Preferences and didn't find
anything helpful in either (besides the Network Manager Applet I mentioned).

I also find it weird that I can't access it via System -> Administration
anymore... Any thoughts? I can provide debugging if you let me know what
you need (and how to get it).

On Sat, Oct 11, 2008 at 7:20 PM, Alexander Sack <email address hidden> wrote:

> jonathan, nm manager should be in the tray. maybe relogin. if that
> doesnt work, please ensure that NetworkManager process is running.
>
> However, if you have configurations in /etc/network/interfaces and you
> want NM to manage them you have to turn on managed=true in
> /etc/NetworkManager/nm-system-settings.conf.
>
> This is an experimental mode in intrepid though.
>
> --
> [MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
> state for networks that are managed outside of network manager.
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Mozilla Firefox Browser: Fix Released
> Status in NetworkManager: Confirmed
> Status in USB ADSL Modem Manager for Gnome, written in Python: New
> Status in "empathy" source package in Ubuntu: New
> Status in "evolution" source package in Ubuntu: Invalid
> Status in "firefox-3.0" source package in Ubuntu: Invalid
> Status in "network-manager" source package in Ubuntu: Fix Released
> Status in "pidgin" source package in Ubuntu: Confirmed
> Status in empathy in Ubuntu Hardy: New
> Status in evolution in Ubuntu Hardy: Invalid
> Status in firefox-3.0 in Ubuntu Hardy: Invalid
> Status in network-manager in Ubuntu Hardy: Triaged
> Status in pidgin in Ubuntu Hardy: Confirmed
> Status in empathy in Ubuntu Intrepid: New
> Status in evolution in Ubuntu Intrepid: Invalid
> Status in firefox-3.0 in Ubuntu Intrepid: Invalid
> Status in network-manager in Ubuntu Intrepid: Fix Released
> Status in pidgin in Ubuntu Intrepid: Confirmed
> Status in "firefox-3.0" source package in Baltix: New
>
> Bug description:
> Binary package hint: firefox-3.0
>
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=8.04
> DISTRIB_CODENAME=hardy
> DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"
> Firefox 3.0b3
> When I start firefox from the panel it always start in offline mode. I am
> connected via wireless to a network that is always on. When I want to browse
> I need to unclick "work offline"
>
> Workaround 1: (since ffox 3.0.1) ->
> set toolkit.networkmanager.disable to false in about:config
>
> Workaround 2: (make NM to be always online) ->
> add a non existing ...

[Jonathan Blackhall (johnny-one-eye)]

I just noticed that you said there should be a process called "NetworkManager". That process is not running and I don't know how to start it. I tried sudo NetworkManager but it doesn't appear to do anything.

[ichudov (igor-chudov)]

if you have it,

sudo /etc/init.d/NetworkManager start

On Sun, Oct 12, 2008 at 03:02:25AM -0000, Jonathan wrote:
> I just noticed that you said there should be a process called
> "NetworkManager". That process is not running and I don't know how to
> start it. I tried sudo NetworkManager but it doesn't appear to do
> anything.
>

[yamo (stephane-gregoire)]

Hi today the bug whith NetworManager is fixed in intrepid for me after an update :)

[Woody (mrwoodbrick)]

I am still using Hardy, and I am total newb, but the top of this post looks wrong to me:

Workaround 1: (since ffox 3.0.1) ->
 set toolkit.networkmanager.disable to false in about:config

Doesn't it make more sense to set networkmanager.disable to "true," as then would then disable firefox checking network manager? Anyway, that's what I did and it worked for me!

[Alexander Sack (asac)]

pidgin should be fixed by latest NM upload

[Alexander Sack (asac)]

empathy should be fixed by latest NM upload

[chewearn (chewearn)]

I was just setting up 3G broadband dial-up using the following setup:
- Tether from Intrepid to mobilephone via bluetooth.
- Mobile phone serve as dial-up modem.
- Using wvdial and gnome-ppp.

Once connection is established, I got a ppp0 entry from ifconfig. However, Firefox still starts in offline mode. nm-applet shows an icon wihth exclamation mark, indicating it is not aware of the ppp connection. The internet connection itself is working, once I manually set Firefox to online mode.

I have the Network Manager updated to: 0.7~~svn20081015t224738-0ubuntu1

[chewearn (chewearn)]

Additional info:
Evolution is working. It started in online mode and able to send/receive mails.
Pidgin in not working. It get stuck trying to connect.

[Jonathan Blackhall (johnny-one-eye)]

Pidgin is working here as is Empathy.

[Alexander Sack (asac)]

On Thu, Oct 16, 2008 at 03:51:19PM -0000, chewearn wrote:
> Additional info:
> Evolution is working. It started in online mode and able to send/receive mails.
> Pidgin in not working. It get stuck trying to connect.
>

please do a restart of your system, reproduce and attach the complete
syslog. also attach your /etc/network/interfaces

 - Alexander

[ideefixe (ivan-babkin)]

I also have this problem with intrepid with all updates and ppp connection over bluetooth. I have /etc/ppp/peers/ppp0, and pon and poff commands are working correctly, but network manager always thinks I'm not connected.

If this is fixed, could you please provide working example of /etc/network/interfaces, /etc/NetworkManager/nm-system-settings.conf?

Thank you.

[chewearn (chewearn)]

Alexander Sack wrote on 2008-10-21:
> please do a restart of your system, reproduce and attach the complete
> syslog. also attach your /etc/network/interfaces

Apologies for taking so long to respond, I thought I was subscribed to this bug; but I wasn't.
Attached the files you requested.

[takeda64 (takeda64)]

Reporting, because log said so :) :
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574078] ata1: EH complete
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574165] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574199] sd 0:0:0:0: [sda] Write Protect is off
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574203] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574261] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574318] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574349] sd 0:0:0:0: [sda] Write Protect is off
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574352] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.574410] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.640154] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.640161] pci 0000:00:02.0: setting latency timer to 64
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642076] PM: resume devices took 12.984 seconds
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642084] ------------[ cut here ]------------
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642087] WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176 suspend_test_finish+0x74/0x80()
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642091] Modules linked in: tun ipv6 af_packet i915 drm binfmt_misc rfcomm sco bridge stp bnep l2cap bluetooth ppdev acpi_cpufreq cpufreq_userspace cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_ondemand freq_table wmi container pci_slot sbs sbshc iptable_filter ip_tables x_tables panasonic_acpi parport_pc lp parport loop joydev pcmcia arc4 ecb crypto_blkcipher serio_raw evdev iwlagn pcspkr iwlcore psmouse rfkill led_class lbm_cw_mac80211 iTCO_wdt iTCO_vendor_support sdhci_pci sdhci mmc_core yenta_socket rsrc_nonstatic pcmcia_core tpm_infineon lbm_cw_cfg80211 tpm video snd_hda_intel tpm_bios ac output snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss battery button snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc intel_agp agpgart shpchp pci_hotplug ext3 jbd mbcache sd_mod crc_t10dif sg ata_piix pata_acpi ahci ata_generic libata scsi_mod dock sky2 ehci_hcd uhci_hcd usbcore thermal processor fan
Oct 30 15:21:48 tkdlap2 kernel: bcon tileblit font bitblit softcursor fuse
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642176] Pid: 9635, comm: pm-suspend Tainted: G W 2.6.27-7-generic #1
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642179] [<c037c406>] ? printk+0x1d/0x1f
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642186] [<c0131de9>] warn_on_slowpath+0x59/0x90
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642192] [<c014d255>] ? sched_clock_cpu+0xd5/0x170
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642197] [<c014c0af>] ? down_trylock+0x2f/0x40
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642201] [<c01324c2>] ? try_acquire_console_sem+0x12/0x40
Oct 30 15:21:48 tkdlap2 kernel: [ 7798.642207] [<c024e580>] ? kobject_put+0x20/0...

[Alexander Sack (asac)]

Derek, please open new bugs instead of posting your content to some bug you feel might be the same. In any case, your particular issue is already filed in bug 291291.

[kelargo (kelong-2000)]

I have kubuntu and everything worked great with DHCP. I wanted to go with a static IP and it does not persist.
My syslog refers to this bug.

<info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)

If my problem is a different bug, then I'll open a new bug on this issue.

I've tried uninstalling network-manager. both KDE and gnome versions. my network settings are correct.
The nameserver stays in place. but after rebooting I have to redo ifconfig (up) and add the default route.

I also get this syslog message:

[ 260.779405] network-admin[8703]: segfault at 0 ip 00007f70c0a6c110 sp 00007fffcd12f488 error 4 in libglib-2.0.so.0.1800.2[7f70c0a03000+c3000]

I'm not sure where this IP Address is being stored (192.168.0.10) my statis is 192.168.0.99.
I might have used 192.168.0.10 at one time, but not now.

HOST ALERT: gateway;DOWN;SOFT;3;CRITICAL - Network Unreachable (192.168.0.10)

Actually, I just looked at my /etc/network/interfaces and I see that it appears to be being saved- two sets of entries are in the file, now.

# cat /etc/network/interfaces
auto lo eth0
iface eth0 inet static
address 192.168.0.99
netmask 255.255.255.0
gateway 192.168.0.1
iface eth0 inet static
address 192.168.0.99
netmask 255.255.255.0
network 192.168.0.0
broabcast 192.168.0.255
gateway 192.168.0.10

let me know if I can provide any other info.

[Jeffgbaker (jeffgbaker)]

This bug still exists. I am running FF 3.0.4 on Fedora 9 and this is still an issue on my system. NM does not control my network connections. Setting toolkit.networkmanager.disable to true corrects the problem.

[Mozilla06b (mozilla06b)]

Another way around this on Fedora 9 is to use system-config-network and check the box for the network connection to allow it to be managed by NetworkManager.

[John Doe (johndoe32102002)]

Reporting because the log said so:

Nov 15 17:54:50 COMPUTER NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Nov 15 18:14:31 COMPUTER NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Nov 15 18:14:35 COMPUTER last message repeated 2 times
Nov 15 18:25:08 COMPUTER NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Nov 15 18:37:57 COMPUTER gdmsetup[23496]: Gtk-WARNING: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
Nov 15 18:37:57 COMPUTER last message repeated 6 times
Nov 15 18:41:43 COMPUTER NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Nov 15 18:41:44 COMPUTER NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Nov 16 11:01:24 COMPUTER bluetoothd[5031]: HCI dev 0 registered
Nov 16 11:01:25 COMPUTER bluetoothd[5031]: HCI dev 0 up
Nov 16 11:01:35 COMPUTER bluetoothd[5031]: Can't write inquiry mode for /org/bluez/hci0: Connection timed out (110)
Nov 16 11:01:40 COMPUTER bluetoothd[5031]: Can't write class of device: Connection timed out (110)
Nov 16 11:01:55 COMPUTER last message repeated 3 times
Nov 16 11:01:55 COMPUTER bluetoothd[5031]: Registered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Nov 16 11:02:00 COMPUTER bluetoothd[5031]: Can't write class of device: Connection timed out (110)
Nov 16 11:02:00 COMPUTER bluetoothd[5031]: Registered interface org.bluez.NetworkHub on path /org/bluez/hci0
Nov 16 11:02:05 COMPUTER bluetoothd[5031]: Can't write class of device: Connection timed out (110)
Nov 16 11:02:05 COMPUTER bluetoothd[5031]: Registered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Nov 16 11:02:05 COMPUTER bluetoothd[5031]: Registered interface org.bluez.SerialProxyManager on path /org/bluez/hci0
Nov 16 11:02:05 COMPUTER bluetoothd[5031]: Registered interface org.bluez.Service on path /org/bluez/hci0
Nov 16 11:02:05 COMPUTER bluetoothd[5031]: Adapter /org/bluez/hci0 has been enabled
Nov 16 11:02:05 COMPUTER bluetoothd[5031]: Starting security manager 0
Nov 16 11:02:11 COMPUTER bluetoothd[5031]: Can't write class of device: Connection timed out (110)
Nov 16 11:03:07 COMPUTER NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Nov 16 11:08:24 COMPUTER bluetoothd[5031]: HCI dev 0 down
Nov 16 11:08:24 COMPUTER bluetoothd[5031]: Unregistered interface org.bluez.NetworkPeer on path /org/bluez/hci0
Nov 16 11:08:24 COMPUTER bluetoothd[5031]: Unregistered interface org.bluez.NetworkHub on path /org/bluez/hci0
Nov 16 11:08:24 COMPUTER bluetoothd[5031]: Unregistered interface org.bluez.NetworkRouter on path /org/bluez/hci0
Nov 16 11:08:24 COMPUTER bluetoothd[5031]: Adapter /org/bluez/hci0 has been disabled
Nov 16 11:08:24 COMPUTER bluetoothd[5031]: Stopping security manager 0
Nov 16 11:08:25 COMPUTER bluetoothd[5031]: HCI dev 0 up
Nov 16 11:08:35 COMPUTER bluetoothd[5031]: Can't write inquiry mode f...

[mbeccaria (massibeccaria)]

I am experiencing that the network-manager is reporting my wired connection as disconnected and not managed, whenever the wired connection is changed through the "old" network-admin tool.

[Marcello Anni (marcello-anni)]

i have this issue yet, in mandriva 2009 and firefox 3.0.4, and i don't use networkmanager. hope you'll resolve this bug soon, it's very annoying.

Bye
Marcello

[Sylvain Pasche (sylvain-pasche)]

Marcello, you can now disable offline detection by going to about:config and setting toolkit.networkmanager.disable to true.

[Alexander Sack (asac)]

On Wed, Nov 26, 2008 at 11:28:50AM -0000, mbeccaria wrote:
> I am experiencing that the network-manager is reporting my wired
> connection as disconnected and not managed, whenever the wired
> connection is changed through the "old" network-admin tool.
>

Yes, in intrepid (0.7) this shouldnt make a difference. for 0.6 we
need to integrate the patch that was posted (here?).

 - Alexander

[kevin_405 (kevin-405)]

I had to workaround 1 to true not false

Workaround 1: (since ffox 3.0.1) ->
 set toolkit.networkmanager.disable to true in about:config

[kevin_405 (kevin-405)]

I had to set workaround 1 to true not false

Workaround 1: (since ffox 3.0.1) ->
 set toolkit.networkmanager.disable to true in about:config

[Eric Lee Elliott (eric-eric-elliott)]

On Wednesday 17 December 2008 21:27:47 kevin_405 wrote:
> I had to set workaround 1 to true not false
>
> Workaround 1: (since ffox 3.0.1) ->
> set toolkit.networkmanager.disable to true in about:config
Fresh install of kubuntu 8.10 with all updates has cellular modem connected
via kppp, then Firefox starting off line every start. Off line mode options do
not prevent or inhibit off line condition. Network Manager is not used or
needed but does not help problem with cellular modem as only Internet
connection.

[Alexander Sack (asac)]

On Thu, Dec 18, 2008 at 12:25:47PM -0000, Eric Lee Elliott wrote:
> On Wednesday 17 December 2008 21:27:47 kevin_405 wrote:
> > I had to set workaround 1 to true not false
> >
> > Workaround 1: (since ffox 3.0.1) ->
> > set toolkit.networkmanager.disable to true in about:config
> Fresh install of kubuntu 8.10 with all updates has cellular modem connected
> via kppp, then Firefox starting off line every start. Off line mode options do
> not prevent or inhibit off line condition. Network Manager is not used or
> needed but does not help problem with cellular modem as only Internet
> connection.
>

If you dont use networkmanager at all you probably dont need it. Not
sure if kde has proper UI for mobile broadband devices, but at least
in gnome you can use them directlyin NM (e.g. no need for kppp).

 - Alexander

[kevin_405 (kevin-405)]

Eric Lee Elliott

I have uninstalled network manager all together.. I found in Ubuntu 8.1 it is very buggy for Wifi with WPA encryption..
I have resorted to manual setup of network and and setting firefox toolkit.networkmanager.disable to true in about:config

May be u can give that a try...

Kevin

[Matti-mversen (matti-mversen)]

*** Bug 470658 has been marked as a duplicate of this bug. ***

[Fandens-oldemoder (fandens-oldemoder)]

When I set the pref "toolkit.networkmanager.disable" to true in about:config, it actually works - no more offline at startup.
Thanks!

[Klaus Thorn (klaus-trillke)]

Firefox 3.0.5 starts in offline mode, failing to detect that I am online (with a connection which Opera, ping and apt-get all know to use well).

The online connection that is not detected by firefox (nor network manager) is via UMTS, on an Asus EeePc 901GO, using wvdial and pppd. All these programs are part of an Ubuntu 8.04 Desktop wiith kernel 2.6.24-21-eeepc i686.

If all programs acted like firefox 3, I woud have had no chance to help myself, because I did not search nor find the "offline mode" in the "file" menu. I searched it in the network settings, (just a hint for the usability "experts" out there).

This issue is not only technical but political. I think it is an important aspect and I will not search another hour for the correct place for publishing it, this place is good enough:

It is obvious and reported here that the crucial user experence with firefox is crushed in many cases by this bug. It is easy to understand that improving the detection of online states will always be inferiour to just try to connect, because the latter depends on less other programs. Those programs, like all software, will have bugs and missing features, which curretly is the case. Neither do I expect Network Manager or Firefox to understand all features of wvdial or pppd nor should firefox rely on Network Manager or dbus. I think it is clear that correctly auto-enabling the offline mode is much less important than being able to use an online connection.

Despite all of this, the bug got closed, people are told that they don't write enough information, that the bug is a bug of another program, or that part of their reports have nothing to do with this bug. All of these counter-arguments do not lead to a solution but do defend the problem and the problematic decision to auto-enable offline mode due to messages from dbus, network-manager or whatever.

Changing the behaviour of Firefox (back to always start in online mode and just try to connect) isn't difficult in terms of problem-solving or programming. It was there in Firefox 2 I assume, so it is more a decision than a technical problem. Who decides? And who decides whether a technocrat, bureaucrat or service-oriented human is dealing with this problem? Do the ubuntu users have influence here? Or the firefox users? I had enough technocrats and bureaucrats giving answers in politician's style, instead of solving problems in Firefox, Openoffice etc.. So if I am part of the power deciding about Firefox and Ubuntu, just because I use it, spread the word about it and install it on dozens of machines, then I vote for starting firefox in online mode by default and for replacing the persons dealing with this bug. Wether they are paid or altruistic, they should not be able to continue to worsen this fine piece of software. It's like with the lights on my bicycIe: It should not turn off automatically, even if someone from the producers claims that the brightness sensor is the problem. Forget the sensor, just let the lights shine!

Installed packages:
Installed: firefox 3.0.5+nobinonly-0ubuntu0.8.04.1
Installed: firefox-3.0 3.0.5+nobinonly-0ubuntu0.8.04.1
Installed: firefox-3.0-gnome-support 3.0.5+nobinonly-0ubu...

[Alexander Sack (asac)]

kelargo wrote:
> # cat /etc/network/interfaces
> auto lo eth0
> iface eth0 inet static
> address 192.168.0.99
> netmask 255.255.255.0
> gateway 192.168.0.1
> iface eth0 inet static
> address 192.168.0.99
> netmask 255.255.255.0
> network 192.168.0.0
> broabcast 192.168.0.255
> gateway 192.168.0.10
>
>
probably not the cause, but you have a typo in broadcast.

[Alexander Sack (asac)]

mbeccaria wrote:
> I am experiencing that the network-manager is reporting my wired
> connection as disconnected and not managed, whenever the wired
> connection is changed through the "old" network-admin tool.
>
>
what really matters for most applications (!= the applet, which is known
to show you disconnected unless a managed device is connected) is what
you get as the "main" online/offline state when running nm-tool. So I get :

 nm-tool | head

NetworkManager Tool

State: connected

^^^ if this is connected, then all should be ok and applications started
probably assume that you are online.

[Eric Lee Elliott (eric-eric-elliott)]

Klaus,
I filed bug for FF lacking way to defeat off line mode, several months ago.
People refused to see that most users might never use or need off line mode.
People refused to change FF behavior to avoid users switching to browser with
less vexing behavior. Finally they combined my bug with bug blaming other
programs for FF being off line.
No consideration seemed to be given for default on line behavior as you
desired. Why the people in control of FF would want to have the only browser
that so discourages users is beyond my understanding.
--

God Bless You,

Eric Lee Elliott

<email address hidden> http://eric-elliott.com
800.827.5038 870.613.1398

PMB 6755, 167 Rainbow Drive, Livingston TX 77399-1067
On Tuesday 23 December 2008 17:57:34 Klaus Thorn wrote:
> Firefox 3.0.5 starts in offline mode, failing to detect that I am online
> (with a connection which Opera, ping and apt-get all know to use well).
>
> The online connection that is not detected by firefox (nor network
> manager) is via UMTS, on an Asus EeePc 901GO, using wvdial and pppd. All
> these programs are part of an Ubuntu 8.04 Desktop wiith kernel
> 2.6.24-21-eeepc i686.
>
> If all programs acted like firefox 3, I woud have had no chance to help
> myself, because I did not search nor find the "offline mode" in the
> "file" menu. I searched it in the network settings, (just a hint for
> the usability "experts" out there).
>
> This issue is not only technical but political. I think it is an
> important aspect and I will not search another hour for the correct
> place for publishing it, this place is good enough:
>
> It is obvious and reported here that the crucial user experence with
> firefox is crushed in many cases by this bug. It is easy to understand
> that improving the detection of online states will always be inferiour
> to just try to connect, because the latter depends on less other
> programs. Those programs, like all software, will have bugs and missing
> features, which curretly is the case. Neither do I expect Network
> Manager or Firefox to understand all features of wvdial or pppd nor
> should firefox rely on Network Manager or dbus. I think it is clear that
> correctly auto-enabling the offline mode is much less important than
> being able to use an online connection.
>
> Despite all of this, the bug got closed, people are told that they don't
> write enough information, that the bug is a bug of another program, or
> that part of their reports have nothing to do with this bug. All of
> these counter-arguments do not lead to a solution but do defend the
> problem and the problematic decision to auto-enable offline mode due to
> messages from dbus, network-manager or whatever.
>
> Changing the behaviour of Firefox (back to always start in online mode
> and just try to connect) isn't difficult in terms of problem-solving or
> programming. It was there in Firefox 2 I assume, so it is more a
> decision than a technical problem. Who decides? And who decides whether
> a technocrat, bureaucrat or service-oriented human is dealing with this
> problem? Do the ubuntu users have influence here? Or the firefox users?
> I had enough technocrats and bureaucrats ...

[Alexander Sack (asac)]

On Tue, Dec 23, 2008 at 11:57:34PM -0000, Klaus Thorn wrote:
> Firefox 3.0.5 starts in offline mode, failing to detect that I am online
> (with a connection which Opera, ping and apt-get all know to use well).
>
> The online connection that is not detected by firefox (nor network
> manager) is via UMTS, on an Asus EeePc 901GO, using wvdial and pppd. All
> these programs are part of an Ubuntu 8.04 Desktop wiith kernel
> 2.6.24-21-eeepc i686.
>
> If all programs acted like firefox 3, I woud have had no chance to help
> myself, because I did not search nor find the "offline mode" in the
> "file" menu. I searched it in the network settings, (just a hint for
> the usability "experts" out there).

I dont disagree ... only point i can say is that NM doesnt support
when you do things outside of NM ...

This hopefully will change in future. If we want a solution now,
someone needs to find the time to improve our "unmanaged == always
online" patch to also enforce ONLINE if there is any interface up with
IP set.

 - Alexander

[Colin Alston (colina)]

BRAVO! Firefox is my new nominee for a Darwin award.

I have this thing called a kiosk with a web-app in the background of the box. It has no network connectivity - it doesn't need to, there is this strange thing on Linux since like 1970 called loopback (for the Firefox developers, this can be found at http://127.0.0.1).

Of course Firefox wants to be in "online" mode to connect to loopback.

Did anyone consider this? Please, just get rid of this insane feature.

[Nitesh Mistry (mistrynitesh)]

>I have this thing called a kiosk with a web-app in the background of the
>box. It has no network connectivity - it doesn't need to, there is this
>strange thing on Linux since like 1970 called loopback (for the Firefox
>developers, this can be found at http://127.0.0.1).

I didn't know that linux existed in 1970 also!

On Fri, Jan 9, 2009 at 8:15 PM, Colin Alston <email address hidden> wrote:

> BRAVO! Firefox is my new nominee for a Darwin award.
>
> I have this thing called a kiosk with a web-app in the background of the
> box. It has no network connectivity - it doesn't need to, there is this
> strange thing on Linux since like 1970 called loopback (for the Firefox
> developers, this can be found at http://127.0.0.1).
>
> Of course Firefox wants to be in "online" mode to connect to loopback.
>
> Did anyone consider this? Please, just get rid of this insane feature.
>
> --
> [MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
> state for networks that are managed outside of network manager.
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Anomaly256 (anomaly256)]

Why is this 'feature' even there in the first place? The user should never have to explicitly switch between online/offline modes. The browser can either resolve and load a site or it can't, and when it can't /then/ show a warning regarding it. Forcing the user to manually re-enable the ability to browse every time their connection goes up or down is just idiotic. I'm guessing this entire concept is just legacy nonsense and has no actual logical /practical/ rationale associated with it any longer.

[Anomaly256 (anomaly256)]

can't load a live bookmark, homepage, or other external site > assume offline mode.

user tries to view an external site when in offline mode > assume online mode, try, and either leave online mode if successful or warn the user and revert to offline if not.

otherwise > assume online mode.

This flow would make using firefox on the plethora of portable 3g/2.5g/2g/wifi connected devices SO much smoother. Sure you can disable this behavior by telling firefox, through about:config, to ignore NetworkManager, but do you think average Joe Blogs will have any clue how to do this or where to find the instructions to do it? </2_cents>

[A-sloman (a-sloman)]

(In reply to comment #126)
> When I set the pref "toolkit.networkmanager.disable" to true in about:config,
> it actually works - no more offline at startup.
> Thanks!

I had done that some time ago, but when I upgraded from Fedora 9 to Fedora 10 (which installed Fedora/3.0.5-1.fc10 Firefox/3.0.5) I found Firefox had reverted to the old behaviour. I had completely forgotten how to fix this and it took me some time to rediscover it.

The facility to switch off the behaviour (going offline and preventing old web pages from being redisplayed) really should be one of the items in the preference menu which will be preserved in the user's files.

I use Firefox as a substantial extension of my working memory. I usually have several windows open (anything between 3 and about 20) each of which can have several tabs. I don't use networkmanager because my desktop PC is connected by cable to a router using a static address. If I have to restart firefox e.g. after booting, or after suspend/resume (I use tuxonice) it is a real pain to have to go through every tab in every window clicking 'try again', after deselecting 'work offline'. Who dreamed up that mechanism?

For people who have not learnt how to use "about:config", and who use multiple tabs as I do, it is essential either to make everything reconnect automatically when 'work offline' is deselected, or to have an adjacent button labelled 'retry all'. or 'reconnect all' which works only when offline is deslected.

(Ideally that should be in addition to a preference to turn off checking of network connectivity. It's a bit pointless anyway, because there can be a network failure at many locations, e.g. at the service provider, or beyond, and whether networkmanager does or does not think there is a successful connection can be irrelevant in that case.)

[Incidentally, I am finding that Firefox causes a much smaller load since I switched to Fedora 10.]

[Fandens-oldemoder (fandens-oldemoder)]

For a work-around: See Comment #28 From Mike Shaver 2008-05-26 11:45:21 PST above:

Right-click any tab, select 'Reload All Tabs'

For me the change in about:com is the only solution.

Living high up in the Andes Mountains and using a GPRS dongle, during the day time I have about 30 Kbit/s at best. Reloading 10-12 tabs often took half an hour.

[Alexander Sack (asac)]

decent offline support is really required to do enhanced stuff like pausing/resuming downloads; saying "dump offline integration with linux desktop" is not really innovation. Instead we should tackle the underlying issues that cause the bad experience here imo.

[Roc-ocallahan (roc-ocallahan)]

You mean I should fix Network Manager and take responsibility get the updates pushed out to all users?

[Roc-ocallahan (roc-ocallahan)]

Note that it's preffed off so if your distro has a working NetworkManager you can easily turn it back on.

[drizad (drizad)]

For me, I don't think it's FF3 problem. It's network-manager's problem. I could get connected to internet through PPPoE and browse normally with FF3, but network-manager applet failed to detect it as connected.

Solution (maybe temporary) with Ubuntu Intrepid 8.10:
1. remove network-manager
sudo apt-get remove network manager

2. Install wicd
http://www.ubuntugeek.com/wicd-wired-and-wireless-network-manager-for-ubuntu.html

3. When asked about wicd pubkey, just
wget -q http://apt.wicd.net/wicd.gpg -O- | sudo apt-key add -

Restart your Ubuntu as although you have remove network-manager, it can give you some error message.

Good luck!

[Alexander Sack (asac)]

On Fri, Jan 30, 2009 at 03:39:50AM -0000, drizad wrote:
>
> Solution (maybe temporary) with Ubuntu Intrepid 8.10:
> 1. remove network-manager
> sudo apt-get remove network manager
>
> 2. Install wicd
> http://www.ubuntugeek.com/wicd-wired-and-wireless-network-manager-for-ubuntu.html
>

This isnt a solution to this bug and please post such instructions
outside of the bug tracking system. Forums are a good place to put
this - and there are probably plenty of these advices there, so there
is no need at all to post this here.

Thanks!

 - Alexander

[Eric Lee Elliott (eric-eric-elliott)]

On Friday 06 February 2009 11:09:37 Alexander Sack wrote:
> On Fri, Jan 30, 2009 at 03:39:50AM -0000, drizad wrote:
> > Solution (maybe temporary) with Ubuntu Intrepid 8.10:
> > 1. remove network-manager
> > sudo apt-get remove network manager
> >
> > 2. Install wicd
> > http://www.ubuntugeek.com/wicd-wired-and-wireless-network-manager-for-ubu
> >ntu.html
>
> This isnt a solution to this bug and please post such instructions
> outside of the bug tracking system. Forums are a good place to put
> this - and there are probably plenty of these advices there, so there
> is no need at all to post this here.
>
> Thanks!
>
>
> - Alexander
This bug has not bothered me in months. Still using ATT and a Sierra 875
cellular data card to access Internet. Ubuntu 8.1 finds, installs & operates
Att connection with minimal attention & no errors. Kubuntu not as easy, not
automatic install, but rarely has off line problem. Debian KDE also stays on
line.

God Bless You,

Eric Lee Elliott

<email address hidden> http://eric-elliott.com
800.827.5038 870.613.1398

PMB 6755, 167 Rainbow Drive, Livingston TX 77399-1067

[Joel Wirāmu Pauling (aenertia) (aenertia)]

I have this issue, it appears to be caused by Network manager not being able to cope with previously defined debian interface files.

I saw this for the first time when upgrading/installing via net-installer to jaunty. lspci, lshal and nm-tool info attached . my /etc/network/interfaces is just auto eth0 etc defaults as created by deb-installer.

Only weird thing about my network is that I run ipv6 along side .( which on a side note the deb-installer does not support)

[Tom Pino (metalsmith-rangeweb)]

An easier solution, if your FF3 is updated to current, is to type
"about:config" in a blank tab. Click OK to the scary message. Type
tool in the filter line.

You will find the below one ending in false. click on the line to
change to true. This is not a FF problem but they found a fix for it
and it is an easy one for Hardy and Intrepid.

"toolkit.networkmanager.disable;true"

Tom

aenertia wrote:
> I have this issue, it appears to be caused by Network manager not being
> able to cope with previously defined debian interface files.
>
> I saw this for the first time when upgrading/installing via net-
> installer to jaunty. lspci, lshal and nm-tool info attached . my
> /etc/network/interfaces is just auto eth0 etc defaults as created by
> deb-installer.
>
> Only weird thing about my network is that I run ipv6 along side .( which
> on a side note the deb-installer does not support)
>
> ** Attachment added: "lspci, lshal and nm-tool"
> http://launchpadlibrarian.net/22404423/logs.gz
>
>

[Joel Wirāmu Pauling (aenertia) (aenertia)]

Actually this is not a firefox / nm interaction issue at all ( I have seen
this one, and know how to work around it).

It is purely network-manager failing to correctly manage network devices. It
is more an issue of not having populated device entries correctly and then
not being able to manage them through the various gui tools.

not just a FF issue.

2009/2/10 Tom Pino <email address hidden>

> An easier solution, if your FF3 is updated to current, is to type
> "about:config" in a blank tab. Click OK to the scary message. Type
> tool in the filter line.
>
> You will find the below one ending in false. click on the line to
> change to true. This is not a FF problem but they found a fix for it
> and it is an easy one for Hardy and Intrepid.
>
> "toolkit.networkmanager.disable;true"
>
> Tom
>
> aenertia wrote:
> > I have this issue, it appears to be caused by Network manager not being
> > able to cope with previously defined debian interface files.
> >
> > I saw this for the first time when upgrading/installing via net-
> > installer to jaunty. lspci, lshal and nm-tool info attached . my
> > /etc/network/interfaces is just auto eth0 etc defaults as created by
> > deb-installer.
> >
> > Only weird thing about my network is that I run ipv6 along side .( which
> > on a side note the deb-installer does not support)
> >
> > ** Attachment added: "lspci, lshal and nm-tool"
> > http://launchpadlibrarian.net/22404423/logs.gz
> >
> >
>
> --
> [MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
> state for networks that are managed outside of network manager.
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Alexander Sack (asac)]

Roc, do we have any requirements NM has to fulfill before we can enable this by default again?

Maybe we can probe for the running version and enable it by default if NM is 0.7 or later is used?

[Roc-ocallahan (roc-ocallahan)]

No, NM 0.7 will not solve the problem. AFAIK it can't manage all possible network interfaces, and even if it could there will still be people who choose to run NM but have some active interfaces not managed by NM, no matter how much we wish they wouldn't. And if we treat StateChange messages as reliable they will blame Firefox for being broken.

The NM issues are covered pretty well here: http://bugzilla.gnome.org/show_bug.cgi?id=418745#c13
I agree with Martin's comment there and have just attached a followup comment of my own, which echoes what I've already said in this bug. It seems to me that NM could enumerate the active interfaces (like ifconfig does) and detect when there are interfaces in that list that it isn't managing (and aren't loopback), and in that case, refrain from sending StateChange messages.

[Alexander Sack (asac)]

aenertia, this is not your bug. this bug is about applications thinking that you are offline, meaning pidgin doesnt try to connecte because it thinks its offline or firefox starting in offline status even though you are online. Your issue is just an applet display glitch, which is less severe and known.

[Larry Linde (linde)]

Then at least provide the option to tell FF to ignore NM status. I want FF to try to connect period.
I don't want it dependant of some other buggy POC that get pushed out and breaks core functionality.

[Jeremy Wilkins (wjeremy)]

Ok, it was reported in February, now it is well into May, Jaunty has been released already. Has anyone even tried to fix this? I think the about:config workaround above does seem to fix it for Firefox, but is there a reason why we shouldn't just force that as a default or if that isn't feasible to permit browsing to the local loopback/net addresses at least regardless of network status? NetworkManager does many great things, but making programs dependent upon it is ridiculous. It doesn't always know if a particular address will be available or not. If I am travelling and I do not have a network connection Firefox prevents me from browsing to localhost. That is plain stupid! Konqueror browses to localhost just fine without a network. I am running Jaunty with the latest updates installed, but it still isn't fixed.

[Alexander Sack (asac)]

Jeremy, the localhost problem is a valid issue and is a different bug, please file it.

Besides from that we want to use a service to determine online/offline state; this would allow us to improve user experience in many ways; the fact that network manager is not able to manage all types of connections is unfortunate, but isn't a problem for the majority of our users. For now if you are struck by this, disable the feature using about:config.

Also, be assured that we are unhappy about the current situation and are working on real solutions to the problem; one idea is to move online/offline detection to a dedicated and connection-manager-independent service that can deal with all type of connections. So stay tuned. Thanks for your patience.

[Jeremy Wilkins (wjeremy)]

@Alexander: I apologize for the terse post earlier. I love Ubuntu, especially the Kubuntu variant and all my computers run Jaunty (except for my server which is still Intrepid). My post was made at 2am my time after being up since 7am working all day, driving 2.5 hours at 4pm and working from 8pm to 1am. I was stressed and should not have posted so late. I found out the solution for the localhost problem was to switch Firefox to offline mode. It's just unfortunate that Firefox isn't smart enough to respond automatically by using a local dns test first or if an ip/ipv6 address is given within a known loop back range (this is a standard) or an ip that is local to an interface regardless of NetworkManager's status. This first seems simple to me, but maybe Firefox doesn't have sufficient privileges for the second? I'm not saying that Firefox should ignore NetworkManager, but instead it should check NetworkManager first to see if we're online since that is the fastest way to know, and fall back to the other tests as a last resort. To rely solely on NetworkManager is to cause many Web Developers (who often use the local machine as a web server), and those who use their machines in a disconnected fashion with web programs, a great disservice. We are trying to make things easier, not harder for everyone. Most people wouldn't think that you have to switch to offline mode to access localhost when you're not connected to a network. I always thought offline mode was reserved to those on cellular, satelite or dial-up connections who don't want their internet activated to reduce possible charges.
So, should I open a bug report with this information?

[jkohler2 (jkohler2)]

I have the same problem with my Acer Aspire 5315 and Zoom 3095 modem using Ubuntu 9.04

John

[hugomariani (hugo-mariani)]

I have a Dell Latitude which works both windows xp and Kubuntu. I had Kubuntu 8.04 and I have upgraded tu 9.04 (jaunty). When I used 8.04 I had configured my wireless card (a Broadcom BCM4312) with its Windows module by Ndiswrapper. After a little bit of work it was worked fine. But when I change to Jaunty I can't connect with AP with WEP encryption. Even I try to install and use the old application Knetworkmanager, but without successful results.

There is part of my syslog:

Jun 8 12:22:01 D830 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Jun 8 12:22:08 D830 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Jun 8 12:23:51 D830 NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Jun 8 12:24:00 D830 NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/Connection/0 failed to activate (timeout): (0) Connection was not provided by any settings service

And with Knetworkmanager, launched by console:

Processing Setting 'ipv4'
  Attach setting 'ipv4'
    ignore-auto-dns: <bool>false</bool>
    ignore-auto-routes: <bool>false</bool>
    method: <string>auto</string>
  Processing Setting '802-11-wireless'
  Attach setting '802-11-wireless'
    mode: <string>infrastructure</string>
    security: <string>802-11-wireless-security</string>
    ssid: <list> <byte>83</byte> <byte>105</byte> <byte>115</byte> <byte>116</byte> <byte>101</byte> <byte>109</byte> <byte>97</byte> <byte>115</byte> </list>
  Processing Setting '802-11-wireless-security'
  Attach setting '802-11-wireless-security'
    group: <list> <string>tkip</string> <string>ccmp</string> </list>
    key-mgmt: <string>none</string>
    pairwise: <list> <string>tkip</string> <string>ccmp</string> </list>
    wep-tx-keyidx: <int32>0</int32>
  Processing Setting '802-1x'
  Setting '802-1x' is empty, discarding
ConnectionSettingsDialogImpl::~ConnectionSettingsDialogImpl

Thanks for your help.

Best regards,

Hugo Mariani

[Shwan (shwan-ciyako)]

you can just stop NM by
sudo /etc/init.d/NetworkManager stop

and then everything should work , or maybe start it when you want again by

sudo /etc/init.d/NetworkManager start

[Pavol Klačanský (pavolzetor-deactivatedaccount)]

or "service" alternative
sudo service NetworkManager stop
sudo service NetworkManager start

[arjordan (jorsuscrip)]

I am here because there is an entry in KSystemlog inviting me to see this bug report.

"<info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) "

But I don't know what to do.
This message started appearing after I configured my wireless network with WPA encryption in /etc/network/interfaces, and after a lot of tries to configure it via Network Manager GUI.

By the way, I do not have problems with off-line notifications like the ones mentioned here. Also toolkit.networkmanager.disable is false in Firefox. Is still something wrong in my network connection or this message is just informational?

thanks. Regards
Jorge
Kubuntu 9.04

[Nick Colgan (nick-colgan)]

I was also directed to this bug report by the following entry in my syslog:

NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)

Although I didn't even have Firefox open at the time. Is this bug report even relevant to this issue?

[Mackenzie Morgan (maco.m)]

That message is saying that NM is pretending the unmanaged device is online
since it can't tell if it is or not to avoid people here seeing Firefox offline.
It's perfectly safe to ignore.

[jkohler2 (jkohler2)]

As I understand, the internet connection is one issue, the browser
communicating with the DSL or PPP
software is another issue. I have no problem with the browser starting
right away on my DSL, but the ppp
won't talk to my browser until I go to Firefox "file" and drag down to
uncheck "offline."

John

On Wed, Jul 15, 2009 at 11:39 PM, Nick Colgan
<<email address hidden><nick.colgan%<email address hidden>>
> wrote:

> I was also directed to this bug report by the following entry in my
> syslog:
>
> NetworkManager: <info> Unmanaged Device found; state CONNECTED forced.
> (see http://bugs.launchpad.net/bugs/191889)
>
> Although I didn't even have Firefox open at the time. Is this bug report
> even relevant to this issue?
>
> --
> [MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
> state for networks that are managed outside of network manager.
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[jkohler2 (jkohler2)]

Thank you for your reply.

John Kohler

On Tue, Aug 4, 2009 at 7:24 PM, Duke <email address hidden> wrote:

> ** Changed in: network-manager
> Assignee: (unassigned) => Duke (ers-duke16)
>
> --
> [MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
> state for networks that are managed outside of network manager.
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>
u

[Howard Chu (hyc)]

Another possible solution would be just to add a mechanism to NetworkManager (and the applet) to explicitly inform it of the existence of a connected interface. I'm using adb from the Android SDK to start a ppp session with my G1 phone, and ppp0 comes online with no trouble but NetworkManager doesn't see it and none of the current choices under Edit Connections are appropriate for adding it. (It really should fit under Mobile Broadband but NM doesn't even see the G1 as a usable device.)

And pidgin still refuses to connect in this situation. (This is on jaunty...)

[Alexander Sack (asac)]

ntrack looks promissing. we should look into using that in firefox and other apps next cycle to tackle this problem.

[Rovano (rovano)]

In Karmic Koala same problem with Network manager if manual i manual editing Interfaces and Resolv.conf with static address. Else all ok.

[Benjamin Heil (benjamin-heil)]

In my syslog I get also "NetworkManager: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)" when I try to connect to Ubuntu One. Ubuntu One can't establish a connection. All other network related things are working, I can only see this with Ubuntu One. Weird.

This machine has static IP given at installation time. I've installed VirtualBox, which created a virtual network interface ("vboxnet0"). I think, network manager doesn't know how to handle this virtual interface, which results in the problem above.

[Mathieu Trudel-Lapierre (cyphermox)]

Benjamin,

Seeing that message is normal when you have new virtual interfaces such as 'vboxnet0' from VirtualBox, see comment #266.

Have you run updates since your installation of Karmic? There was one know problem with Ubuntu One and synchronization was disabled for the release. You would see an icon with two arrows circling an exclamation mark if it is the case, along with a popup notification if it is the case. This should be fixed now.

Otherwise, consider opening a new bug, since as you say other network related things are working. Don't forget to tell us what new bug number it is :)

Thanks,

[irishbreakfast (v-spagnolo)]

A newbie experience: I just successfully figured out how to establish a connection at boot so others on the home network can access 'stuff'. When I do log in, I am successfully connected to the router although the applet doesn't find any active connections. And syslog has "NetworkManager: <info> Unmanaged Device found; state CONNECTED forced."
Cheers

[jkohler2 (jkohler2)]

Thanks for the info. My problem with the NetworkManager was different. It
would not allow me to call up either of my 2 usb 56k dialup modems (Zoom and
US Robotics). The failure only happened under Ubuntu 9.10 as 9.04 worked
fine. I needed to remove the
software (sudo apt-get remove networkmanager) to get dialup working for me
under Karmic Koala.

On Sat, Jan 9, 2010 at 4:47 AM, irishbreakfast <email address hidden> wrote:

> A newbie experience: I just successfully figured out how to establish a
> connection at boot so others on the home network can access 'stuff'. When I
> do log in, I am successfully connected to the router although the applet
> doesn't find any active connections. And syslog has "NetworkManager: <info>
> Unmanaged Device found; state CONNECTED forced."
> Cheers
>
> --
> [MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
> state for networks that are managed outside of network manager.
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Evžen Šubrt (evzen-subrt)]

Possible workaround for pidgin: Running pidgin with -f option, i.e.
pidgin -f
Pidgin then connects if using USB modem that is not recognized by NM. Works for me with Pidgin 2.6.2 on Ubuntu 9.10 Keramic Koala.

[Javier López (javier-lopez)]

I've the same issue in Jaunty but I also can't run pidgin -f, it doesn't have an -f option (at least not in the Jaunty version), I wonder why Ubuntu applications rely on NM if it's incomplete.

[Javier López (javier-lopez)]

I've the same issue in Jaunty but I also can't run pidgin -f, it doesn't have an -f option (at least not in the Jaunty version), I wonder why ubuntu applications rely on NM if it's incomplete.

[dzidek23 (dzidek23)]

Hi, I've just upgrade from 9.10 to 10.04 and I found out that my wireless is not working any more. Network setting were still there, but gnome refused to connect saying that wireless is not available. When I used a USB wireless card NM showed two devices but both unavailable.

I have a hardware switch (to turn wireless on or off) which was working perfectly in Windows, Ubuntu 8.04 and later seem to forget about it and 10.04 recognize it. I've turned it ON and the network is working.

Curiosity is that hardware switch turned off/on not only build-in network card but the USB stick as well.

[Sergio Zanchetta (primes2h)]

Thank you for reporting this bug to Ubuntu. Intrepid Ibex 8.10 reached EOL on 30 March 2010.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Please feel free to report any other bugs you may find.
Thank you.

[Sergio Zanchetta (primes2h)]

I realized I had made a mistake, Intrepid Ibex 8.10 "will reach" EOL on 30 "APRIL" 2010.

Sorry for this.

Anyway, I think that one month doesn't make any difference now.

[Steven Harper (stevenharperuk)]

No worries

On 30 Mar 2010, at 22:30, Sergio Zanchetta <email address hidden> wrote:

> I realized I had made a mistake, Intrepid Ibex 8.10 "will reach" EOL
> on
> 30 "APRIL" 2010.
>
> Sorry for this.
>
> Anyway, I think that one month doesn't make any difference now.
>
> --
> [MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper
> online state for networks that are managed outside of network manager.
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.

[dino99 (9d9)]

Architecture: amd64
DistroRelease: Ubuntu 9.04
Gconf:

NonfreeKernelModules: nvidia
Package: pidgin 1:2.5.5-1ubuntu8.6
PackageArchitecture: amd64
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_FR.UTF-8
Uname: Linux 2.6.28-18-generic x86_64
UserGroups: adm admin boinc cdrom dialout lpadmin plugdev sambashare
WpaSupplicantLog:

[dino99 (9d9)]

found these errors into syslog (seems to me they are new on my end)

 nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/net_00_1d_60_39_e9_d6, iface: eth1): not well known

[dino99 (9d9)]

daemon output

[Lipps-steve (lipps-steve)]

I don't see disabling NetworkManager as a realistic solution. I don't want to have to change configuration on my laptop every time I move from a wired to wireless situation. I also don't see any good reason for making this check in the first place. Let me disable the check and I promise I'll never miss it.

While I'm at it, my other annoyance: Why can't Firefox simply ASK if I want to accept cookies or javascript from a particular site and store a record of the choice? (Sorry if this is the wrong place for this. I'm new here and having difficulty finding my way around.)

[nukedathlonman (areginato)]

Read through this, and I'm really confused.... Is this bug a cause or an effect for bug a bug I reported on Friday - bug # 572777 reported here https://bugs.launchpad.net/ubuntu/+bug/572777

I had no problems with 9.04, and upgrading to 9.10, but my upgrade to 10.04 (Lucid) has left me with non-functional wireless. I see a ton of time outs, then messages refer to a prompt where I have to re-input my WPA key. I also see a reference to this bug in my syslog. But for me, my wireless is not connecting at all...The reading of this bug is various connections are already established, but various other pieces of software - esp. Firefox - think the connection is not established and starting off in offline mode. I don't ever remembering having that issue at any point, and I personally don't believe the problems are related...

[nukedathlonman (areginato)]

Read through this, and I'm really confused on what this bug is effecting.... I'm tryign to determine if this bug might be cause or an effect for bug a bug I reported on Friday - bug # 572777 reported here https://bugs.launchpad.net/ubuntu/+bug/572777

I had no problems with 9.04, and upgrading to 9.10, but my upgrade to 10.04 (Lucid) has left me with non-functional wireless. I see a ton of time outs, then messages refer to a prompt where I have to re-input my WPA key. I also see a reference to this bug in my syslog. But for me, my wireless is not connecting at all...The reading of this bug is various connections are already established, but various other pieces of software - esp. Firefox - think the connection is not established and starting off in offline mode. I don't ever remembering having that issue at any point, and I personally don't believe the problems are related...

[antistress (antistress)]

my father has a dial connection (modem 56K) and i had to uninstall network manager to get a connection through gnome-ppp

[antistress (antistress)]

Concerning my comment #432 i forgot to precise : with a clean install of Lucid

[Ryan Waldroop (ryan.waldroop)]

nukedathlonman & antistress: this bug specifically refers to problems with
firefox (and pidgin and others) not connecting to the internet when Network
Manger thinks it is offline. This bug has been solved and fixed.

On Mon, May 3, 2010 at 6:10 AM, antistress <email address hidden>wrote:

> Concerning my comment #432 i forgot to precise : with a clean install of
> Lucid
>
> --
> [MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
> state for networks that are managed outside of network manager.
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Partho Benerjee (parthobenerjee)]

I see that the fix has been committed and released for network manager. But I think the whole issue hasn't moved an inch towards resolution. Even after two years, nw fails to look at ppp connection status to give an informed online/offline status. All depending applications i.e. evolution, firefox etc. continue to be fooled by nw's online/offline status. They continue to start in offline mode.

In two years, no fix/progress/information sought/fix?? Is there anything I can do to stop evolution from starting in offline mode?
Is there anything, I as a user can do to help?? This is glaring!!

[Partho Benerjee (parthobenerjee)]

I see that the fix has been committed and released for network manager. But I think the whole issue hasn't moved an inch towards resolution. Even after two years, nw fails to look at ppp connection status to give an informed online/offline status. All depending applications i.e. evolution, firefox etc. continue to be fooled by nw's online/offline status. They continue to start in offline mode.

In two years, thgere is no fix or progress or information has been sought ? Is there anything I can do to stop evolution from starting in offline mode?
Is there anything, I as a user can do to help?? This is glaring!!

[Partho Benerjee (parthobenerjee)]

Hi, I connect to internet using Huawei EC1260 USB modem on Lucid Lynx. The network manager "detects" the mobile broadband hardware but doesn't conect for some reason that I'll investigate later.
Since nw can't get me connected (despite detecting the device), I am forced to use ppp (wvdial or GNOME-ppp)

So, I connect using GNOME-PPP that uses pppd interface for the Huawei modem. It works like a charm.
After I successfully connect as above, when I physically pull out the Huawei USB modem, network manager immediately jumps and notifies me that I am "now" offline. Why is network manager telling everybody ( e.g. Firefox, Evolution) that I was offline before ?

My point is : If network manager instantly and exactly "knows" when I get offline after staying connected using ppp, then why is it misguiding all the depending application that I was offline before?

While I used the Firefox workaround using about:config, is there any workaround to get Evolution start online??

[[e-mail] (r-a-g-fey)]

I have just added the option -offline to the starter. example: firefox -offline %u
This works for me, firefox is starting in online mode.

[[e-mail] (r-a-g-fey)]

I have just added the option -offline to the starter.
example: firefox -offline %u
This works for me, firefox is starting in online mode.

[Paul Perkins (catmatist)]

Some recent (this is July 26, 2010) update to Lucid has caused NetworkManager to wake up, on a system that has no need for it (static, permanent, wired, unmanaged network link only) and begin broadcasting via ipc-of-the-week (DBUS?) that the machine had no network connection, causing Firefox, claws-mail, etc.,, to start in Offline mode. Firefox and claws-mail both have obscure ways to tell them not to listen to what NetworkMangler says. I've applied those and also removed as many networkmanager packages as I could using Synaptic. I just hope the Damned thing is dead now.

I also have a laptop, also running Lucid, that kind of needs something like NetworkManager. It works so far... When it is good, it is very, very good, and when it is bad, it is horrid.

[Paul Perkins (catmatist)]

Some recent (this is July 26, 2010) update to Lucid has caused NetworkManager to wake up, on a system that has no need for it (static, permanent, wired, unmanaged network link only) and begin broadcasting via ipc-of-the-week (DBUS?) that the machine had no network connection, causing Firefox, claws-mail, etc.,, to start in Offline mode. Firefox and claws-mail both have obscure ways to tell them not to listen to what NetworkMangler says. I've applied those and also removed as many networkmanager packages as I could using Synaptic. I just hope the Damned thing is dead now.

I also have a laptop, also running Lucid, that kind of needs something like NetworkManager. It works so far. When it is good, it is very, very good, and when it is bad, it is horrid.

[Paul Perkins (catmatist)]

Some recent (this is July 26, 2010) update to Lucid has caused NetworkManager to wake up, on a system that has no need for it (static, permanent, wired, unmanaged network link only) and begin broadcasting via ipc-of-the-week (DBUS?) that the machine had no network connection, causing Firefox, claws-mail, etc., to start in Offline mode. Firefox and claws-mail both have obscure ways to tell them not to listen to what NetworkMangler says. I've applied those and also removed as many networkmanager packages as I could using Synaptic. I just hope the Damned thing is dead now.

I also have a laptop, also running Lucid, that kind of needs something like NetworkManager. It works so far. When it is good, it is very, very good, and when it is bad, it is horrid.

[Paul Perkins (catmatist)]

Launchpad kept giving me an information-free error popup whenever I hit "post" and so I did not know it was actually posting until I hit refresh. Sorry (but it's not my fault really, is it).

[Jim Kyle (jim-jimkyle)]

I have three boxes all running Lucid and all fully updated as of 5 Sept 2010. All three have unmanaged interfaces via /etc/network/interfaces entries. On this box Firefox works normally. On the other two it always comes up in offline mode, and Workaround 1 listed in comment 1 of this report has no effect on it. I've not tried Workaround 2 on them yet.

This box does have one totally unused network adapter that's listed in the interfaces file together with the two NICs that really are used, which may be the difference. However the syslog shows sporadic entries that NetworkManager has found an unmanaged interface and forced "connected" state...

[Jim Kyle (jim-jimkyle)]

Update to comment 456:

Workaround 2 had no effect either, but inverting the setting of Workaround 1 from "false" to "true" did solve the problem on the test system. It no longer comes up in "work offline" mode.

[jkohler2 (jkohler2)]

Thanks for the summary of your efforts. I experience the "offline"
condition for
FireFox only during a dialup connection. Using the DSL network connection
with a router
and DSL adapter Firefox works normally. My dialup connection for Ubuntu
9.04 and 9.10 has been gnome-ppp.

On Sun, Sep 5, 2010 at 8:30 PM, Jim Kyle <email address hidden> wrote:

> Update to comment 456:
>
> Workaround 2 had no effect either, but inverting the setting of
> Workaround 1 from "false" to "true" did solve the problem on the test
> system. It no longer comes up in "work offline" mode.
>
> --
> [MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper online
> state for networks that are managed outside of network manager.
> https://bugs.launchpad.net/bugs/191889
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[dino99 (9d9)]

What is logged on Precise i386:

NetworkManager[2054]: <info> (eth1): deactivating device (reason 'managed') [2]
localhost NetworkManager[2054]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
localhost NetworkManager[2054]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
localhost NetworkManager[2054]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/net/eth1

[dino99 (9d9)]

What is logged on Precise i386:

NetworkManager[2054]: <info> (eth1): deactivating device (reason 'managed') [2]
localhost NetworkManager[2054]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
localhost NetworkManager[2054]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
localhost NetworkManager[2054]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/net/eth1

[jkohler2 (jkohler2)]

I am using Ubuntu 10.04 and a recent fire fox version. When I use my Dial-up
program, Gnome-ppp I still need to uncheck the "work offline" box under the file pull-down menu

John

[David Scott (tdavid-scott3)]

After reading this entire post, and finding nothing useful. The only useful posting was the one about updating (searching for the poster, crashed my FireFox) so I am not sure if this will help anyone.

[My System]
Ubuntu 10.04.3 (server) - updated to generic-pae - running Xubuntu-Desktop
Linux acer 2.6.32-38-generic-pae #83-Ubuntu SMP Wed Jan 4 12:11:13 UTC 2012 i686 GNU/Linux
--------
The steps I took to fix the problem
Applications->Accessories->Terminal
$ sudo su -
$ aptitude search network
    I looked for all that was installed, and what I thought would be needed to maintain the network through apps instead of directly through the /etc/network/interfaces file
I found and installed the below apps
$ sudo apt-get install network-manager network-config network-manager-gnome gnome-network-admin --reinstall

The gui informed me after this install I needed to reboot, so I rebooted.
Once I rebooted, the notification icon didn't appear, and FireFox along with other applications did start correctly, (ie NOT in "Offline" Mode)

[jkohler2 (jkohler2)]

Thanks. I will print this message and follow the directions.

John

On Wed, Jan 25, 2012 at 4:59 AM, David Scott <email address hidden>wrote:

> After reading this entire post, and finding nothing useful. The only
> useful posting was the one about updating (searching for the poster,
> crashed my FireFox) so I am not sure if this will help anyone.
>
> [My System]
> Ubuntu 10.04.3 (server) - updated to generic-pae - running Xubuntu-Desktop
> Linux acer 2.6.32-38-generic-pae #83-Ubuntu SMP Wed Jan 4 12:11:13 UTC
> 2012 i686 GNU/Linux
> --------
> The steps I took to fix the problem
> Applications->Accessories->Terminal
> $ sudo su -
> $ aptitude search network
> I looked for all that was installed, and what I thought would be needed
> to maintain the network through apps instead of directly through the
> /etc/network/interfaces file
> I found and installed the below apps
> $ sudo apt-get install network-manager network-config
> network-manager-gnome gnome-network-admin --reinstall
>
> The gui informed me after this install I needed to reboot, so I rebooted.
> Once I rebooted, the notification icon didn't appear, and FireFox along
> with other applications did start correctly, (ie NOT in "Offline" Mode)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/191889
>
> Title:
> [MASTER] [WORKAROUND] "Offline Mode" feature fails to detect proper
> online state for networks that are managed outside of network manager.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/firefox/+bug/191889/+subscriptions
>

[jsmanian (jsmanian79)]

I also having this bug. System is not shutting down properly.

rsyslog file:

May 23 22:43:22 jsm NetworkManager[666]: <info> (ttyACM0): device state change: activated -> disconnected (reason 'user-requested') [100 30 39]
May 23 22:43:22 jsm NetworkManager[666]: <info> (ttyACM0): deactivating device (reason 'user-requested') [39]
May 23 22:43:22 jsm pppd[2335]: Terminating on signal 15
May 23 22:43:22 jsm pppd[2335]: Connect time 33.5 minutes.
May 23 22:43:22 jsm pppd[2335]: Sent 816683 bytes, received 23488634 bytes.
May 23 22:43:22 jsm NetworkManager[666]: nm_system_iface_flush_routes: assertion `ifindex > 0' failed
May 23 22:43:22 jsm NetworkManager[666]: nm_system_iface_flush_addresses: assertion `ifindex > 0' failed
May 23 22:43:22 jsm pppd[2335]: Connection terminated.
May 23 22:43:22 jsm avahi-daemon[663]: Withdrawing workstation service for ppp0.
May 23 22:43:22 jsm dnsmasq[2388]: exiting on receipt of SIGTERM
May 23 22:43:22 jsm NetworkManager[666]: <info> DNS: starting dnsmasq...
May 23 22:43:22 jsm NetworkManager[666]: <info> (ttyACM0): writing resolv.conf to /sbin/resolvconf
May 23 22:43:23 jsm dnsmasq[3230]: started, version 2.59 cache disabled
May 23 22:43:23 jsm dnsmasq[3230]: compile time options: IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN
May 23 22:43:23 jsm dnsmasq[3230]: warning: no upstream servers configured
May 23 22:43:23 jsm modem-manager[642]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected -> disconnecting)
May 23 22:43:23 jsm dbus[508]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
May 23 22:43:23 jsm NetworkManager[666]: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
May 23 22:43:23 jsm dbus[508]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 23 22:43:24 jsm modem-manager[642]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting -> registered)
May 23 22:43:27 jsm modem-manager[642]: <info> (ttyACM0) closing serial port...
May 23 22:43:27 jsm modem-manager[642]: <info> (ttyACM0) serial port closed
May 23 22:43:27 jsm kernel: [ 2975.160088] usb 3-1: USB disconnect, device number 2
May 23 22:43:27 jsm modem-manager[642]: <info> (tty/ttyACM0): released by modem /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1
May 23 22:43:27 jsm modem-manager[642]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered -> disabled)
May 23 22:43:27 jsm NetworkManager[666]: <info> (ttyACM0): now unmanaged
May 23 22:43:27 jsm NetworkManager[666]: <info> (ttyACM0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
May 23 22:43:27 jsm NetworkManager[666]: <info> (ttyACM0): cleaning up...
May 23 22:43:27 jsm NetworkManager[666]: <info> (ttyACM0): taking down device.
May 23 22:43:27 jsm NetworkManager[666]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
May 23 22:43:27 jsm NetworkManager[666]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
May 23 22:43:36 jsm kernel: Kernel logging (proc) stopped.
May 23 22:43...

[jsmanian (jsmanian79)]

I also having this bug. System is not shutting down properly.
syslog file:
May 23 22:43:22 jsm NetworkManager[666]: <info> (ttyACM0): device state change: activated -> disconnected (reason 'user-requested') [100 30 39]
May 23 22:43:22 jsm NetworkManager[666]: <info> (ttyACM0): deactivating device (reason 'user-requested') [39]
May 23 22:43:22 jsm pppd[2335]: Terminating on signal 15
May 23 22:43:22 jsm pppd[2335]: Connect time 33.5 minutes.
May 23 22:43:22 jsm pppd[2335]: Sent 816683 bytes, received 23488634 bytes.
May 23 22:43:22 jsm NetworkManager[666]: nm_system_iface_flush_routes: assertion `ifindex > 0' failed
May 23 22:43:22 jsm NetworkManager[666]: nm_system_iface_flush_addresses: assertion `ifindex > 0' failed
May 23 22:43:22 jsm pppd[2335]: Connection terminated.
May 23 22:43:22 jsm avahi-daemon[663]: Withdrawing workstation service for ppp0.
May 23 22:43:22 jsm dnsmasq[2388]: exiting on receipt of SIGTERM
May 23 22:43:22 jsm NetworkManager[666]: <info> DNS: starting dnsmasq...
May 23 22:43:22 jsm NetworkManager[666]: <info> (ttyACM0): writing resolv.conf to /sbin/resolvconf
May 23 22:43:23 jsm dnsmasq[3230]: started, version 2.59 cache disabled
May 23 22:43:23 jsm dnsmasq[3230]: compile time options: IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN
May 23 22:43:23 jsm dnsmasq[3230]: warning: no upstream servers configured
May 23 22:43:23 jsm modem-manager[642]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected -> disconnecting)
May 23 22:43:23 jsm dbus[508]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
May 23 22:43:23 jsm NetworkManager[666]: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
May 23 22:43:23 jsm dbus[508]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 23 22:43:24 jsm modem-manager[642]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting -> registered)
May 23 22:43:27 jsm modem-manager[642]: <info> (ttyACM0) closing serial port...
May 23 22:43:27 jsm modem-manager[642]: <info> (ttyACM0) serial port closed
May 23 22:43:27 jsm kernel: [ 2975.160088] usb 3-1: USB disconnect, device number 2
May 23 22:43:27 jsm modem-manager[642]: <info> (tty/ttyACM0): released by modem /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1
May 23 22:43:27 jsm modem-manager[642]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered -> disabled)
May 23 22:43:27 jsm NetworkManager[666]: <info> (ttyACM0): now unmanaged
May 23 22:43:27 jsm NetworkManager[666]: <info> (ttyACM0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
May 23 22:43:27 jsm NetworkManager[666]: <info> (ttyACM0): cleaning up...
May 23 22:43:27 jsm NetworkManager[666]: <info> (ttyACM0): taking down device.
May 23 22:43:27 jsm NetworkManager[666]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
May 23 22:43:27 jsm NetworkManager[666]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
May 23 22:43:36 jsm kernel: Kernel logging (proc) stopped.
May 23 22:43:36...

[jsmanian (jsmanian79)]

I also having this bug. System is not shutting down properly.
syslog file:
May 23 22:43:23 jsm dnsmasq[3230]: compile time options: IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN
May 23 22:43:23 jsm dnsmasq[3230]: warning: no upstream servers configured
May 23 22:43:23 jsm modem-manager[642]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected -> disconnecting)
May 23 22:43:23 jsm dbus[508]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
May 23 22:43:23 jsm NetworkManager[666]: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
May 23 22:43:23 jsm dbus[508]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 23 22:43:24 jsm modem-manager[642]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (disconnecting -> registered)
May 23 22:43:27 jsm modem-manager[642]: <info> (ttyACM0) closing serial port...
May 23 22:43:27 jsm modem-manager[642]: <info> (ttyACM0) serial port closed
May 23 22:43:27 jsm kernel: [ 2975.160088] usb 3-1: USB disconnect, device number 2
May 23 22:43:27 jsm modem-manager[642]: <info> (tty/ttyACM0): released by modem /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1
May 23 22:43:27 jsm modem-manager[642]: <info> Modem /org/freedesktop/ModemManager/Modems/0: state changed (registered -> disabled)
May 23 22:43:27 jsm NetworkManager[666]: <info> (ttyACM0): now unmanaged
May 23 22:43:27 jsm NetworkManager[666]: <info> (ttyACM0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
May 23 22:43:27 jsm NetworkManager[666]: <info> (ttyACM0): cleaning up...
May 23 22:43:27 jsm NetworkManager[666]: <info> (ttyACM0): taking down device.
May 23 22:43:27 jsm NetworkManager[666]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
May 23 22:43:27 jsm NetworkManager[666]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
May 23 22:43:36 jsm kernel: Kernel logging (proc) stopped.
May 23 22:43:36 jsm rsyslogd: [origin software="rsyslogd" swVersion="5.8.6" x-pid="504" x-info="http://www.rsyslog.com"] exiting on signal 15.

And my machine configuration is
Processor - Intel® Core™2 Duo CPU E4600 @ 2.40GHz × 2
OS type - 64Bit
Memory - 2GB

[Neill_R (neill-rutherford)]

 <info> Unmanaged Device found; state CONNECTED forced.

I am running Ubuntu server 12.04 LTS with ubuntu-desktop installed. The eth0 device is not managed by NM. I use NM to connect my 3g Mobile Broardband USB modem to the internet. I also use firestarter to provision (Internet Connection Sharing). As of this moment I see no problems. Either when I use my 3G modem or I plug the eth0 into a router to gain Internet access.

[Standard8 (mbanner)]

Comment on attachment 322833
Disable DBUS support if NetworkManager 0.7 is not present

Per comments 61 - 72 removing what I understand to be an obsolete review request on a long-old patch. If I have miss-understood the patch is still needed, please file a new bug and attach a fresh patch there. Thanks.

[Joni-Pekka Kurronen (joni-kurronen)]

Same here whit 12.5 LTS 64 bit,... but it's anoying
that syslog fill's whit below shit,...

=====
Dec 2 23:28:14 kurrola kernel: [28963.624076] Unknown OutputIN= OUT=lxcbr0 SRC=10.0.3.1 DST=10.0.3.255 LEN=316 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=631 DPT=631 LEN=296
Dec 2 23:28:21 kurrola NetworkManager[2085]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Dec 2 23:28:23 kurrola NetworkManager[2085]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Dec 2 23:28:31 kurrola NetworkManager[2085]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Dec 2 23:28:33 kurrola NetworkManager[2085]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Dec 2 23:28:41 kurrola NetworkManager[2085]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Dec 2 23:28:43 kurrola NetworkManager[2085]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Dec 2 23:28:45 kurrola kernel: [28994.926798] Unknown OutputIN= OUT=lxcbr0 SRC=10.0.3.1 DST=10.0.3.2

[Desiderius Sriyono (dsriyono)]

kode02

[Kychot (petr-dulos)]

Ubuntu 12.10
Linux eb 3.5.0-27-generic #46-Ubuntu SMP Mon Mar 25 20:00:05 UTC 2013 i686 i686 i686 GNU/Linux
USB modem: Product: Vertex Wireless Multi-Function Device

The connection is OK but after every 50 minutes the modem hangups:

May 3 15:36:05 eb pppd[3589]: LCP terminated by peer
May 3 15:36:05 eb pppd[3589]: Connect time 51.1 minutes.
May 3 15:36:05 eb pppd[3589]: Sent 1768732 bytes, received 55238638 bytes.
May 3 15:36:09 eb pppd[3589]: Connection terminated.
May 3 15:36:09 eb NetworkManager[1189]: <info> (ttyACM0): device state change: activated -> failed (reason 'ip-config-unavailable') [100 120 5]
May 3 15:36:09 eb avahi-daemon[1159]: Withdrawing workstation service for ppp0.
May 3 15:36:09 eb NetworkManager[1189]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
May 3 15:36:09 eb NetworkManager[1189]: <warn> Activation (ttyACM0) failed for connection 'UFON 910 045 174'
....

Sometimes the modem falls out after some minutes:
May 3 15:40:24 eb NetworkManager[1189]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
May 3 15:41:14 eb pppd[5438]: Modem hangup
May 3 15:41:14 eb pppd[5438]: Connect time 4.1 minutes.
May 3 15:41:14 eb pppd[5438]: Sent 141041 bytes, received 1393940 bytes.
...

On another netbook with Ubuntu 12.04 LTS this modem runs many hours without problems.
See Attachment for syslog

[Kychot (petr-dulos)]

Ubuntu 12.10
Linux eb 3.5.0-27-generic #46-Ubuntu SMP Mon Mar 25 20:00:05 UTC 2013 i686 i686 i686 GNU/Linux
USB modem: Product: Vertex Wireless Multi-Function Device

The connection is OK but after every 50 minutes the modem hangups:

May 3 15:36:05 eb pppd[3589]: LCP terminated by peer
May 3 15:36:05 eb pppd[3589]: Connect time 51.1 minutes.
May 3 15:36:05 eb pppd[3589]: Sent 1768732 bytes, received 55238638 bytes.
May 3 15:36:09 eb pppd[3589]: Connection terminated.
May 3 15:36:09 eb NetworkManager[1189]: <info> (ttyACM0): device state change: activated -> failed (reason 'ip-config-unavailable') [100 120 5]
May 3 15:36:09 eb avahi-daemon[1159]: Withdrawing workstation service for ppp0.
May 3 15:36:09 eb NetworkManager[1189]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
May 3 15:36:09 eb NetworkManager[1189]: <warn> Activation (ttyACM0) failed for connection 'UFON 910 045 174'
....

Sometimes the modem falls out after some minutes:
May 3 15:40:24 eb NetworkManager[1189]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
May 3 15:41:14 eb pppd[5438]: Modem hangup
May 3 15:41:14 eb pppd[5438]: Connect time 4.1 minutes.
May 3 15:41:14 eb pppd[5438]: Sent 141041 bytes, received 1393940 bytes.
...

On another netbook with Ubuntu 12.04 LTS this modem runs many hours without problems.
See Attachment for syslog

[Shahriyar Rzayev (rzayev-sehriyar)]

While trying to connect using Blackberry Q10 hotspot on Ubuntu 14.04 getting link to this bug report:

Nov 29 11:02:46 shrzayev NetworkManager[1056]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Nov 29 11:02:55 shrzayev NetworkManager[1056]: get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed
Nov 29 11:02:55 shrzayev NetworkManager[1056]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 29 11:02:55 shrzayev NetworkManager[1056]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov 29 11:02:55 shrzayev NetworkManager[1056]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Nov 29 11:02:55 shrzayev NetworkManager[1056]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889
)

Also as you noticed there is an assertion -> get_secret_flags: assertion 'is_secret_prop (setting, secret_name, error)' failed

root@shrzayev:~# uname -r
3.13.0-68-generic