Since upgrading to core 9 from core 8, my laptops start up firefox in "off-line" mode. Changing the value through the menu brings the browser into on-line mode, but only for the session.
This looks like a permissions problem, but I can't find what file is read-only. Any suggestions?
--Phillip
On Wed, 12 Nov 2008 11:37:10 -0500 (EST) Phillip ptho@FIREFLY.NLM.NIH.GOV wrote:
Since upgrading to core 9 from core 8, my laptops start up firefox in "off-line" mode. Changing the value through the menu brings the browser into on-line mode, but only for the session.
I discovered that too. It's something to do with Network Manager. If you don't need NM, turn it off and the problem will go away.
Run "firefox network manager" through Google and you'll find all sorts of write-up about this.
On the good news side, I have F10-beta installed on my laptop, and use NM on that, and haven't seen this issue there yet.
Thanks. Good observation. That worked perfectly. I've had to take NetworkManager off many machines as it messes up the resolv.conf file for static addresses. Apparently a recent update not only installed NetworkManager but also turned it on when it had previously been off.
Phillip
On Wed, 12 Nov 2008, Frank Cox wrote:
On Wed, 12 Nov 2008 11:37:10 -0500 (EST) Phillip ptho@FIREFLY.NLM.NIH.GOV wrote:
Since upgrading to core 9 from core 8, my laptops start up firefox in "off-line" mode. Changing the value through the menu brings the browser into on-line mode, but only for the session.
I discovered that too. It's something to do with Network Manager. If you don't need NM, turn it off and the problem will go away.
Run "firefox network manager" through Google and you'll find all sorts of write-up about this.
On the good news side, I have F10-beta installed on my laptop, and use NM on that, and haven't seen this issue there yet.
-- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com DRY CLEANER BUSINESS FOR SALE ~ http://www.canadadrycleanerforsale.com
On Wed, 2008-11-12 at 10:41 -0600, Frank Cox wrote:
I discovered that too. It's something to do with Network Manager. If you don't need NM, turn it off and the problem will go away.
Alternatively, configure it correctly and the problem also goes away. NM thinks that an interface it's not managing is not connected, and it reports this to other apps that ask it. If you tell it to manage the interface in question, it gets it right.
poc
I just put to about:config in the address bar and set toolkit.networkmanager.disable to true. German.
-- Germán A. Racca Instituto Nacional de Pesquisas Espaciais - INPE Divisão de Astrofísica - DAS/CEA São José dos Campos - SP - Brasil -- TEL: 55 12 3945-7209 FAX: 55 12 3945-6811 -- http://funk.on.br/racca