[Bug 1987703] Re: update-motd-fsck-at-reboot error if no ext parts

Launchpad Bug Tracker 1987703 at bugs.launchpad.net
Tue Aug 30 23:42:52 UTC 2022


This bug was fixed in the package update-notifier - 3.192.56

---------------
update-notifier (3.192.56) kinetic; urgency=medium

  * data/update-motd-fsck-at-reboot: fix exit status 1 if update-motd is run
    on a system with no ext[234] partitions (LP: #1987703)

 -- Dan Bungert <daniel.bungert at canonical.com>  Thu, 25 Aug 2022
15:02:28 -0600

** Changed in: update-notifier (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-notifier in Ubuntu.
https://bugs.launchpad.net/bugs/1987703

Title:
  update-motd-fsck-at-reboot error if no ext parts

Status in update-notifier package in Ubuntu:
  Fix Released

Bug description:
  update-motd will fail if run on a system with no ext partitions.

  The recent change to get the list of ext partitions will trigger the
  'set -e' failure exit if there aren't actually ext partitions.

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




More information about the foundations-bugs mailing list