Timeseal issue where you lose no time.

[GoogleCodeExporter]

There is still a rare timeseal issue where no time is deducted from your clock. 

Possible fixes:
Removing build in timeseal, and return to the precompiled timeseals fics 
provides.

Original issue reported on code.google.com by carsonday on 4 Feb 2013 at 5:48

[GoogleCodeExporter]

Interesting "bug" :-)

Care to provide some more details? I just sort of reverse engineered the 
timeseal code in Raptor and it is so straightforward that I cannot see how 
there could be a case like the issue mentionsm except perhaps a threading issue 
(noticed that "ACK" requests are handled by a different thread, so there might 
be a mixup between the data sent from two different threads?)

Original comment by evil...@gmail.com on 9 Aug 2014 at 4:54