André Offringa <of**@gm**.com> reported this problem on the Debian tracker:

"I am running ntpdate on my laptop, and when I have worked some time without
Internet, my system time might be quite rigurously changed by ntpdate. If
this happens, Workrave continuous to work correctly, and pops up the next
micro break correctly: the timer starts to count down to 0. However, once it
has reached 0, the micro break window does not dissapear, leaving my computer
in a frozen state, as I can not type or close windows either. I have also
seen the counter jumping to a very high value, e.g. two hours to count down,
but that happens less often."

I'm not sure exactly what the problem he's describing is about, so feel free to ask for clarifications, I'll relay your comments over to him.

Cheers,
Francois

Maybe I should try explaining it more briefly: changing the system time causes Workrave to malfunction. The Workrave micro break screen does not dissapear when the break is over.

(though this looks like a some weird border case, it actually happens quite often on my laptop)

Regards, André

*** Bug 745 has been marked as a duplicate of this bug. ***

Thanks. I managed to reproduce the bug.

On Windows, Workrave can distinguish between hibernate/suspend and the system time being changed. On Linux, Workrave cannot make this distinction, so it assumes are time changes are hibernates; even negative changes or small changes.

Workrave now assumes negative and small positive changes (< 10 minutes) are the result of the time being changed. > 10 minutes is considered the result of a hibernate. (during a hibernate, workrave assumes you are idle. time gaps as result of the time being changed are ignored).

I know, it's not perfect, better ideas are welcome.