update-manager crashed with SystemError in mark_install(): E:Unable to correct problems, you have held broken packages.

Bug #862591 reported by allsys
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

just deselct and select again checkbox in updatemanager
updatemanager works further without any problems

checkbox with gnome-control-center update

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: update-manager 1:0.152.19
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Thu Sep 29 21:20:41 2011
ExecutablePath: /usr/bin/update-manager
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/update-manager
ProcEnviron:
 SHELL=/bin/bash
 LANG=ru_RU.UTF-8
PythonArgs: ['/usr/bin/update-manager']
SourcePackage: update-manager
Title: update-manager crashed with SystemError in mark_install(): E:Unable to correct problems, you have held broken packages.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout dip lpadmin plugdev sambashare

Revision history for this message
allsys (g-admin-losei-net) wrote :
Revision history for this message
Apport retracing service (apport) wrote : 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 #768007, 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.

tags: removed: need-duplicate-check
visibility: private → public
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.