Ubuntu
software-properties package

software-properties-gtk crashed with ValueError in run(): <aptsources.sourceslist.SourceEntry object at 0x9b4c7cc> is not in list

Bug #823373 reported by Sergey Kochkin on 2011-08-09

This bug report is a duplicate of: Bug #829286: software-properties-gtk crashed with ValueError in run(): <aptsources.sourceslist.SourceEntry object at 0x15f84d0> is not in list. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	software-properties (Ubuntu)	New	Undecided	Unassigned

Bug Description

fyi

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: software-properties-gtk 0.81.4
ProcVersionSignature: Ubuntu 3.0.0-8.10-generic-pae 3.0.1
Uname: Linux 3.0.0-8-generic-pae i686
Architecture: i386
Date: Tue Aug 9 22:54:02 2011
ExecutablePath: /usr/bin/software-properties-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-properties-gtk
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/software-properties-gtk']
SourcePackage: software-properties
Title: software-properties-gtk crashed with ValueError in run(): <aptsources.sourceslist.SourceEntry object at 0x9b4c7cc> is not in list
UpgradeStatus: Upgraded to oneiric on 2011-08-05 (3 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Sergey Kochkin (kochkin-sergey) wrote on 2011-08-09:

Traceback.txt Edit (438 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2011-08-24: This bug is a duplicate

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 #829286, 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.