User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/20071015 SUSE/220.127.116.11-0.2 Firefox/18.104.22.168 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:22.214.171.124) Gecko/20071015 SUSE/126.96.36.199-0.2 Firefox/188.8.131.52 When Firefox automatically goes offline because NetworkManager says there's no network, and then you try to visit a web site, Firefox gives you an error saying 'Uncheck "Work Offline" in the File menu, then try again.' This isn't really an accurate/useful message in that case. It should say something about you not being connected to the network instead. Reproducible: Always Steps to Reproduce: 1. Open firefox 2. Disconnect network 3. Try visiting another page Actual Results: The "uncheck 'work offline'" message is displayed. Expected Results: A message stating that the network is down, etc.
xref bug 502659
The behaviour is different for me in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:184.108.40.206) Gecko/20091201 Firefox/3.5.6 (.NET CLR 3.5.30729) When I disconnect from the network, I get "Server not found Firefox can't find the server at bugzilla.mozilla.org." as an error.
This bug was originally reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.6 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
Whiteboard: [CLOSEME 2010-07-30]
Version: unspecified → 2.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.8 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.