Red Hat Bugzilla – Bug 970294
Rhythmbox not playing radio statio
Last modified: 2015-02-17 10:26:50 EST
Description of problem:
Rhythmbox not streaming radio stations on Fedora 19 beta x86_64
Version-Release number of selected component (if applicable):
Enter a radio station (http://eno.emit.com:8000/fbi_live_64.aacp) and try to stream
Steps to Reproduce:
1. Start rhythmbox
2. Enter radio station URL
3. Hit play
I checked /var/log/messages. Immediately after starting rhythmbox this message begins to appear until does not stop until I log out of my cinnamon session (several messages per second)
Jun 2 15:21:10 winter /etc/gdm/Xsession: (cinnamon:3839): Clutter-CRITICAL **: clutter_text_get_text: assertion `CLUTTER_IS_TEXT (self)' failed
Jun 2 15:21:10 winter /etc/gdm/Xsession: (cinnamon:3839): Clutter-CRITICAL **: clutter_text_set_text: assertion `CLUTTER_IS_TEXT (self)' failed
Created attachment 756547 [details]
cpuinfo & lspci
Same problem on i686
However, some radio streams do work (http://ubuntu.hbr1.com:19800/ambient.ogg), while others don't (http://18.104.22.168:8100/listen.pls, or the example you gave). Perhaps because of the different stream type?
I do not see the /var/log/messages problem, though.
I can confirm this issue too in Fedora 19 x86_64 stable. None of my radio stations are played when using rhytmbox:
Name : rhythmbox
Arch : x86_64
Version : 2.99.1
Release : 1.fc19
I don't have either a trace in /var/log/messages.
As it stands now, the error messages only occur if you run the program from the command line /usr/bin/rhythmbox
I began to use banshee for radio and that works fine
In my case it does not matter if I run rhythmbox from the command line or from Gnome Shell, none of the stations are played. Althought I found some interesting behavior:
If I add one station URL with a .pls on it, it works (i.e.):
But adding one of the URLs inside the playlist as I used to do in previous versions, it does not work anymore:
This happens in all radio stations that I've tested so far.
This might be related to the following ubuntu bug https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1173510 and upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=639777
Note that gvfsd-http actually WILL start receiving data from the stream and apparently saving it in a buffer, eventuall eating up ALL memory. Even if you quit rhythmbox, it will continue to do so. So perhaps this is a bug in gvfsd-http, not rhytmbox? Clearly, gfvsd-http should stop doing whatever it is doing for some other process once that process is terminated.
The workaround is to kill gvfsd-http after you double clicked the stream in rhythmbox. rhythmbox will then, without any further action needed, re-establish the connection and start playing the music.
Same problem here.
(In reply to Peter Backes from comment #6)
> The workaround is to kill gvfsd-http after you double clicked the stream in
> rhythmbox. rhythmbox will then, without any further action needed,
> re-establish the connection and start playing the music.
Works as explained, but is not very practiacal ;)
I've been seeing the same issue since I upgraded from Fedora 18 to 19. Killing the gvfsd-http does provide a temporary workaround.
Is this something that needs to be fixed in the gvfs package or in rhythmbox?
Also happening here (with same workaround of killing gvfsd-http)
$ rpm -q rhythmbox libsoup gvfs
Anything useful for debugging?
Still not working with rhythmbox-3.0-3.fc20.x86_64
Now working properly (at least after reboot).
I have moved to f20 where this is working fine
After applying the latest updates, it works for me as well. Confirmed on my end.
Works here too! Thanks!
But not in Clementine...
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.