Bugzilla – Bug 15688
Player UI (SB 3/Classic) clock gets stuck - does not update after a WOL
Last modified: 2010-02-15 01:53:14 UTC
+++ This bug was initially created as a clone of Bug #10325 +++ I used to have bug #10325 which was fixed at 7.3.3 However, I have now noticed a similar (but slightly different bug) in my current setup. After my server wakes (on LAN) the SB3's clock is sometimes stuck at the time the server went into standby. Typically I turn that SB3 on and from then on it works fine. However, I have another SB3, in a different room, which often stays off. It just sits there showing the old time. At present, for example, it's showing the time from yesterday evening when my system last went into standby - there's no doubt it's stuck. Server version: 7.4.2 - r29251 Player firmware: 130 Unfortunately, I cannot exactly reproduce the bug every time. I've switched on logging network.protocol network.protocol.slimp3 network.protocol.slimproto and I'm going to try to reproduce it over today. If I can get it to do it I'll come back and add the log.
So I've definitely seen this happen three times over the last two weeks. It's not like it's a transient phenomenon: on one occasion one SB3 was obviously stuck on a time from the previous day, while the other was playing an internet radio station. I checked and the time on the PC was fine. On the other hand, since I've switched on logging I've been unable to reproduce. So it may be something rather odd and difficult to trace, like a race condition during the particular sequence of events when my PC resumes. Or even dependent on a particular sequence of packet loss. So I guess I won't be complaining if you leave this bug on hold until I can generate a better log, or a more reproducible test case.
I have also seen this happen a couple of times over the last week or so. However i am getting it with my SB3 connected to Squeezebox Server (TinySC) running on my Squeezebox Touch. I have not seen it on my Boom and i am unable to reproduce it at present. (In reply to comment #1) > So I've definitely seen this happen three times over the last two weeks. It's > not like it's a transient phenomenon: on one occasion one SB3 was obviously > stuck on a time from the previous day, while the other was playing an internet > radio station. I checked and the time on the PC was fine. > > On the other hand, since I've switched on logging I've been unable to > reproduce. So it may be something rather odd and difficult to trace, like a > race condition during the particular sequence of events when my PC resumes. Or > even dependent on a particular sequence of packet loss. > > So I guess I won't be complaining if you leave this bug on hold until I can > generate a better log, or a more reproducible test case.