software-center-gtk3 crashed with AttributeError in copy(): 'NoneType' object has no attribute 'copy'

[Mihai Chivu]

when opening and switching to History

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: software-center 4.1.20
ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Fri Aug 26 09:24:00 2011
ExecutablePath: /usr/share/software-center/software-center-gtk3
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center-gtk3
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/software-center-gtk3']
SoftwareCenterLog:
 2011-08-26 09:22:41,454 - softwarecenter.ui.gtk3.em - INFO - EM's: 14 11 16
 2011-08-26 09:22:42,718 - softwarecenter.fixme - WARNING - logs to the root logger: '('/usr/share/software-center/softwarecenter/db/database.py', 175, 'open')'
 2011-08-26 09:22:42,718 - root - WARNING - failed to add sca db Couldn't stat '/home/mihai/.cache/software-center/software-center-agent.db' (No such file or directory)
 2011-08-26 09:22:45,074 - softwarecenter.backend.reviews - WARNING - Could not get usefulness from server, no username in config file
 2011-08-26 09:22:55,598 - softwarecenter.ui.gtk3.app - INFO - software-center-agent finished with status 1
SourcePackage: software-center
Title: software-center-gtk3 crashed with AttributeError in copy(): 'NoneType' object has no attribute 'copy'
UpgradeStatus: Upgraded to oneiric on 2011-08-10 (15 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #834196, 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.