After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 606574 - Rhythmbox exhibits annoying 5 seconddelay with ipv6 disabled
Rhythmbox exhibits annoying 5 seconddelay with ipv6 disabled
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
unspecified
Other Linux
: Normal major
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-10 18:04 UTC by careta
Modified: 2010-07-15 10:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Complete debug output (5.61 KB, application/octet-stream)
2010-01-10 18:04 UTC, careta
Details

Description careta 2010-01-10 18:04:50 UTC
Created attachment 151135 [details]
Complete debug output

Hi,

I am experiencing annoying 5 seconds delay when playing a new file with ipv6 disabled on Debian Squeeze.

This delay only happens when a new track starts playing, but on every track play. Sound quality is not affected, and there is no delay while the track is playing.

The cause is the absence of ipv6. If I blacklist the ipv6 module and reboot the computer the delays start. If I remove it from the blacklist, Rhythmbox plays fine.

I'm using Rhythmbox 0.12.6. The delay is clearly visible on these 3 lines:
(17:57:42) [0xc98040] [set_state_and_wait] rb-player-gst.c:615: playbin reached state READY
socket(): Address family not supported by protocol
(17:57:47) [0xc98040] [set_state_and_wait] rb-player-gst.c:571: state change is taking too long..

The "socket():.." message appears on a console even without the -d option.


Attached is the complete debug output.


Regards,
Pedro
Comment 1 Jonathan Matthew 2010-01-10 21:41:36 UTC
This is a GStreamer problem, most likely caused by an audio sink element attempting to use ipv6 for something (no idea what it might be).  Output from 'GST_DEBUG=*:4 rhythmbox -d' might help.
Comment 2 Wim Taymans 2010-01-13 10:56:52 UTC
I have no idea where to look.. could it be pulseaudio or something else in the backend doing something weird?
Comment 3 Sebastian Dröge (slomo) 2010-01-14 11:20:29 UTC
IMHO this looks like a network configuration problem but a debug log like Jonathan said would be really useful.
Comment 4 careta 2010-01-16 19:38:15 UTC
Hi, sorry for the late reply.

This is not a network configuration problem: it happens when I'm disconnected from the network, the streams are local and I'm not using any exotic configuration - just the safe Debian defaults.

It is also not pulseaudio, since I don't have it installed. 

I will gladly capture the output for you, but apparently it consists of thousands of lines. Redirecting with "GST_DEBUG=*:4 rhythmbox -d > output" does not work... Is there a way to redirect to a file instead of to the console?
Comment 5 Sebastian Dröge (slomo) 2010-01-16 20:03:25 UTC
GST_DEBUG=*:4 rhythmbox 2>&1 > output

should work.
Comment 6 careta 2010-01-19 17:57:32 UTC
Hi,

it didn't work, millions of lines outputted to the console. 

However, after I removed GNOME (I'm using LXDE now) it is working! No more 5 second delay. Let me know if you need more info, but i removed hundreds of packages from my system, so I probably won't be of much help...
Comment 7 Tobias Mueller 2010-07-15 10:48:21 UTC
Hm. I'm closing as INCOMPLETE then. Please reopen if you can still reproduce it.