Bug 15673 - Fab4 clock not always set - possibly if SP using remote SbS
: Fab4 clock not always set - possibly if SP using remote SbS
Status: CLOSED FIXED
Product: SB Touch
Classification: Unclassified
Component: API
: unspecified
: PC Debian Linux
: P2 normal (vote)
: 7.5.0
Assigned To: Felix Mueller
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-02-10 00:01 UTC by Alan Young
Modified: 2010-04-08 17:24 UTC (History)
4 users (show)

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Young 2010-02-10 00:01:17 UTC
It seems as though Fab4's kernel clock does not get set if its local SP (controller and player) are connected to a remote SbS, even in the case that TinySC is running and has connected players.

TinySC should probably set the system clock when it gets the time from SN. It would also be best if it only did this if the difference was > 15s so as to avoid small updates that could mess with synced play.
Comment 1 Michael Herger 2010-02-10 02:32:07 UTC
Alan - isn't this fixed by change 30112?
Comment 2 Chris Owens 2010-02-18 11:04:08 UTC
Alan is this something that you wanted to look at yourself?  My inclination would be to assign it to Felix.
Comment 3 Alan Young 2010-02-19 05:56:27 UTC
Sure, let Felix look at it.
Comment 4 SVN Bot 2010-02-24 09:20:14 UTC
 == Auto-comment from SVN commit #30244 to the  repo by fmueller ==
 == https://svn.slimdevices.com/?view=revision&revision=30244 ==

Fixed Bug: 15673 
Description: Set system time from SN if system and SN time differ by more than 15 seconds.
Comment 5 SVN Bot 2010-02-24 10:41:11 UTC
 == Auto-comment from SVN commit #30245 to the  repo by fmueller ==
 == https://svn.slimdevices.com/?view=revision&revision=30245 ==

Fixed Bug: 15673 
Description:
- Set system time from SN if system and SN time differ by more than 15 seconds. 
- Self contained solution without leaking into SqueezeNetwork.pm (Thanks Alan for pointing that out).
Comment 6 Chris Owens 2010-04-08 17:24:09 UTC
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release.

If you are still seeing this issue, please let us know!