Ubuntu
software-properties package

software-properties-gtk crashed with ValueError in remove(): list.remove(x): x not in list

Bug #976408 reported by kjeld Olsen on 2012-04-08

This bug report is a duplicate of: Bug #774728: software-properties-gtk crashed with ValueError in remove(): list.remove(x): x 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 when trying to update after reboot.

Toshiba AC100-10D PDN01E-00801EN5 Nordic.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: software-properties-gtk 0.82.7
Uname: Linux 3.0.19-2-ac100 armv7l
ApportVersion: 2.0-0ubuntu4
Architecture: armhf
Date: Sun Apr 8 09:23:40 2012
ExecutablePath: /usr/bin/software-properties-gtk
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-properties-gtk -n -t 58720385
PythonArgs: ['/usr/bin/software-properties-gtk', '-n', '-t', '58720385']
SourcePackage: software-properties
Title: software-properties-gtk crashed with ValueError in remove(): list.remove(x): x not in list
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Revision history for this message

kjeld Olsen (kjeldo) wrote on 2012-04-08:

Dependencies.txt Edit (5.5 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (137 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (52.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (735 bytes, text/plain; charset="utf-8")
Traceback.txt Edit (1.1 KiB, text/plain; charset="utf-8")

visibility:

private → public

Apport retracing service (apport) on 2012-04-08

tags:

removed: need-duplicate-check

Revision history for this message

Robert Roth (evfool) wrote on 2012-05-10:

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 #774728, 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. Feel free to continue to report any other bugs you may find.