update-motd-fsck-at-reboot error if no ext parts
Bug #1987703 reported by
Dan Bungert
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-notifier (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
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.
Related branches
~dbungert/update-notifier:lp-1987703-update-motd
- Dan Watkins (community): Approve
- Brian Murray: Pending requested
- Ubuntu Core Development Team: Pending requested
-
Diff: 28 lines (+8/-1)2 files modifieddata/update-motd-fsck-at-reboot (+1/-1)
debian/changelog (+7/-0)
~oddbloke/update-notifier:oddbloke/nbd-focal
- Dan Bungert: Approve
-
Diff: 13 lines (+1/-1)1 file modifieddata/update-motd-fsck-at-reboot (+1/-1)
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in update-notifier (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package update-notifier - 3.192.56
---------------
update-notifier (3.192.56) kinetic; urgency=medium
* data/update-
on a system with no ext[234] partitions (LP: #1987703)
-- Dan Bungert <email address hidden> Thu, 25 Aug 2022 15:02:28 -0600