Comment 259 for bug 417757
Revision history for this message
| Steve Langasek (vorlon) wrote Re: [Bug 417757] Re: [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups | #259 |
On Sun, Mar 07, 2010 at 07:01:53AM -0000, Ricardo Fernández wrote:
> What part of "disabling IPv6 doesn't fix this issue" you didn't read?
> seriously, I'm starting to get tired of saying this didn't fix the bug
> for me, and few others keep saying the same, are you guys really not
> reading the posts? Just because the status was changed to "Fixed"
2> doesn't mean it is really fixed if people are still getting the same
> problems.
Conversely, having the same symptoms (and as much as anyone has shown
here since the fix for this bug was verified is that "their network is
slow", which is a very broad symptom) doesn't mean this bug isn't fixed.
You say you've disabled ipv6. How did you do this? Do you have network
traces showing that eglibc is still sending the wrong DNS queries?
I have personally retested the karmic version of libc6 in response to your
message here. The bug described in this report is fixed - a system with no
routable ipv6 addresses will not generate AAAA DNS queries with libc6
2.10.1-0ubuntu16 installed. So whatever problem you're seeing should be
tracked in a separate bug report.
> And don't tell me it is fixed because otherwise i wouldn't be posting
> here don't you think ?
No offense, but experience shows that with high-profile bugs where the
symptom is described in such general terms as is the case here, users *very
frequently* follow up when the problem they're experiencing has nothing to
do with the bug report in question.
> Really c'mon guys, why it is so hard? If it is fixed for you, nice!
> congratulations! now move along, we have people here that still have
> problems (including myself).
If it's fixed for them, then it's almost 100% certain that people still
experiencing problems have a different bug. Different bug -> different bug
report.
(If you're reading this because you *did* file a separate bug and your bug
was marked as a duplicate of this one, then that was a mistake and we should
correct that status. Unfortunately, Launchpad's UI doesn't make it easy to
figure out which commenters in a bug report filed which duplicates, and
encourages users to all follow up to the master bug.)
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://
<email address hidden> <email address hidden>