Closed Bug 496597 Opened 15 years ago Closed 15 years ago

[3.5Beta99testday][Linux] Firefox 3.5b99 cannot browse

Categories

(Firefox :: General, defect)

3.5 Branch
x86_64
Linux
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 414197

People

(Reporter: u279076, Unassigned)

Details

(Whiteboard: 3.5Beta99testday)

Attachments

(2 files)

Attached image Screenshot
Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1b99) Gecko/20090604 Firefox/3.5b99

OS: Ubuntu 9.04 64-bit

STR:
1. Open FF3.5b99 with a new profile
2. Navigate to www.mozilla.org
3. Open Shiretoko with a different profile
4. Navigate to www.mozilla.org

RESULT:
FF3.5b99 -> Server not found
Shiretoko -> page loaded

EXPECTED:
FF3.5b99 should load the page

Mac build appears to be working ok.
Flags: blocking-firefox3.5?
Summary: Firefox 3.5b99 cannot browse → [Linux] Firefox 3.5b99 cannot browse
Is this the firstrun page? Maybe there's a problem with the url, I'd suggest trying google...
Summary: [Linux] Firefox 3.5b99 cannot browse → [5Beta99testday][Linux] Firefox 3.5b99 cannot browse
Whiteboard: 5Beta99testday
Summary: [5Beta99testday][Linux] Firefox 3.5b99 cannot browse → [3.5Beta99testday][Linux] Firefox 3.5b99 cannot browse
Whiteboard: 5Beta99testday → 3.5Beta99testday
(In reply to comment #1)
> Is this the firstrun page? Maybe there's a problem with the url, I'd suggest
> trying google...

No, as you can see from the screenshot, I am attempting to load www.mozilla.org.  I also tried this with www.google.ca and achieved the same result.

It appears as though this is a 32-bit build and I am using a 64-bit OS.  The archive name "firefox-3.5b99.tar.bz2" does not indicate that this will NOT work on 64-bit.  Traditionally, platform is indicated in the file name.  Leaving this information out makes me think this is not a bit-specific build.  This is where I got confused I suppose.

Resolving this bug INVALID.  I'll just have to wait until we get 64-bit builds.
Flags: blocking-firefox3.5?
Could be bug 414197. You could you try setting network.dns.disableIPv6 to true and see if it helps.
(restoring INVALID, don't think Sylvain meant to re-open this as the other bug is also INVALID)
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
I didn't reopen it, it wasn't marked INVALID before. Maybe Anthony wanted to test with the 64-bit build before marking it so? But in any case I agree it shouldn't block.
If someone seeing the symptoms can confirm this is bug 414197 we can mark it as a duplicate.
There is no 64 bit build. the same build is used for 32 and 64. Firefox.next may have 64 bit, but not now. Have you checked for firewall settings? http://support.mozilla.com/en-US/kb/Firefox+cannot+load+websites+but+other+programs+can may help.
Attached image Build list
Actually, we do create 64-bit builds, for Linux.  We don't on Windows, but Linux we do.  We have for a long time.  This is because I was running a 32-bit build on 64-bit.
Marking verified.  No 64-bit builds existed at the time and I assumed the 32-bit build would work.  Running the same build on 32-bit worked.  No further action needs to be taken on this bug.
Status: RESOLVED → VERIFIED
(In reply to comment #7)
> Actually, we do create 64-bit builds, for Linux.  We don't on Windows, but
> Linux we do.  We have for a long time.  This is because I was running a 32-bit
> build on 64-bit.

Just to clarify, there are 64-bit builds for nightlies, but not for official Linux releases (no 64-bit builds are available from http://www.mozilla.com/en-US/firefox/all-beta.html or ftp://ftp.mozilla.org/pub/firefox/releases/3.5b4/).
Yes, that was what I meant, sorry for the confusion.
Which brings me to the point: Users on Ubuntu 9.04 64bit that may want to give
3.5 a try may encounter this issue, because they won't be able to get a 64-bit
builds from http://www.mozilla.com/en-US/firefox/all-beta.html.

So maybe the release notes should mention that if users on Ubuntu 9.04 64bit
are getting "Server not found" error messages, they should install the
lib32nss-mdns package.
Marking as a dupe of 414197, please correct if you have another explanation.
Status: VERIFIED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: INVALID → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: