group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <2049785@xxxxxxxxxxxxxxxxxx>]

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 <nathan.teodosio@xxxxxxxxxxxxx>  Wed, 26 Jun
2024 11:11:46 +0200

** Changed in: update-manager (Ubuntu Xenial)
       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/2049785

Title:
  /usr/bin/update-manager:json.decoder.JSONDecodeError:/bin/update-
  manager@118:start_update:start_available:refresh_cache:_get_ua_security_status:load:loads:decode:raw_decode

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

Bug description:
  * Impact

  The new Ubuntu Pro integration hits an exception when the pro client
  call isn't returning a value json output

  * Test case

  Check that reports on
  https://errors.ubuntu.com/problem/741dff427bf59c3208da3b509caf1e8d2385fdea
  stop

  Also on a system not connected to pro, install an old ubuntu-
  advantage-tools 27 (outdated version), disconnect from internet and
  start update-manager, it should list the updates and not error out

  * Regression potential

  The code is changing the callback to get the list of pro updates to
  use the ubuntu-advantage-tools python API instead of calling the
  cmdline client. If there is an issue with the new API the pro updates
  listing on non pro-attached system could be incorrect or the client
  could hit a new exception

  --------------------------------------

  In JournalErrors:

  --->
  Failed to access URL: https://contracts.canonical.com/v1/resources?architecture=amd64&kernel=5.15.0-91-generic&series=focal
  Cannot verify certificate of server
  Please check your openssl configuration.
  [info] A new version is available: 30~20.04
  Please run:
  sudo apt-get install ubuntu-advantage-tools
  <---

  Is it the ubuntu-advantage-tools version problem, is it the failure to
  access contracts.canonical.com? Should we switch to calling the API
  directly as in 24.04[1] or handle the exception?

  [1] https://code.launchpad.net/~nteodosio/update-manager/+git/update-
  manager/+merge/456088

  ------

  The Ubuntu Error Tracker has been receiving reports about a problem regarding update-manager.  This problem was most recently seen with package version 1:20.04.10.18, the problem page at https://errors.ubuntu.com/problem/741dff427bf59c3208da3b509caf1e8d2385fdea 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/2049785/+subscriptions