Comment 3 for bug 560301

From the trace this looks like a time out between the Python bindings and the MythTV data base.

Has this happen just once or is this a frequent occurrence? Are other data base related activities working? Such as viewing your the Watch Recordings screen which is the data base request that was being executed (getRecordings() function).

As this code is used with every jamu run of the "-MW" options and it is not been reported before, I suspect that this is one of the following:
A one-off error, installation error, database server issue or network issue.