Summary: | www-client/{mozilla-firefox-bin,seamonkey-bin} sees no DNS | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jeff Mitchell <jeffrey.mitchell> |
Component: | New packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | mike |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jeff Mitchell
2008-06-29 12:12:26 UTC
What does /etc/resolv.conf say? Does wget work normally? Do you really think you have uncovered a major bug in firefox/seamonkey or could this be a simple configuration error on your part? > What does /etc/resolv.conf say? Does wget work normally? /etc/resolv.conf is sane and points to my home router, which resolves DNS from upstream. wget works normally. konqueror works normally, firefox (not -bin) works normally, kopete works normally, pidgin works normally...in short, everything works normally except for firefox/seamonkey -bin. > Do you really think > you have uncovered a major bug in firefox/seamonkey or could this be a simple > configuration error on your part? No, my delusions of grandeur are not that big. I think I am hitting a bug in the Gentoo -bin builds of firefox/seamonkey, which may or may not have something to do with my machine configuration. As I said, self-compiled, non-bin, 64-bit versions work just fine. Tried with a clean profile? Quoting from the second sentence of my original report: "I have also tried it with a totally new, clean profile" Oops :D Well, then i have no idea. Tried unpacking the tarball and running it iself? I tried unpacking it from the tarball, deleting my profile, and running it from the unpacked directory. No dice. Then you should report this upstream I can try, but running on another x86_64 Gentoo box I do not have the same problem. Whatever it is seems localized to my box, but I have no clue what it could be. (In reply to comment #8) > I can try, but running on another x86_64 Gentoo box I do not have the same > problem. Whatever it is seems localized to my box, but I have no clue what it > could be. > Jeff, I have run into this numerous times, Firefox/SeaMonkey have a horrible problem with caching stale DNS info. I have found better results using the DNSCache plugin which allows you to disable FF's caching of DNS info, without voiding anything. Also you can tweak the DNS cache settings in about:config. Are you using DHCP or static IP, also what kind of DNS do you have setup? -Mike I was using DHCP, although the address it was given was static. DNS was being done through my home router. Anyways, I can no longer replicate this, because I have given up in disgust and gone to a 32-bit install. I needed Java applets working, and OpenJDK/IcedTea was too much of a hassle (although it worked). I had been wanting to use firefox-bin to get around the Java/Flash/wrapper stuff, but it wasn't worth fighting anymore. I'll leave this open since Mike Weissman at least is having the same problem. As no mozilla herd dev has been able to duplicate, I am closing. If you wish to have upstream track down the issue please file a bug report upstream, as all -bin packages in gentoo are from upstream. |