software-center crashed with AttributeError in __contains__(): 'NoneType' object has no attribute '__contains__'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Software Center |
Invalid
|
Undecided
|
|||
software-center (Ubuntu) |
Fix Released
|
Low
|
Gary Lasker | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Low
|
Gary Lasker |
Bug Description
Apport says:
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: software-center 5.1.14.1
ProcVersionSign
Uname: Linux 3.2.0-21-generic i686
NonfreeKernelMo
ApportVersion: 2.0-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Wed Apr 4 12:13:30 2012
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
PythonArgs: ['/usr/
SourcePackage: software-center
Title: software-center crashed with AttributeError in __contains__(): 'NoneType' object has no attribute '__contains__'
UpgradeStatus: Upgraded to precise on 2012-02-27 (36 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
Related branches
- Michael Vogt: Approve
-
Diff: 11 lines (+1/-0)1 file modifiedsoftwarecenter/ui/gtk3/app.py (+1/-0)
tags: | removed: need-duplicate-check |
Changed in software-center (Ubuntu): | |
status: | Confirmed → Triaged |
assignee: | nobody → Gary Lasker (gary-lasker) |
status: | Triaged → In Progress |
Changed in software-center (Ubuntu): | |
status: | In Progress → Fix Committed |
Changed in software-center (Ubuntu Precise): | |
status: | New → Fix Committed |
Changed in software-center (Ubuntu Precise): | |
status: | Fix Committed → Fix Released |
Mey mpt! Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 920196, so it 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.
Thanks again!