Description of problem: Although libcurl has support for asynchronous DNS through libcares, libcurl in Mageia doesn't seem to be built with such support. This causes GUI blocking in tools that use libcurl for networking, such as Virtaal. Version-Release number of selected component (if applicable): 7.28.1-6.1.mga3 Steps to Reproduce: 1. curl --version 2. the "Features:" line should contain "AsynchDNS", while on Mageia it doesn't I guess it might be some configure option or similar. libcurl had support for asynchronous DNS a few releases ago in Mandriva, and it has support in Fedora, if that helps. Reproducible: Steps to Reproduce:
Keywords: (none) => TriagedAssignee: bugsquad => boklm
Dan and I discussed the possibility of adding c-ares support to curl (more precisely, Dan explained me his point of view, since I know neither curl nor c-ares). I could post bits of our exchange here but it's a bit lengthy, and I think the topic of asynchronous DNS is wider than just c-ares support. Dan will probably be able to given some input.
CC: (none) => dan, remi
The problem with c-ares is that it is missing some functionality that the stock resolver has that some users would care about (lack of nsswitch support is the big one). An alternative is to compile with --enable-threaded-resolver which uses the stock resolver but spawns a thread to perform each resolve so they can be non-blocking. This wouldn't work well for high-performance applications that open thousands of connections at once, but those won't be using a stock distro-compiled libcurl, either. There was a thread about this recently on the libcurl list at http://curl.haxx.se/mail/lib-2013-08/0088.html. Apparently, Red Hat has been using this option for 4 years without issue. I would suggest enabling this on Mageia as well.
Thank you for the explanation. I'm not familiar with the different choices - I only speak for the user experience in a desktop application I'm developing that uses this. In as far as I can see from a quick check, things are working well in Fedora (no GUI blocking), so I guess it won't make a difference to me or the Virtaal application which of the choices are configured. DNS resolution can take multiple seconds where I live, so solving this provides a big improvement to the user experience of the affected applications.
Assignee: boklm => bugsquad
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD
This is still an issue in Mageia 4 and Cauldron.
Version: 3 => CauldronSource RPM: curl-7.28.1-6.1.mga3.src.rpm => curl-7.40.0-1.mga5.src.rpmStatus: RESOLVED => REOPENEDResolution: OLD => (none)
CC: (none) => marja11Whiteboard: (none) => MGA4TOO
Assigning to maintainer in case it's still valid.
Assignee: bugsquad => shlomif
This report saw no action since almost 5 years ago, therefore closing as OLD Feel free to reopen if it is still valid in current cauldron or Mageia 8
Status: REOPENED => RESOLVEDAssignee: shlomif => bugsquadResolution: (none) => FIXED
(In reply to Marja Van Waes from comment #7) > This report saw no action since almost 5 years ago, therefore closing as OLD > > Feel free to reopen if it is still valid in current cauldron or Mageia 8 again closing as OLD
Resolution: FIXED => OLD