[Bug 474629] Re: Firefox Not Load Most Pages Via Verizon Wireless DSL - DOES Load Them Using Wireless Dial-up Account - Workaround Included Within Posts

Christopher M. Penalver christopher.m.penalver at gmail.com
Mon Jan 20 05:26:04 UTC 2014

Lawrence H. Bulk, this bug was reported a while ago and there hasn't
been any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux REPLACE-WITH-BUG-NUMBER

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:

where VERSION-NUMBER is the version number of the kernel you tested. For example:

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:

If the mainline kernel does not fix this bug, please add the following tags:

As well, please remove the tag:

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results. Thank you for your

** Description changed:

  Computer: Acer Extensa 5620-6419, Intel Core 2 Duo Processor T5550 [1.83
  GHz, 667 MHz FSB, 2 MB L2 Cache], Up to 358 MB Mobile Intel Graphics,
  Media Accelerator X3100, 3 GB DDR2, 160 GB HDD, DVD-Super Multi DL,
  802.11a/b/g WLAN.
+ WORKAROUND: Type about:config in the address bar, press Enter. Find
+ network.dns.disableIPv6 in the list. Right-click -> Toggle. Set to true.
+ Restart Firefox.
  Internet services: Verizon DSL (Wireless) or EarthLink Dial-up (through
  a Wi-flyer wireless router - this handles dial-up internet accounts).
  Everything on the computer is functioning normally and I have made no
  modifications whatsoever with the exception of wiping Windows Vista
  entirely and replacing it with Ubuntu Linux. That was in June 2008 and
  the first Ubuntu version I used was 'Hardy.' The wireless routers are
  also functioning normally.
  I had few troubles with 8.04, 8.10, or 9.04.
  The following problem has now happened three times and, as it makes
  absolutely no sense to me, I cannot understand it:
  The first day I install 'Karmic,' everything - EVERYTHING - works
  perfectly. No matter how many times I effect a restart or a complete
  shutdown, leaving the computer off for an hour or so, and then start it
  up again, everything works perfectly.
  That's the first day (the day of installation).
  On the NEXT day, everything works correctly EXCEPT Firefox [3.5.4] WILL
  NOT load MOST pages. Obviously it has loaded this one - I'm typing this
  from my computer with 'Karmic' installed; it will also load up most
  Ubuntu pages - but almost nothing else. For example, <
  http://www.refdesk.com > will not load; <http://www.amazon.com > will
  only partially load (after about ten minutes!), and others are the same.
  Either they don't load at all or they only partially load.
  The above is with my Verizon wireless DSL.
  Now you would say (and I did) that the problem is with Verizon - but no;
  I also own an Asus EeePC 1000/Linux (uses the modified Xandros OS) and
  it too is running Firefox 3.5.4 - and every page loads up perfectly!
  (Obviously both Verizon and my wireless DSL router are also functioning
  So now you might say (and I did) that the problem is with Firefox - but
  no; when I connect to the internet through EarthLink dial-up (via the
  Wi-flyer), all desired pages load up perfectly on Firefox (although
  agonizingly slowly - it is dial-up, after all).
  I repeat - every piece of hardware seems to be operating normally and,
  on the first day I install 'Karmic,' everything is just fine.
  But on the second day --- well, that's why I'm here!
  And this has happened to me three times now. I first effected a network
  update from 'Jaunty' and, the first day, everything worked. After
  Firefox would not load MOST pages on the second day, I 'wiped' the
  computer with DBAN and reinstalled 'Karmic' from my previously
  downloaded disc.
  I've now done the 'wipe' and reinstall twice, each time with the same
  I cannot understand how I can be connected to the internet (I have a
  couple of internet radio stations' URLs stored in my Music folder (for
  example, one which I have labeled Classic FM UK.m3u which calls up
  SMPlayer and another labeled WQXR 105.9 MHz.scpls which calls up VLC)
  and these continue to work perfectly!
  Obviously, I am DEFINITELY connected to the internet!
  How can I be connected to the internet using 'Karmic' Verizon wireless
  DSL and yet not have Firefox load pages?
  Before I totally 'wipe' my computer again (and reinstall 9.04 'Jaunty')
  can ANYONE help me? Please? Is this happening to ANYBODY else?

** Package changed: firefox (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

** Summary changed:

- Firefox Not Load Most Pages Via Verizon Wireless DSL - DOES Load Them Using Wireless Dial-up Account - Workaround Included Within Posts
+ Firefox Not Load Most Pages Via Verizon Wireless DSL - DOES Load Them Using Wireless Dial-up Account - when ipv6 is enabled

You received this bug notification because you are a member of Mozilla
Bugs, which is subscribed to firefox in Ubuntu.

  Firefox Not Load Most Pages Via Verizon Wireless DSL - DOES Load Them
  Using Wireless Dial-up Account - when ipv6 is enabled

To manage notifications about this bug go to:

More information about the Ubuntu-mozillateam-bugs mailing list