/usr/bin/update-manager:NotImplementedError:<lambda>:on_button_install_clicked:start_install:_start_pane:start:commit_oem

[errors.ubuntu.com bug bridge]

[Impact]

The latest focal SRU introduced a regression when trying to use a different backend than aptdaemon (i.e. synaptic).

[Test Case]

Run update-manager with UPDATE_MANAGER_FORCE_BACKEND_SYNAPTIC=1 and make sure no crash (with the traceback below) is encountered when trying to apply the updates.

[Where problems can occur]

TODO

[Original Description]

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

Stack trace:

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/UpdatesAvailable.py", line 880, in on_button_install_clicked
    self.window_main.start_install()
  File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line 234, in start_install
    self._start_pane(install_backend)
  File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line 177, in _start_pane
    pane.start()
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/__init__.py", line 59, in start
    self.commit_oem(pkgs_install_oem, pkgs_upgrade_oem)
  File "/usr/lib/python3/dist-packages/UpdateManager/backend/__init__.py", line 95, in commit_oem
    raise NotImplementedError
NotImplementedError

[Łukasz Zemczak (sil2100)]

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

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

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

ubuntu-release-upgrader/1:20.04.30 (armhf)

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/focal/update_excuses.html#update-manager

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

Thank you!

[Julian Andres Klode (juliank)]

Running with 20.04.10.3, it crashed as soon as I clicked install. 20.04.10.4 does not crash anymore.

I don't see it making any progress, but then I have no idea whether the synaptic backend worked in the first place, so, meh?

[Łukasz Zemczak (sil2100)]

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

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

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

ubuntu-release-upgrader/1:20.04.30 (armhf)

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/focal/update_excuses.html#update-manager

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

Thank you!

[Julian Andres Klode (juliank)]

Reverified for 20.04.10.5; it does not crash anymore, and packages install.

We still do not install the OEM pacakges we offer with the synaptic backend, we should evaluate post-.2 what to do about that. Like hide them, implement the functionality for that backend, or enforce the aptd backend.

[Łukasz Zemczak (sil2100)]

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:20.04.10.5

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

  * UpdateManager/backend/__init__.py: Really make commit_oem a no-op in the
    base class to avoid crash when people force synaptic backend (LP: #1913732)
  * Fix typo in previous changelog

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

  * Revert previous change to UpdateList.py, as it breaks kernel
    autoremoval (LP: #1912718)
  * UpdateManager/backend/__init__.py: Make commit_oem a no-op in the base
    class to avoid crash when people force synaptic backend (LP: #1913732)

 -- Julian Andres Klode <email address hidden> Fri, 29 Jan 2021 17:43:01 +0100