Testcase:
In the office, you have a desktop and a laptop, both running workrave connected
via the network. Lock your desktop for the night. Shut down the laptop. Leave
for home. Come back the following day, unlock the desktop.

Expected result:
All timers register zero activity, because a natural restbreak (sleep) has been
taken

Actual result:
All timers are way overdue

Continued testcase:
Immediately after taking a restbreak, restart the laptop.

Expected result
No effect on timers

Actual result:
Daily limit jumps from way overdue to some reasonable value. Restbreak shows a
break being overdue (even though I just took one). Didn't pay attention to
micropause.

I suffer this same issue.

When leaving, I shut down my laptop (Gentoo), leaving my desktop (WinXP) be. After coming back, the desktop workrave won't reconnect well, and the counters are way overdue.

I would expect workrave to disconnect from the network connection after a reasonable time-out, and start counting for itself.

As te laptop comes online again, I would expect reconnection to occur automatically, but this doesn't work (always).

If you need any information on this matter, let me know.

BTW, the version I am using is 1.8.4 currently, but the bug is the same.