GNOME Bugzilla – Bug 544183
souphttpsrc is not doing lookups properly
Last modified: 2009-01-17 15:19:42 UTC
I have a livecd with gstreamer installed, it booted without the network card configured so I had the following configuration in /etc: 127.0.0.1 localhost.localdomain localhost Using playbin from gst-launch will yield following error message: ERROR: from element /playbin0/source: Cannot resolve hostname Additional debug info: gstsouphttpsrc.c(683): gst_soup_http_src_finished_cb (): /playbin0/source: libsoup status code 2 ERROR: pipeline doesn't want to preroll. This is the wrong behavior, and might very will be a bug in libsoup itself. Using gst-plugins-good 0.10.8-7.fc9 and libsoup 2.4.1-1.fc9
Sorry, I forgot to mention the complete launch line I used: $ gst-launch playbin=http://localhost.localdomain:8800/ Using 127.0.0.1 instead of localhost.localdomain works as expected
Does 'ping localhost.localdomain' work?
Yes, pong localhost.localdomain works, host localhost.localdomain does not. nsswitch.conf is not being honoured for some reason, I'm trying to track down which libc/socket call is used and which one should be used.
ping does the following: inet_aton("localhost.localdomain", 0x8062ae4) = 0 idna_to_ascii_lz(0xbfd199ec, 0xbfd17c84, 0, 0, 0x1d2658) = 0 gethostbyname("localhost.localdomain") = 0x33cac4 I cannot get ltrace to work on soup/gstreamer, so I cannot check that.
maybe you need to ltrace gst-launch-0.10 rather than the gst-launch wrapper?
I still can't reproduce this. If I disable network in NM, so that /etc/resolv.conf is just comments and blank lines, and /etc/nsswitch.conf says: hosts: files dns I can still resolve all of the hostnames in /etc/hosts fine. If you want a simple test case, build libsoup from svn and use tests/dns: danw@spellbook:tests> ./dns localhost Name: localhost Address: 127.0.0.1 danw@spellbook:tests> ./dns foo Name: foo Error: Cannot resolve hostname You may want to "strace -f" in addition to ltrace, to see what config files it's reading...
NEEDINFOing since I can't reproduce this (In reply to comment #6) > You may want to "strace -f" in addition to ltrace, to see what config files > it's reading... and that's "strace -s 8192 -f" to make sure it gets lots of I/O goodness
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!