[Bug 1826213] Re: /usr/bin/update-manager:AttributeError:/usr/bin/update-manager at 118:start_update:start_available:refresh_cache:update
Brian Murray
1826213 at bugs.launchpad.net
Wed Jun 3 18:47:27 UTC 2020
** Changed in: update-manager (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: update-manager (Ubuntu Eoan)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: update-manager (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: update-manager (Ubuntu Bionic)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1826213
Title:
/usr/bin/update-manager:AttributeError:/usr/bin/update-
manager at 118:start_update:start_available:refresh_cache:update
Status in update-manager package in Ubuntu:
Fix Released
Status in update-manager source package in Bionic:
In Progress
Status in update-manager source package in Eoan:
In Progress
Status in update-manager source package in Focal:
In Progress
Bug description:
[Impact]
update-manager is crashing frequently causing a bad user experience.
[Test Case]
The crash happens when an AssertionError is raised in MyCache but I haven't figure out how to recreate that. So here's a way to force an assertion error.
1) edit the MyCache class's __init__ function (found in UpdateManager/Core/MyCache.py) to 'raise AssertionError' which will simulate having a dirty journal or broken packages
2) run update-manager and observe the Traceback in comment #1
Additionally, we can use the bucket in the Error Tracker to confirm
that there are no crashes with the version of the package from
-proposed.
[Regression Potential]
Original Description
--------------------
The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager. This problem was most recently seen with package version 1:19.04.5, the problem page at https://errors.ubuntu.com/problem/1bcfccc6ceab83c6e401f14c655c1cd5045be5d4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1826213/+subscriptions
More information about the foundations-bugs
mailing list