Bugzilla – Bug 9759
Error messages should eventually time out
Last modified: 2011-11-06 23:24:43 UTC
I was playing an MP3 from my local server and got an error (CONNECTION TIMED OUT) displayed on the SB3. I picked up my SBC and skipped to the next track, audio changed as appropriate, but the error message stayed up. Still here, the next day. (CONNECTION TIMED OUT bug is submitted as bug 9758).
Dean, I'm not saying that you are wrong, but I cannot find where this could have come from for local tracks. It is the case that many of the plugins replace the title of the current track (stream/station) with an error message when some sort of long-term error occurs, but you say that this happened with local tracks. As far as I can tell local-track errors are always just show-brieflies. Even with the plugins, restarting playback in any way should change the current title again. It is interesting that you typed it in all upper-case. Do you recall if it was on the top line (which is always single-case)? I wonder if there is some mechanism to override the contents of the top line that I don't know about and which is being used here.
this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.
Some error conditions cause the top line of a player-UI display to be replaced with an error message. I think that this is mostly or completely confined to certain services. When this happens, the error message never gets cleared. Possible the error message is only present on the Now-Playing screen. Andy, Triode, I cannot find where in the code this top line could be getting set like this. Any clues would be appreciated.
--debug player.display should help you identify where this is coming from (suggest doing with only one ip3k player attached)
The biggest problem is recreating it in the first place. I have seen it twice in the past 6 months.
Unassigned bugs cannot have a priority.