On Friday 30 March 2018 16:36:19 D. R. Evans wrote:
On Friday 30 March 2018 09:08:54 D. R. Evans wrote:
I'm not sure where to report this:
I have three 24-hour TDE clocks in a panel: one on local time; one on London time; and one on UTC. The London and UTC clocks are reading the same time, but I discovered yesterday that in fact London is already on summer time (and has been for nearly a week, I understand), so the London time should be displaying a number one hour higher than UTC.
I have more info on this now, but still don't know where best to report it.
The additional info is that logging out and logging back in -- which is something I rarely do; I often go weeks without doing so, but I happened to do it today -- "fixed" the problem.
So what appears to happen (this is a guess, but it fits the evidence) is that the clock figures out the time in London at log-in time, and then starts free-running, keeping the same offset between the displayed time and UTC, regardless of subsequent changes to/from summer time that might occur during the logged-in session.
In any case, the fact that the clock is unreliable and can display an incorrect time is obviously a bug, and I would hope that someone can look into the issue. (FWIW, the local clock -- Denver -- quite happily adjusted the time automatically and correctly earlier in the month.)
Doc
This doesn't happen on my system. It makes no difference if I stay in the same session continuously for days or even weeks without rebooting, or a new log-in.
I have actually watched the clock on my desktop at the moment the time changes for daylight savings, or changes back in the fall; it just automatically skips an hour, forwards or backwards, at 2 a.m. I just watched this happen a few weeks ago (11th of March) when the time changed here locally.
Then again, I only use one clock, not three. It could be that they somehow interfere with one another; but it sounds like maybe this is your customary setup? (I chat with people in many different time zones, but I just mark different cities in my clock, then change my local time. Or, I use the very handy Trinity World Clock. Otherwise, I have a time zone map for reference.)
Otherwise, maybe the bug is in your version of Trinity, or is in your OS. I run Debian Jessie, with the Trinity r14.0.4 desktop. What are you running?
Bill