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

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

Bug Description

Installed a fresh copy on system with 3 partitions for /, /home, /var
No customization. Nothing. First boot. Opened update manager started unchecking the packages that were more than 500kb. After selecting/de-selecting a few items I get a crash dialog.

Updated update manager from command line. same thing again.

Suggestion: update manager needs more options. Like select-all, un-select-all, sort-by-name, sort-by-size etc etc.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: update-manager 1:0.150.3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Wed Aug 3 00:21:46 2011
ExecutablePath: /usr/bin/update-manager
GConfNonDefault:
 /apps/update-manager/check_new_release_ignore=
 /apps/update-manager/first_run=false
 /apps/update-manager/window_size=(1366,744)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110411.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python2.7 /usr/bin/update-manager
ProcEnviron:
 LANGUAGE=en_IN:en
 LANG=en_IN
 LC_MESSAGES=en_IN.UTF-8
 SHELL=/bin/bash
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 lpadmin plugdev sambashare

Revision history for this message
Raman Devgan (techxcell) 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
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.