Comment 1 for bug 249984

Yup. I was using datetime.utcnow() instead of datetime.now(). I have fixed this in both the main and webkitui branches. I don't remember now why I used utcnow in the errors... I hope there wasn't a good reason. ;-)