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 602145 - Radio stations are marked as unplayable, even if Banshee can connect to them
Radio stations are marked as unplayable, even if Banshee can connect to them
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: Internet Radio
git master
Other Linux
: Normal normal
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
: 608412 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-11-16 23:38 UTC by Scott M Sanders
Modified: 2011-03-22 15:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch for the problem (894 bytes, patch)
2010-12-20 09:12 UTC, Alex
committed Details | Review

Description Scott M Sanders 2009-11-16 23:38:38 UTC
There's a red [X] that persists to the left of one of my stations that failed to load just once but has loaded every time since. It disappears on play but reappears on every subsequent Banshee startup.
Comment 1 Michael Martin-Smucker 2009-11-17 02:02:51 UTC
I can confirm this with git master.  The shape (X) and color (red) may vary from one icon theme to another, but the problem is real: once Banshee has determined a station won't play, it continues to mark it that way no matter how many times you successfully connect to it.
Comment 2 Alexander Kojevnikov 2010-01-29 06:45:45 UTC
*** Bug 608412 has been marked as a duplicate of this bug. ***
Comment 3 Gregor Wenkelewsky 2010-02-08 23:18:58 UTC
Exactly the same here, just one more info. I have this X mark at some radio stations too, all stations to which the connection failed at some time.
But as soon as I play a station, its X mark will disappear - and then all marks appear again after Banshee is exited and restarted again later.

(The only way to get rid of those seems to be deleting and re-creating that station, for now.)
Comment 4 Alex 2010-12-20 09:12:12 UTC
Created attachment 176747 [details] [review]
Patch for the problem
Comment 5 Alex 2010-12-20 09:12:57 UTC
I've written a one liner that fixes the bug for me.
Comment 6 Gabriel Burt 2011-03-22 15:15:11 UTC
Comment on attachment 176747 [details] [review]
Patch for the problem

Thanks Alex, committed