Comment 3 for bug 74269

Revision history for this message
Colin Watson (cjwatson) wrote :

The problem is that your system clock is set to a bogus value (probably something in 1904) during boot. This is also bug 57952.