I have 17 different radio streams. I'd like to be able to use the alarm extension so I could wake up to one of them playing.

However, I can't do this because Banshee (2.2 daily build) never, and I do mean never, connects to any of them on the first try.

If I click to play any radio stream, on the first try it says "Contacting...", and then it says "Idle", and a little X mark appears beside the name of the station.

However, if I click it a second time, it works fine.

It always goes like this. Without fail. I can never connect on the first try, and I can almost always connect on the second try.

I don't know how close together the two tries have to be in order to work.

What I do know, though, is if I use the Alarm extension to start playing a radio stream in the morning, nothing happens in the morning because it attempts to connect and then fails and gives up trying.

Any advice on how to solve this would be appreciated.

See also:

  • 2
    What happens if you use the stable build rather than the daily build? - sounds like a bug which you should report to the banshee maintainers. – fossfreedom Oct 29 '11 at 8:31
  • 2
    ... I see that you took my advice :) bugzilla.gnome.org/show_bug.cgi?id=662909 – fossfreedom Oct 31 '11 at 20:21
  • 1
    @fossfreedom: I've learned not to put all eggs in one basket when seeking help. :) – Questioner Nov 1 '11 at 1:33
  • @DaveMG Relevant reading – ændrük Nov 3 '11 at 16:24
  • 2
    @DaveMG I apologize, my last post was unnecessarily rash. What I mean to convey is that the answer is relevant because 1) it explicitly condones cross-posting to disconnected support avenues, and 2) its respect-based rational for the policy on inter-SE cross-posting is applicable to the general case. My hope in bringing your attention to each of these points is to 1) arm you with established justification for the cross-posts you made, since you seemed hesitant to share them with us, and 2) convince you to link to them, not out of obligation, but out of respect for the others on this site. – ændrük Nov 4 '11 at 11:53

I have encountered this problem in Banshee as well. I also use the daily builds (as of this past week or so again) - and in my experience it seems to mainly occur in the daily builds and not in the Stable release.

My guess to the cause

To my knowledge there is no real "fix" that you can apply, because it seems to be both a problem in Banshee and in the radio stations themselves. When I was still on Windows, this also used to happen with some radio stations. It seems to be a server side issue (partially), in that when you first try to connect, it fails and thus the music player marks it as unavailable (hence the x).

On the other hand, once the music player is told to try again, it finds the station - apparently after the server allots "space" to your player (that's just my guess).

The real answer:

I would suggest you simply wait on a fix from the Banshee developers, which will probably include having the player retry the station a few times. It is very unlikely that there is anything you can do on your end.

You could also try the stable build of Banshee, which seems to do better in this situation.

Alternate solution:

Another option may be to use another player, such as Clementine (for example), which may be able to play the station even if it reports itself as down at first (I have not tried this). You could use either a cron job or a timer application (there are numerous timer apps available) for the alarm functionality.

  • To be totally honest, I was hoping for a more concrete solution of some kind, but I guess you're right that it's just a matter of waiting and hoping Banshee developers fix it. I'll give Clementine a look, as I used to like Amarok 1.4. I just want a music player that works... – Questioner Nov 5 '11 at 5:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.