Comment 7 for bug 440889

Hi Dave - you're right in noting that the original bug report was describing a different issue. For some reason apport marked all the 919xxx bugs as duplicates of this one. In order not to confuse all the new subscribers by unmarking their new bugs as duplicates and then marking them as duplicates of something else, I decided to modify this report to reflect all its duplicates. Although not an ideal situation, I figured that this would cause the least disruption - the original bug no longer occurs in software-center. Hope this clarifies things a bit!

As for the current issue, an initial look would seem to imply that it was caused by a recent python update?