In hopes of recovering from loosing sync due to bug#594, I chose "network->reconnect" on the local PC. This caused the local workrave to crash (crashlog attached), and the remote workrave to "freeze": None of the clocks are moving and my restbreak takes literally forever

Expected result:
No crash, no freeze ;-)

Created attachment 72
Crashlog

Created attachment 73
Now the remote end crashed as well

Up until now, I continued to use the remote end (just clicked "skip" in the restbreak window and reconnected to the laptop).

Just now, it crashed on me.

Sigh...
After restarting and reconnecting the remote workrave, my usage statistics are nearly gone.
I now have one and a half minute of usage (on the daily timer), but a total of 30 overdue minutes on the restbreak.

Sigh again....

"Workrave has unexpectedly crashed and failed to create a crash log"

Do I need to remove the old log before it creates a new one?

Local Workrave
00434068  0022F940  00440DDF PacketBuffer::peek_ushort(int)
00440DDF  0022F964  004434C1 DistributionSocketLink::socket_io
004434C1  0022F984  00443644 GNetSocketDriver::async_io

Remove Workrave:
007268CB  0022F7AC  00443844 Some DLL 
00443844  0022F7CC  0043E954 GNetSocketConnection::write
0043E954  0022F7F8  0043EA0E DistributionSocketLink::send_packet_except
0043EA0E  0022F80C  0043F3A1 DistributionSocketLink::send_packet_broadcast
0043F3A1  0022F858  0043F523 DistributionSocketLink::send_client_message
0043F523  0022F878  0042C459 DistributionSocketLink::heartbeat()
0042C459  0022F8B0  0042E531 Core::process_distribution()
0042E531  0022F8CC  00404B8A Core::heartbeat()

Fixed. 

About the "Workrave has unexpectedly crashed and failed to create a crash log": Workrave normally overwrites the previous crashlog. This error is generated when a crash occurs in the crash handler...