/usr/bin/update-manager:AttributeError:<lambda>:available:start_available:refresh_cache:_get_ua_security_status

[errors.ubuntu.com bug bridge]

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/.

[Launchpad Janitor (janitor)]

This bug was fixed in the package update-manager - 1:24.10.1

---------------
update-manager (1:24.10.1) oracular; urgency=medium

  [ Nathan Pratta Teodosio ]
  * Don't crash if the updates() end-point of the Pro API fails (LP: #2064211).

  [ Himadri Sekhar Basu ]
  * Fix scroll window on update downloading page
    - Currently the download progress box does not
      expand vertically when in fullscreen, however
      the expansion in vertical direction with
      increasing window height is the proper
      behaviour. This fix provides this desired
      behaviour.
    - Fixes LP: #1772486, LP: #1856404

 -- Graham Inggs <email address hidden> Wed, 22 May 2024 15:21:09 +0000

[Nathan Teodosio (nteodosio)]

Fix was insufficient as per test case, current_news() also hits the same problem. Reverting to triaged and proposing a new merge request for that remaining part.

[Launchpad Janitor (janitor)]

This bug was fixed in the package update-manager - 1:24.10.2

---------------
update-manager (1:24.10.2) oracular; urgency=medium

  * Don't crash if the current_news() end-point of the Pro API fails
    (LP: #2064211).

 -- Nathan Pratta Teodosio <email address hidden> Fri, 24 May 2024 16:08:50 +0200

[Benjamin Drung (bdrung)]

The packages were sponsored and waiting in the queue:

* 1:24.04.8 in https://launchpad.net/ubuntu/noble/+queue?queue_state=1
* 1:22.04.21 in https://launchpad.net/ubuntu/jammy/+queue?queue_state=1
* 1:20.04.10.22 in https://launchpad.net/ubuntu/focal/+queue?queue_state=1
* 1:18.04.13 in https://launchpad.net/ubuntu/bionic/+queue?queue_state=1
* 1:18.04.13 in https://launchpad.net/ubuntu/bionic/+queue?queue_state=1

So unsubscribing ~ubuntu-sponsors.

[Timo Aaltonen (tjaalton)]

Hello errors.ubuntu.com, or anyone else affected,

Accepted update-manager into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-manager/1:22.04.21 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Timo Aaltonen (tjaalton)]

Hello errors.ubuntu.com, or anyone else affected,

Accepted update-manager into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-manager/1:20.04.10.22 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Timo Aaltonen (tjaalton)]

An upload of update-manager to noble-proposed has been rejected from the upload queue for the following reason: "fix the version".

[Timo Aaltonen (tjaalton)]

Hello errors.ubuntu.com, or anyone else affected,

Accepted update-manager into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-manager/1:18.04.13 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Timo Aaltonen (tjaalton)]

Hello errors.ubuntu.com, or anyone else affected,

Accepted update-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-manager/1:16.04.23 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Nathan Teodosio (nteodosio)]

In Xenial virtual machine, installed 1:16.04.23 and ran

  UA_CONFIG_FILE=/ update-manager --no-update', update-manager

The program started normally and did not crash.

[Nathan Teodosio (nteodosio)]

In Focal virtual machine, installed 20.04.22 and ran

  UA_CONFIG_FILE=/ update-manager --no-update

The program started normally and did not crash.

[Nathan Teodosio (nteodosio)]

In Bionic virtual machine, installed 18.04.13 and ran

  UA_CONFIG_FILE=/ update-manager --no-update

The program started normally and did not crash.

[Nathan Teodosio (nteodosio)]

In Jammy virtual machine, installed 22.04.21 and ran

  UA_CONFIG_FILE=/ update-manager --no-update

The program started normally and did not crash.

[Robie Basak (racb)]

See discussion at https://irclogs.ubuntu.com/2024/07/10/%23ubuntu-release.html#t13:23

IIUC, this means that the Noble unapproved upload needs replacing, and so do the other SRUs that are in proposed now.

[Nathan Teodosio (nteodosio)]

Note for SRU reviewers: We're catching the catch-all Exception rather than UbuntuProError as discussed in https://code.launchpad.net/~nteodosio/update-manager/+git/update-manager/+merge/469201.

[Robie Basak (racb)]

I was asked to review the current upload in jammy-proposed for release, in order to make 22.04.5. I agree with Seb and Nathan that the benefit of getting what is currently in jammy-proposed into the point release outweighs the code quality concern I had identified previously. +1 to release to jammy-proposed.

I believe Utkarsh has already acked this on behalf of the release team.

[Robie Basak (racb)]

This leads to a minor inconsistency but I think that's acceptable. I understand that the desktop team already has code committed (somewhere) to get this resolved in the future.

[Robie Basak (racb)]

The verification of the Stable Release Update for update-manager has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package update-manager - 1:22.04.21

---------------
update-manager (1:22.04.21) jammy; urgency=medium

  * Don't crash if the end-points of the Pro API fail (LP: #2064211).

 -- Nathan Pratta Teodosio <email address hidden> Wed, 26 Jun 2024 11:01:35 +0200

[Timo Aaltonen (tjaalton)]

Hello errors.ubuntu.com, or anyone else affected,

