** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => 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/bug
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => 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/bug
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => 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/bug
This bug was fixed in the package linux-aws - 4.18.0-1002.3
---
linux-aws (4.18.0-1002.3) cosmic; urgency=medium
* linux-aws: 4.18.0-1002.3 -proposed tracker (LP: #1796944)
* iptables --list --numeric fails on -virtual kernel / -virtual missing
bpfilter (LP: #1795036)
- [
Yes this change (the Debian version of it, not yours) is in since 3.3.1-3
Thanks a lot Mark! for the ping on this forgotten bug also for the
documentation of the config in regard to BackupZeroFilesIsFatal if previously
set to 1.
(And also thanks for your upstreaming work on this)
** Also affec
I've moved mitaka back to Triaged since this is only fixed so far in the
systemd init file.
** Changed in: cloud-archive/mitaka
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
M
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in: ubuntu-power-systems
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: U
** Description changed:
[Impact]
* network menu in recovery mode doesn't work correctly, blocking at
starting systemd services depends to enable networking.
[Test Case]
* Boot w/ Xenial or Bionic in recovery mode via grub
* Choose "network" in friendly-recovery menu
T
This bug was fixed in the package systemd - 239-7ubuntu10
---
systemd (239-7ubuntu10) cosmic; urgency=medium
* units: Disable journald Watchdog (LP: #1773148)
* Add conflicts with upstart and systemd-shim. (LP: #1773859)
-- Dimitri John Ledkov Thu, 04 Oct 2018 15:58:51
+0100
Just to connect the dots, this particular fix is:
https://github.com/hughsie/fwupd/commit/86fdd975adbb725965d8a015994f023469e697d8
#diff-22684cccbec07d4328eaef43086e6f47
It's in the 1.0.9 release that will be SRUed by
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1791999
** Changed in: fwu
This particular issue hasn't received reports in anything newer than
Ubuntu 16.04. The fwupd version in 16.04 is in deep maintenance mode
and issues on the branches contained there (0.7.x and 0.8.x) will not be
fixed.
** Changed in: appstream-glib (Ubuntu)
Status: Triaged => Invalid
** Ch
11 matches
Mail list logo