I have today reinstalled Precise twice to see if I had a hard drive problem or one of the recent updates was causing problems.
I have Kubuntu and Precise installed ( on another hard drive and have applied updates and it is not crashing like the latest daily build. After intallaiton, and while applying updates compiz crashed, then software center, then update manager, went to the terminal to finish update and something else crashed I could not stop to work on that then. Now I have applied all updates and restarted and rebooted numerous times. I will after this bug report install my drive with my early install of Ubuntu 12.04 and Kubuntu 12.04 and see if they are still running normally. There are far too many crashes to keep up with. The last upgrade did include kernel 3.2.0.10 It had been , up till now a very quiet Alpha release. Not now. Best Wishes and Good luck.
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: fglrx
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Jan 20 20:09:51 2012
DuplicateOf: https://bugs.launchpad.net/bugs/440889
ExecutablePath: /usr/share/software-center/software-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120112)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/software-center']
SoftwareCenterLog:
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 cdrom dip lpadmin plugdev sambashare sudo
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.