Bugzilla – Bug 12818
"Now Playing" on Controller sticks on a song and shows 59 mins length
Last modified: 2009-10-05 14:33:55 UTC
The "Now Playing" Screen is OK after a reboot (or after switching receivers to my Boom, and back) but after playing a few songs it "sticks" and just shows the same song from there on. The time bar extends to 59 minutes and is shows progress against that. However, all the commands on the Controller work normally. On the PC, the Squeezecenter interface shows the correct information - it's just the Controller which has this behaviour. This seemed to start after the firmware last got updated. I've tried a factory reset of the Controller, but the behaviour came back. I'm using Squeezecenter 7.3.3 on a Vista 64 PC with wireless connection to Duet Controller. Firmware is 7.3 r6038.
QA to verify on 7.4 branch when stable
Moving to the product SqueezePlay because this bug appears to apply to any player based on that application code. Feel free to move it back if it's specific to the single original product.
As James said - QA to verify with 7.4 :-) Tim - did you have a chance to test 7.4?
(In reply to comment #3) > > Tim - did you have a chance to test 7.4? No, I haven't downloaded 7.4, website says it is unstable... not used my squeezebox for a while, right now controller is behaving itself, I'll report back.
I have not been able to reproduce this, been testing for several weeks now. Please continue to monitor up-till GM
Happened on 7.3.3, not able to reproduce on 7.4. so I am marking as RESOLVED. Reopen if it reoccurs.
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server! * SqueezeCenter: 28672 * Squeezebox 2 and 3: 130 * Transporter: 80 * Receiver: 65 * Boom: 50 * Controller: 7790 * Radio: 7790 Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.