update-manager crashed with SIGABRT in raise()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-manager (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I am using the beta version that works very well but there are updates that the system cannot perform and comes with these erros.
Not all updates can be installed, asks to run a partial update and them is says: Unable to get exclusive lock,
This usually means that another package management application (like apt-get or aptitude) already running. Please close that application first.
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade:
The package 'unity' is marked for removal but it is in the removal blacklist.
This can be caused by:
* Upgrading to a pre-release version of Ubuntu
* Running the current pre-release version of Ubuntu
* Unofficial software packages not provided by Ubuntu
This is most likely a transient problem, please try again later.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: update-manager 1:0.156.9
ProcVersionSign
Uname: Linux 3.2.0-20-
ApportVersion: 1.95-0ubuntu1
Architecture: i386
Date: Fri Mar 23 10:50:44 2012
ExecutablePath: /usr/bin/
GsettingsChanges:
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/
Signal: 6
SourcePackage: update-manager
Title: update-manager crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
| Paulo A Paglione (paulo-paglione-gmail) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #930839, 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.