Comment 3 for bug 343469

Revision history for this message
Graham Binns (gmb) wrote :

I think the problem was caused by the watch not being updated for some time; it now appears to have been updated correctly, so I'm going to mark this bug Invalid.