Accepted update-manager into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-manager/1:24.04.8 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Timo Aaltonen (tjaalton)]

Hello errors.ubuntu.com, or anyone else affected,

Accepted update-manager into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-manager/1:20.04.10.23 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Timo Aaltonen (tjaalton)]

Hello errors.ubuntu.com, or anyone else affected,

Accepted update-manager into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-manager/1:18.04.13.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Nathan Teodosio (nteodosio)]

In a 20.04 virtual machine, I installed update-manager/1:20.04.10.23 and ran 'UA_CONFIG_FILE=/ update-manager --no-update'. Update-manager started normally.

[Nathan Teodosio (nteodosio)]

In a 24.04 virtual machine, I installed update-manager/1:24.04.8 and ran 'UA_CONFIG_FILE=/ update-manager --no-update'. Update-manager started normally.

[Nathan Teodosio (nteodosio)]

In a 18.04 virtual machine, I installed update-manager/1:18.04.13.1 and ran

  UA_CONFIG_FILE=/ update-manager --no-update

It started normally.

[Launchpad Janitor (janitor)]

This bug was fixed in the package update-manager - 1:24.04.8

---------------
update-manager (1:24.04.8) noble; urgency=medium

  * Display changelogs also for PPA packages on ppa.launchpadcontent.net
    (lp: #2068809)

  [ Nathan Pratta Teodosio ]
  * Don't crash if the end-points of the Pro API fail (LP: #2064211).

 -- Sebastien Bacher <email address hidden> Mon, 08 Jul 2024 14:00:19 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package update-manager - 1:20.04.10.23

---------------
update-manager (1:20.04.10.23) focal; urgency=medium

  * Print warning message on failing to run updates end-point (LP: #2064211).

update-manager (1:20.04.10.22) focal; urgency=medium

  * Don't crash if the end-points of the Pro API fail (LP: #2064211).

 -- Nathan Pratta Teodosio <email address hidden> Wed, 11 Sep 2024 13:41:08 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package update-manager - 1:18.04.13.1

---------------
update-manager (1:18.04.13.1) bionic; urgency=medium

  * Print warning message on failing to run updates end-point (LP: #2064211).

update-manager (1:18.04.13) bionic; urgency=medium

  * Don't crash if the end-points of the Pro API fail (LP: #2064211).

 -- Nathan Pratta Teodosio <email address hidden> Wed, 11 Sep 2024 13:36:31 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package update-manager - 1:16.04.23

---------------
update-manager (1:16.04.23) xenial; urgency=medium

  * Don't crash if the end-points of the Pro API fail (LP: #2064211).

update-manager (1:16.04.22) xenial; urgency=medium

  * Replace Popen to 'ua security-status --format=json' by the Ubuntu Pro API.
    The former is not stable enough and would break the program once in a
    while when something unrelated to Update Manager (Livepatch, for instance)
    went awry. The updates() end point from the API, on the other hand,
    does not raise exceptions. LP: #2058133.

update-manager (1:16.04.21) xenial; urgency=medium

  * Fix autopkgtest (linter errors).

update-manager (1:16.04.20) xenial; urgency=medium

  * d/control: Depend on ubuntu-advantage-tools >= 30~.
    Fixes edge case whereby the program crashes upon an incomplete
    response from ua security-status (LP: #2049785).
  * The New Release dialog should take precedence over a list of updates dialog
    if the latter would only show Ubuntu Pro updates in an unattached system.
    (LP: #2051115).

update-manager (1:16.04.19) xenial; urgency=medium

  * Add back removed widgets to UI file to fix crash when updating
    Upgrade Manager from inside itself (LP: #2045918).

update-manager (1:16.04.18) xenial; urgency=medium

  * Implement the new Ubuntu Pro design (lp: #1990450).
    - Fuse the description and changes tabs into a single view.
    - Add button to attach to enable Ubuntu Pro if it is the only action
      available.
    - Ubuntu base -> System components.
    - Fix Ubuntu Pro item not being a parent group of its corresponding
      packages.
    - Fix incorrect available version for Ubuntu Pro updates in unattached case
      (LP: #2043425).

 -- Nathan Pratta Teodosio <email address hidden> Wed, 26 Jun 2024 11:11:46 +0200

[Timo Aaltonen (tjaalton)]

An upload of update-manager to jammy-proposed has been rejected from the upload queue for the following reason: "git cruft in the upload".

[Andreas Hasenack (ahasenack)]

Hello errors.ubuntu.com, or anyone else affected,

Accepted update-manager into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update-manager/1:22.04.22 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted update-manager (1:22.04.22) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-release-upgrader/1:22.04.20 (amd64, s390x)
ubuntu-release-upgrader/unknown (arm64)
update-notifier/unknown (arm64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#update-manager

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Nathan Teodosio (nteodosio)]

Autopkgtests fixed.

[Andreas Hasenack (ahasenack)]

This is missing a jammy verification.

[Nathan Teodosio (nteodosio)]

In 22.04 installed update-manager .22, ran

  UA_CONFIG_FILE=/ update-manager --no-update

It started normally.

[Launchpad Janitor (janitor)]

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 <email address hidden> Thu, 11 Jul 2024 11:48:43 +0200