Comment 21 for bug 1462688

I have all the information I need now, looks like this is probably caused by "None" entries for the timezone.