Andre Truter wrote:

On 1/18/07, Wolfgang Rosenauer wrote:

...

Andre Truter wrote:

...

I installed openSUSE 10.2 for a client on a laptop. One of the main [...]

How is the local demo accessed then? On a local webserver or as local files? If it's a webserver which IP address is used then?

http://localhost

So, the computer can be off-line in terms of the internet, but Firefox should not.

I have set localhost as the home page, so when you open FIrefox the first time, it says that it cannot find the page as you are offline. Pretty stupid huh? The web server runs locally, you only need the loopback interface, no other interfaces.

When you start firefox again, it has cached the initial page, so it displays, but the first thing you click on the page results in a "Cannot find page - please go online"

So, I would like Firefox to start in online mode, no matter if the machine is connected to a network or not.

OK, I admit that is strange and shouldn't happen. Known local addresses shouldn't go through this offline mode. Would you mind open a bug in bugzilla about it (and CC me). Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Roger Dedrick wrote:

Andre Truter wrote:

...

I installed openSUSE 10.2 for a client on a laptop. One of the main uses he has for it is to go around to clients and demo a web application that is installed on the laptop. So, the machine will not be connected to a network when he does the demos.

He will also mainly use modem dial up for internet connectivity.

Problem is that apparently Firefox looks at the status of NetworkManager to decide if it should start in offline mode of online mode. So, every time he does a demo, he first need to remember to set Firefox in online mode. This is extremely frustrating, as that is the last thing you think of if you do a demo on your local machine and it is also not so good to try and impress a client and the first thing they see is an error message.

Does anybody know if there is a way of overriding this behavior in Firefox?

I have googled, but have not found anything yet.

Thanks I'm not sure if it's that same situation but my desktop went into the "off line mode" it was very annoying. . look in the user settings folder for the prefs.js file and edit the line "user_pref("browser.offline", false);" It worked for me.

This should work as a workaround I think but I'm not absolutely sure if this lives long enough. My questions before were about improving the online/offline feature if it behaves wrong. The machine _is_ offline so offline-mode would be correct. Therefore I asked why offline mode is a problem when the demo is local. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Hey, here's another problem that I've seen. I installed 10.2 on my mom's 'puter and each time Firefox is started, it starts in "offline" mode. That is damned irritationg to me and somewhat confusing to her. Mihamina suggested "You should just make the Firefox home page either a blank page or http://localhost/ (if a web server is set up) or file:/// as last choice." That might work, but since Mom is dialed in and on the net before Firefox is started, she expects it to be in online mode and the home page to be what she wants it to be. Can someone explain why Firefox stays offline even when a dialup connection is made? Roger's idea of "look in the user settings folder for the prefs.js file and edit the line "user_pref("browser.offline", false);" might be the best route to follow if, in fact, the setting will stay. Thanks for the help, Fred -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 1/19/07, Wolfgang Rosenauer wrote:

So most probably NetworkManager is activated on the system but not used for the dialup connection. This is a known issue since NetworkManager still thinks the machine is offline. If NetworkManager is not needed (e.g. for WiFi) you should deactivate it, which would fix the problem.

Yip, deactivating Network Manager do fix the problem.

From James Ogley's response in the older thread, it sounded like FF might depend on Network Manager, but I suppose that I misinterpreted it.

I'll log a bug in bugzilla. Thanks -- Andre Truter | Software Consultant | Registered Linux user #185282 Jabber: andre.truter@gmail.com | http://www.trusoft.co.za ~ A dinosaur is a salamander designed to Mil Spec ~ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org