This bug was fixed in the package update-manager - 1:22.04.22
---------------
update-manager (1:22.04.22) jammy; urgency=medium
* Print warning message on failing to run updates end-point (LP: #2064211).
* When all packages are unselected, install button goes away; Fix it not
coming back after once a package is selected again (LP: #2068805).
* Switch to Debian source 3.0 (native)
-- Nathan Pratta Teodosio <nathan.teodo...@canonical.com> Thu, 11 Jul
2024 11:48:43 +0200
** Changed in: update-manager (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/2064211
Title:
/usr/bin/update-
manager:AttributeError:<lambda>:available:start_available:refresh_cache:_get_ua_security_status
Status in update-manager package in Ubuntu:
Fix Released
Status in update-manager source package in Xenial:
Fix Released
Status in update-manager source package in Bionic:
Fix Released
Status in update-manager source package in Focal:
Fix Released
Status in update-manager source package in Jammy:
Fix Released
Status in update-manager source package in Noble:
Fix Released
Bug description:
Impact
------
This bug was is a regression of the bug fix LP:2058133; It held back
the phasing of the package.
The symptom is that update-manager crashes right at start, doesn't
launch.
The ua.updates() and current_news() end-points are documented to throw
no exceptions, but actually they might, in which case this bug is
encountered. As such, the proposed fix tries the API but ignores
exceptions raised by it, causing update-manager to still work, even if
the Pro packages end up being classified as normal packages or if Pro
news aren't displayed.
Test plan
---------
Run 'UA_CONFIG_FILE=/ update-manager --no-update', update-manager
should launch, not crash.
Where problems could occur
--------------------------
If the API end-points are working, ensure that classifying Pro
packages as such and displaying possible Pro news continues to work.
Original report
---------------
Looks like ua.updates() can actually throw an exception. Only that
would explain this crash.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/UpdateManager/Dialogs.py", line 118,
in <lambda>
button.connect("clicked", lambda x: callback())
File "/usr/lib/python3/dist-packages/UpdateManager/Dialogs.py", line 371,
in available
self.window_main.start_available(error_occurred=True)
File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line
242, in start_available
self.refresh_cache()
File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line
461, in refresh_cache
self._get_ua_security_status()
File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line
285, in _get_ua_security_status
for package in self.ua_updates:
AttributeError: 'UpdateManager' object has no attribute 'ua_updates'
The Ubuntu Error Tracker has been receiving reports about a problem regarding
update-manager. This problem was most recently seen with package version
1:22.04.20, the problem page at
https://errors.ubuntu.com/problem/ed0e9f0ed8bc4002d808a11e37e4ee9d870e32c1
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/2064211/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
