** Description changed: [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 in the initialization of MyCache and looks like a problem with "UpdateManager/backend/__init__.py" carrying on when cache is set to None. Here are the lines of code I'm looking at: - except Exception as e: - logging.debug("error reading cache (%s)" % e) - cache = 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 in my opinion. + regression potential as far as I can see.
** Description changed: [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 in the initialization - of MyCache and looks like a problem with - "UpdateManager/backend/__init__.py" carrying on when cache is set to - None. Here are the lines of code I'm looking at: + 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. ** Also affects: update-manager (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: update-manager (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: update-manager (Ubuntu Bionic) Status: New => Confirmed ** Changed in: update-manager (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1880987/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
