software-center crashed with ImportError in /usr/lib/python2.7/bsddb/__init__.py: No module named _bsddb

[Vyacheslav Sharmanov]

After update from 11.10 to 12.4 Alpha 1

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: software-center 5.1.6
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sat Jan 21 12:34:28 2012
DuplicateOf: https://bugs.launchpad.net/bugs/440889
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/software-center']
SoftwareCenterLog:
 2012-01-20 19:30:13,297 - softwarecenter.ui.gtk3.em - INFO - EM's: 17 15 21
 2012-01-20 19:30:16,682 - softwarecenter.backend.reviews - WARNING - Could not get usefulness from server, no username in config file
 2012-01-20 19:30:16,820 - softwarecenter.ui.gtk3.utils - INFO - Softwarecenter style provider for ambiance Gtk theme: /usr/share/software-center/ui/gtk3/css/softwarecenter.css
 2012-01-20 19:30:25,688 - softwarecenter.ui.gtk3.app - INFO - software-center-agent finished with status 0
 2012-01-20 19:32:19,578 - softwarecenter.utils - WARNING - Could not determine the installed desktop file path for app-install desktop file: 'None'
SourcePackage: software-center
Title: software-center crashed with ImportError in /usr/lib/python2.7/bsddb/__init__.py: No module named _bsddb
UpgradeStatus: Upgraded to precise on 2012-01-21 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #440889, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.