[Bug 1880987] Re: [SRU] /usr/bin/update-manager:TypeError:_on_finished:_action_done:get_deb2snap_dups:_on_finished:_action_done:get_deb2snap_dups

Launchpad Bug Tracker 1880987 at bugs.launchpad.net
Thu Jun 18 09:18:49 UTC 2020


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

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

  * UpdateManager/UpdateManager.py: when refreshing the cache and encountering
    an error return rather than trying to use the undefined cache which causes
    crashes. Additionally, don't present the dialog with a "Try Again" button
    which won't do anything. (LP: #1826213)
  * Fix hang in apturl-gtk. (LP: #1874591)
  * Fix crash in snap updates when refreshing the cache fails. (LP: #1880987)

 -- Brian Murray <brian at ubuntu.com>  Wed, 03 Jun 2020 10:18:00 -0700

** Changed in: update-manager (Ubuntu Focal)
       Status: Fix Committed => Fix Released

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

Title:
  [SRU] /usr/bin/update-
  manager:TypeError:_on_finished:_action_done:get_deb2snap_dups:_on_finished:_action_done:get_deb2snap_dups

Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Focal:
  Fix Released

Bug description:
  [Impact]

  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, the problem page at https://errors.ubuntu.com/problem/b2c8bc0cb8285d022b6b6aa8a75000e6d82dab19 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/.

  [Test Case]

  This is reproducable by raising an AssertionError during the
  initialization of MyCache in "UpdateManager/backend/__init__.py"
  whereby the cache is then assigned to None:

          except Exception as e:
              logging.debug("error reading cache (%s)" % e)
              cache = None

  [Regression Potential]

  Instead of assigning the cache to None and attempting to continue the
  duplicates check, we now just return an empty array. It's perfectly
  safe to postpone this duplicates check to a later update, so there's
  little regression potential as far as I can see.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1880987/+subscriptions



More information about the foundations-bugs mailing list