FS#26007 - [glibc] Internet problems with 2.14-6

Attached to Project: Arch Linux
Opened by Polo (lihato) - Wednesday, 14 September 2011, 12:47 GMT
Last edited by Allan McRae (Allan) - Sunday, 30 October 2011, 06:50 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Allan McRae (Allan)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 7
Private No

Details

Description:

Upgrading from glibc 2.14-5 to glibc 2.14-6 creates problems with what seems to be name resolving. With Firefox, uzbl or privoxy, one have to refresh the website once or twice to get the full page to disblay fine.

I also noticed some problems with mutt, newsbeuter (RSS). I have to run them twice to get everything up to date.

Reverting to glibc 2.14-5 solves the problem.

Locale is fr_FR.UTF-8
Several guys on the french board have the same problem.
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 30 October 2011, 06:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  glibc-2.14.1-1
Comment by Polo (lihato) - Wednesday, 14 September 2011, 12:54 GMT
Typical behavior with privoxy:
- the website does not show up (the domain name could not be resolved);
- refresh: the page displays fine, except content that comes from other domains;
- second refresh: everything shows up.
Comment by Amethyste (Amethyste) - Wednesday, 14 September 2011, 13:01 GMT
Same problem with i686 package. I use the same locale too. I downgraded too and it solved my problem
I must add when I used AUR I've got the message "curl error" with no other precision. Hope it could help

Edit :
With glib 2.14-6 wget -4 <url> seems to work perfectly. wget <url> (so without -4) work badly
With glib 2.14-5 wget -4 <url> or wget <url> both work perfectly fine
Comment by Polo (lihato) - Wednesday, 14 September 2011, 20:49 GMT
I can confirm the IPv4/v6 problem with wget.
Comment by Kevin (kjslag) - Wednesday, 14 September 2011, 22:10 GMT
Downgrading and rebooting didn't work for me. I also can confirm the wget issue.
Comment by Kevin (kjslag) - Friday, 16 September 2011, 06:14 GMT
Disregard my comment. The comment is true, however ubuntu isn't working for me either. I think the problem is related to my new router, which doesn't bother windows for some reason.
Comment by Tom Gundersen (tomegun) - Sunday, 25 September 2011, 22:23 GMT
FWIW, I'm seeing similar behavior, though not entirely identical:

I'm using dnsmasq via NetworkManager.

$ git remote update
always gives "fatal: Unable to look up anongit.freedesktop.org" on first try, and works fine on the second.

I have not noticed any problems with my browser (Chromium), but it might just be retrying automatically for all I know.
Comment by Kevin (kjslag) - Monday, 26 September 2011, 01:15 GMT
I think chromium tries many DNS lookups at once and uses the first result. I think firefox uses the standard system DNS lookup (I forget the function name). And for me, firefox is sometimes slow at DNS lookup (only with new sites).
Comment by Allan McRae (Allan) - Tuesday, 27 September 2011, 05:05 GMT
Please test:
http://allanmcrae.com/tmp/glibc-2.14-6.1-i686.pkg.tar.xz
http://allanmcrae.com/tmp/glibc-2.14-6.1-x86_64.pkg.tar.xz

and report if it fixes the issue.
Comment by Amethyste (Amethyste) - Tuesday, 27 September 2011, 07:45 GMT
For me it slightly improve Firefox but kmail still doesn't work and I still have to force IPv4 with wget. I used the i686 package.
Comment by Polo (lihato) - Tuesday, 27 September 2011, 09:40 GMT
The bug is still there for me. glibc 2.14-5 still solves the problem.

Thank you for taking care of this, Allan.
Comment by Tom Gundersen (tomegun) - Wednesday, 28 September 2011, 11:11 GMT
Just tried 2.14-6.1, and git still does not work.
Comment by Polo (lihato) - Thursday, 20 October 2011, 16:18 GMT
Today updates seem to solve the problem.
Comment by Tom Gundersen (tomegun) - Thursday, 20 October 2011, 16:23 GMT
Please ignore all my comments on this bug. I was being a moron and not checking carefully enough what was happening. Turns out I just had a bad DNS server, switched to a good one and now everything is the way it should be. Sorry for the noise.
Comment by Allan McRae (Allan) - Friday, 21 October 2011, 01:00 GMT
@lihato: what did you update?
Comment by Amethyste (Amethyste) - Friday, 21 October 2011, 07:00 GMT
Today update doesn't change a thing for me
Comment by Allan McRae (Allan) - Tuesday, 25 October 2011, 09:42 GMT
I went back to the crappy workaround from glibc-2.14-4 again in glibc-2.14.1-1 as neither of the patches appear to fully fix the issue. This is all due to crappy DNS servers, so everyone who was affected should look into changing that because there is no guarantee that the workaround will stay once more commits get made to that area of the code...
Comment by Allan McRae (Allan) - Tuesday, 25 October 2011, 09:42 GMT
Also, please confirm glibc-2.14.1-1 fixes the issues for you.

Loading...