Comment 13 for bug 326768

This should definitely be added to the release notes or fixed, but it appears that the problem can be resolved by performing the workaround in the original description.

Also, just doing something to interact with the database (like schedule a dummy recording), always worked to fix the problem for me before I applied the workaround.