group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1317164@xxxxxxxxxxxxxxxxxx>]

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

---------------
update-manager (1:16.04.14) xenial; urgency=medium

  * Print transaction error and let the user try again applying updates
    (LP: #1317164)
  * Don't ask backend to do package operations aready done.
    Aptdaemon cancels the transaction when asked to remove packages already
    removed which results the failure being shown to the user. This
    is unnecessary as update-manager can just filter the package operations to
    be done using a fresh cache and decrease the likelyhood of hitting
    a race condition where packages to be removed are already removed.
    (LP: #1791931)

 -- Balint Reczey <rbalint@xxxxxxxxxx>  Wed, 19 Sep 2018 09:18:52 +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/1317164

Title:
  Show reason of TransactionFailed and let the user try again instead of
  crashing

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

Bug description:
  [Impact]

   * Update-manager crashes when it tries to remove a package that was
  already removed since update-manager refreshed its cache. A typical
  scenario is when the list of available packages is updated, then
  update-manager pops up to notify the user about the updates. The user
  is not in front of the screen and unattended-upgrades installs the
  security updates and removes unused kernels making the list of updates
  shown to the user outdated. User clicks "Install now" and update-
  manager crashes.

   * The fix shows the reason of the transaction failure then asks
  offers the user to try again.

  [Test Case ]
   (with Bionic's package names)

   * Revert the patch for LP: #1791931 since it shadows the issue by
  filtering the package operations in advance.

   * Install older kernel packages, downgrade a few packages and mark the kernels autoremovable:
     $ sudo eatmydata apt install -y --allow-downgrades linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic libpoppler73=0.62.0-2ubuntu2 poppler-utils=0.62.0-2ubuntu2 ; sudo /etc/kernel/postinst.d/apt-auto-removal ; sudo apt-mark auto linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic

   * Start update-manager in a different terminal and _don't_ start the
  upgrade

   * Remove kernel packages behind u-m's back:
     $ sudo eatmydata apt remove -y linux-headers-4.15.0-32

   * Start the update on update-manager's GUI and observe it not
  crashing with the fixed version but showing the reason of the update
  failing and offering trying it again.

  [Regression Potential]

   * Inaccurate exception handling could shadow other problems.

  [Original bug text]

  On errors.ubuntu.com there are multiple crashes reported about update-
  manager that end in a Traceback like the following:

  aptdaemon.errors.TransactionFailed: Transaction failed: The package system is broken
   The following packages have unmet dependencies:

  rhythmbox-plugin-magnatune: Depends: rhythmbox (= 3.0.2-0ubuntu2) but
  3.0.2-0ubuntu1 is installed

  Naturally, the package name varies. I don't believe these are actually
  crashes about update-manager or aptdaemon. Rather there is something
  wrong with the users package system. Subsequently, it'd be better if
  these were not reported to the error tracker and clogging up the bug
  lists.

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