Comment 3 for bug 1061714

I saw this bug again today.
For some reasons, it seems to not always happen.
Currently, I can reproduce the bug even after closing/reopenning software-center or when lauching it from the command-line (no specific error in it btw).

A recent upgrade of some dependencies perhaps?