Randomly stops playing radio streams

[Bryce Harrington]

Binary package hint: rhythmbox

While playing radio streams (such as from HBR2.com), Rhythmbox will periodically stop playback without issuing an indication why it stopped. I can usually restart it without issue by just clicking 'play' again.

The root cause of this might be deeper in one of Rhythmbox's dependencies (e.g. gstreamer), however it is a Rhythmbox bug that it is not reporting an error message as to why playback has stopped.

[Bryce Harrington (bryce)]

Here is a backtrace taken at a point after the playback has stopped.

[Sebastien Bacher (seb128)]

Thank you for your bug. What version of Ubuntu do you use? Do you have anything printed about that if you run "rhythmbox -d"? Getting a gstreamer log with "GST_DEBUG_NO_COLOR=1 GST_DEBUG=5 rhythmbox 2>log" could be useful (maybe the debug level 3 would be enough, if the bug happens only after some time log 5 will create lot of log). Maybe you can try if you get the same behaviour with "gst-launch-0.10 playbin uri=..."

[Bryce Harrington (bryce)]

This is with Ubuntu Feisty.

Here is a log with GST_DEBUG=3 when it ceased playback. Playback stopped after 44 minutes of http://ubuntu.hbr1.com:19800/ambient.ogg. No error message dialog popped up, and nothing appeared on the console beyond what's included in this log.

I'm running with the gst-launch command currently and will report if I see the same issue or not.

Bryce

[Bryce Harrington (bryce)]

Here is the output from running "gst-launch-0.10 playbin uri=...". Again, it ran for about 30-45 minutes before stopping play. During this time there were several "drop outs" where playback stopped for about 1 sec or less and then restarted. These dropouts correspond to the 'Unexpected discontinuity' error messages.

However, I see the underlying error message now: 'Got EOS from element "playbin0"'. This is probably what needs to get propagated up to the UI.

Next I'll try running rhythmbox -d. Anything else I should try?

Thanks,
Bryce

[Bryce Harrington (bryce)]

Here is the tail output from running rhythmbox -d.

[Bryce Harrington (bryce)]

I've also tried running with debug level 5, but the bug never showed itself; perhaps with that much debugging, it slows things down enough that it doesn't lose synchronization or something maybe?

[Sebastien Bacher (seb128)]

You get the problem with gst-launch so that's a gstreamer problem, I've forward it upstream: http://bugzilla.gnome.org/show_bug.cgi?id=407634. There might be a small request for rhythmbox which could also display a dialog (if gstreamer sends an error and not simply stop playing)

[Sebastien Bacher (seb128)]

comment from upstream:

"Could you provide a working example URI that demonstrates the problem please?

The one mentioned in the launchpad bug doesn't seem to work (or rather: I can't
reach hbr1.com, and hbr2.com looks like a random search engine/ad spam site).

I suspect the problem is chained oggs though (= bug #320984)."

[Bryce Harrington (bryce)]

I've encountered this problem with several streams, however the ones used in all the above reports are:

http://ubuntu.hbr1.com:19800/ambient.ogg
http://ubuntu.hbr1.com:19800/trance.ogg
http://ubuntu.hbr1.com:19800/tronic.ogg

I used these URLs because they come configured as defaults in Ubuntu's rhythmbox.

[I posted this info upstream as well.]

[Sebastien Bacher (seb128)]

bug #32858 is similar to this one

[Ivan Razumov (iarspider)]

Not sure if this is the same bug, but I have similar problem. But in my case I get a message: "failed to seek; server does not accept Range HTTP header".

Here is the full output:
=======================================================
$ gst-launch-0.10 playbin uri=http://mp3.nashe.ru:80/nashe-128
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstAudioSinkClock
Buffering, setting pipeline to PAUSED ...
ERROR: from element /GstPlayBin:playbin0/GstSoupHTTPSrc:source: "http://mp3.nashe.ru:80/nashe-128": failed to seek; server does not accept Range HTTP header
Additional debug info:
gstsouphttpsrc.c(677): gst_soup_http_src_got_headers_cb (): /GstPlayBin:playbin0/GstSoupHTTPSrc:source
Execution ended after 75382123495 ns.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
FREEING pipeline ...
=======================================================

I can attach output from running rhytmbox (degug level 5), but it's rather large (~800 MB).

[Sebastien Bacher (seb128)]

could you try if that's still an issue in jaunty?

[Bryce Harrington (bryce)]

Still an issue in Jaunty. Just happened yesterday in fact, and has been happening fairly routinely since the original report.

[Phasmus (phasmus)]

This bug has been bothering me in Hardy, Intrepid and Jaunty. Rhythmbox and Banshee alike. In Hardy with Rhythmbox channels that failed would sometimes refuse to load again until I restarted the program. In Jaunty with Banshee I can restart them easily but it's still annoying.

[trailblazer (rulavan)]

Still in Karmic...

[Michael Düll (akurei)]

Still happening =(

[sheril (shershnov)]

Have the same problem, but only when using internet via my home wi-fi acsess point. When i connect with ethernet cable, it works fine!

[reitsma (reitsma)]

I have the same in Karmic.
Very annoying. This makes Ubuntu and derivative Mint a lesser distro.
I use LAN ADSL.
I had it in Ubuntu 8.10 and Mint 6 too.
I don't know what to do about it? Wait for updates?

[Pasquale Di Gennaro (pasquale-digennaro)]

I'm using ubuntu 9.10. I experience a similar problem (rhythmbox randomly stopping playing radio) just at home where I have a not so good adsl connection and a wireless access point. No problem at work, where I have a very stable and fast connection.

So I think that this bug is related to the quality of the internet connection.

I do not know if this helps, but at home I have similar problems with wget, which randomly stops when downloading big files. No problem at all while streaming video with moonlight....

[Bryce Harrington (bryce)]

Haven't had this trouble on ubuntu for a while now. I changed ISPs last year from comcast to verizon. Perhaps it was a problem specific to my last ISP?