Bug#490203: gworldclock runs about 50 seconds behind

2009-06-09 Thread Paul Gotch
On Tue, Jun 09, 2009 at 02:18:27AM +1000, Drew Parsons wrote: > Since one of the reasons for not displaying the seconds is that you > really don't care that much about to that degree of accuracy, I'm not > entirely convinced it's worth complicating the timer handling to deal > with it. I'll leave

Bug#490203: gworldclock runs about 50 seconds behind

2009-06-08 Thread Drew Parsons
I think this is just an aliasing artifact. When seconds are not displayed, gworldclock only updates once per minute. There are no rules on which part of that minute it will update in, it will depend on when you launch the program. Try timing it to launch right at the stroke of the minute hand an

Bug#490203: gworldclock: runs about 50 seconds behind time as reported by date if not displaying seconds

2008-07-10 Thread Paul Gotch
Package: gworldclock Version: 1.4.4-6 Severity: important gworldclock appears to run about 50 seconds behind the time as reported by "date" if seconds are not being displayed. If seconds are being displayed then it displays the correct time. I'm using a custom display format of %x %H:%M GMT%z %