Comment 6 for bug 734645

Revision history for this message
James Page (james-page) wrote :

It looks like the problem encountered during the upgrade has already resolved itself.

As this error is not repeatable and we can't identify the root cause I'm going to mark this bug as 'Invalid'

Thanks again for taking the time to report this bug.