Ubuntu
software-properties package

Update Manager crashed after adding and editing another source

Bug #848143 reported by Mac on 2011-09-12

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

Crashed whilst attempting to apply a change to the Distribution field; following authentication.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: software-properties-gtk 0.81.9
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
Date: Mon Sep 12 19:16:48 2011
ExecutablePath: /usr/bin/software-properties-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-properties-gtk --open-tab 2
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2']
SourcePackage: software-properties
Title: software-properties-gtk crashed with ValueError in run(): <aptsources.sourceslist.SourceEntry object at 0x190c490> is not in list
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

Mac (andrew-xiion) wrote on 2011-09-12:

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

Revision history for this message

Apport retracing service (apport) wrote on 2011-09-12: 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.