[Bug 1795898] Re: TypeError: _action_done() got an unexpected keyword argument 'trans_failed'

Steve Langasek steve.langasek at canonical.com
Sat Oct 13 03:58:55 UTC 2018


Hello Balint, 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.11.6 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 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.

** Changed in: update-manager (Ubuntu Bionic)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  TypeError: _action_done() got an unexpected keyword argument
  'trans_failed'

Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  Lazy imports made update-manager crash when an update-manager
  update changed the backend API and an updated incompatible backend
  was loaded to the not updated running update-manager process.

  The issue causes crashes upon update-manager updates harming the
  upgrade experience for users.

  The fix avoids lazy loading of the backend modules but still honors
  the backend selection options.

  [Test Case]

  1. Start with a fully upgraded system and downgrade a few packages to let u-m upgrade them:
  $ sudo eatmydata apt install -y --allow-downgrades  gnome-software=3.28.1-0ubuntu4 gnome-software-common=3.28.1-0ubuntu4

  2. Start u-m with:
   $ update-manager --no-update

  3. Make a syntax error in /usr/lib/python3/dist-
  packages/UpdateManager/backend/InstallBackendAptdaemon.py

  4. Press "Install Now" on u-m GUI.
   The fixed u-m will successfully perform the installation, the unfixed one will fail with SyntaxError.

  [Regression Potential]

  Wrong changes to the backend import/selection logic could make u-m
  unable to find the available backends, but in my testing the fixed
  version could properly find both aptdaemon and synaptic when they were
  present.

  [Original Bug Text]
   
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py", line 242, in _on_finished
      trans_failed=trans_failed)
  TypeError: _action_done() got an unexpected keyword argument 'trans_failed'

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



More information about the foundations-bugs mailing list