update-manager crashed with Package isn't installed in _run_in_dialog()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Utopic |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Errors Bucket
-------------
This crash will be bucketed separately due to the package name not being available changing. However, here is one example crash indicating the volume of the problem:
https:/
This happened when I did an 'apt-get autoremove --purge' from the shell to free up space after update-manager had launched, causing a package that was in the upgrade list to be removed. Since the apt database is not continuously locked while update-manager is running, it should gracefully handle changes to the installed package list between the time it displays the list and the time it applies the list to aptd.
ProblemType: CrashDistroRelease: Ubuntu 13.10
Package: update-manager 1:0.188
ProcVersionSign
Uname: Linux 3.9.0-6-generic x86_64
ApportVersion: 2.10.2-0ubuntu2
Aptdaemon:
Architecture: amd64
Date: Wed Jun 26 09:34:30 2013
ExecutablePath: /usr/bin/
GsettingsChanges:
b'com.
b'com.
b'com.
b'com.
b'com.
InstallationDate: Installed on 2010-09-24 (1006 days ago)Installatio
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/bin/
PythonArgs: ['/usr/
Title: update-manager crashed with Package libsignon-qt1 isn't installed in _run_in_dialog()
UpgradeStatus: Upgraded to saucy on 2013-05-06 (50 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src sudo
tags: | removed: need-duplicate-check |
Changed in update-manager (Ubuntu): | |
importance: | Undecided → Medium |
summary: |
- update-manager crashed with Package libsignon-qt1 isn't installed in - _run_in_dialog() + update-manager crashed with Package isn't installed in _run_in_dialog() |
tags: | added: trusty utopic |
Changed in update-manager (Ubuntu): | |
status: | Confirmed → Triaged |
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.