Does anyone else have time problems w/7.1.7?

[texneus]

I filed a bug report late last night but I've seen no-one else mention this so I thought I would...

I just noticed last night my system clock had drifted pretty far off the mark. SageTV (7.1.7 beta) is set to sync with the SageTV time server at guide updates but apparently it is not. If I go to setup and try to toggle the setting, it cannot be disabled (just stuck on enabled). Regardless, I looked in my SageTV properties file and it shows time sync is disabled and time zone is blank. Since my clock had drifted about 30 seconds since installing 7.1.7 ~1 month ago, I assume it is indeed not synchronizing. Manually synchronizing using the built in Windows 7 tools corrected the clock (for now).

[matt91]

weird - i had this problem too. I was 8 minutes (!!) fast the other day. My wife saw the time on Sage and said "is it really xxx time already?" I assured her that Sage was always right on time, and that her watch was wrong.

I later found out that Sage had advanced about 8 min.

I updated it pretty easily, and it seems OK since then. strange, though, as I've never had to worry about the clock on this server (other than the DST jave issue a couple of years ago).

[Narflex]

Originally Posted by texneus

If I go to setup and try to toggle the setting, it cannot be disabled (just stuck on enabled). Regardless, I looked in my SageTV properties file and it shows time sync is disabled and time zone is blank.

We've fixed this issue for V7.1.8 already. For now, if you just change the value in Sage.properties for clock sync to be true you'll be fine (but the next beta should be out this week).

[KeithAbbott]

Originally Posted by Narflex

(but the next beta should be out this week).

Excellent. And Hauppauge is supposed to have a new version of the Colossus driver out any day now, per SHS. Here's hoping for a stable and reliable Colossus in the days to come!