Am Dienstag 22 Juli 2008 schrieb Mike Hommey: > On Tue, Jul 22, 2008 at 11:00:10AM +0200, Martin Steigerwald <[EMAIL PROTECTED]> wrote: > > Am Dienstag 22 Juli 2008 schrieb Mike Hommey: > > > > However I think it is important to have an option in Iceweasel to > > > > disable asking Network Manager for online status. Like the above > > > > mentioned option that does not appear to work here. That is what > > > > this bug report is for. > > > > > > And this is exactly what toolkit.networkmanager.disable is supposed > > > to be doing. And it needs to be true, not false, to work. So, reset > > > its value (true is supposed to be the default (though not the > > > upstream default)) > > > > about:config shows me: > > > > toolkit.networkmanager.disable Standard boolean true > > > > Its true and I do not know how I can make it any truer than that. > > You said you set it to false
Yes, I did. Sorry. My fault.
> > For the sake of it I also tried the reverse logic in case the Firefox
> > gets the logic wrongly. But whatever the setting is: Iceweasel starts
> > offline.
>
> Doesn't it start offline because it was offline before, because of NM ?
> If you put it online again, close iceweasel and start again, what
> happens ?
Thanks. I tried all that. I did it again just to verify it.
I had network manager running and started Iceweasel without any special
networkmanager setting in my user preferences:
[EMAIL PROTECTED]> grep "toolkit\.networkmanager\.disable"
~/.mozilla/firefox/default[...]/*.js
[EMAIL PROTECTED]>
Which means that is defaults to true. I verified that by looking at
about:config.
I set it to be online:
[EMAIL PROTECTED]> grep "offline" ~/.mozilla/firefox/default[...]/*.js
/home/martin/.mozilla/firefox/default[...]/prefs.js:user_pref("browser.offline",
false);
I close it and verify that no firefox processes are running:
[EMAIL PROTECTED]> ps aux | egrep "(iceweasel|firefox)"
[EMAIL PROTECTED]>
I start Firefox again: Its offline again.
I stop network manager and its dispatcher. I set Firefox to online. I
close firefox. I start firefox again and it is still online.
Anyway when network manager is stopped, Iceweasel is *always* online,
regardless what I set via GUI in user.js:
[EMAIL PROTECTED]> # I stop Iceweasel with no network-manager running and
set to offline
[EMAIL PROTECTED]> grep "offline" ~/.mozilla/firefox/default[...]/*.js
/home/martin/.mozilla/firefox/default[...]/prefs.js:user_pref("browser.offline",
true);
[EMAIL PROTECTED]> ps aux | grep network-manager
[EMAIL PROTECTED]> # I start Iceweasel again
[EMAIL PROTECTED]> grep "offline" ~/.mozilla/firefox/default[...]/*.js
/home/martin/.mozilla/firefox/default[...]/prefs.js:user_pref("browser.offline",
true);
[EMAIL PROTECTED]> # But nonetheless it reports being *online* in the GUI...
[EMAIL PROTECTED]> # I quit it again
[EMAIL PROTECTED]> grep "offline" ~/.mozilla/firefox/default[...]/*.js
/home/martin/.mozilla/firefox/default[...]/prefs.js:user_pref("browser.offline",
true);
[EMAIL PROTECTED]> # It start it again
[EMAIL PROTECTED]> # Its still online in the GUI and I can surf, but it
reports otherwise in the pref
[EMAIL PROTECTED]> grep "offline" ~/.mozilla/firefox/default[...]/*.js
/home/martin/.mozilla/firefox/default[...]/prefs.js:user_pref("browser.offline",
true);
Now that doesn't seem to be *consistent* behavior to me.
*puzzled*
Anything else I can provide? (I would like to avoid posting the complete
prefs.js or user.js without looking carefully whether something stored
something private in there, but I can provide further parts of it.)
> > So the option does not work here.
>
> The code is such that there is *no*way* NM can be responsible of
> iceweasel being offline at startup, so it's either a problem with your
> configuration or another bug.
Could it be that the debian variant of Iceweasel does not include the
patch that was mentioned in the upstream bug report?
Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
signature.asc
Description: This is a digitally signed message part.
