gt; Low
** Changed in: prometheus-node-exporter (Ubuntu Focal)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970422
Title:
awk
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1970422/+attachment/5583973/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970422
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1970422/+attachment/5583972/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "HookError_ubuntu.txt"
https://bugs.launchpad.net/bugs/1970422/+attachment/5583971/+files/HookError_ubuntu.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1970422/+attachment/5583970/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Every time the prometheus-node-exporter-apt.service service runs; it
comes out with awk warnings; the regex used is understood but misparsed:
Apr 25 12:06:25 s8mtl1-srs1-prd systemd[1]: Starting Collect apt metrics for
prometheus-node-exporter...
Apr 25 12:06:25
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845529
Title:
bash completion shows `awk: line 18: function gensub never defined` on
`umount /dev/`
To manage
** Description changed:
+ [Impact]
+ Any user attempting to tab-complete from "umount /dev/" when running the bash
shell.
+
+ [Test cases]
Steps to reproduce:
1. Install Ubuntu MATE 19.10 using minimal desktop option
2. Open terminal and enter `umount /dev/s` and then hit
Expected
** Also affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845529
Title:
bash completion shows `awk: line 18: function gensub
I have an issue with leaving cruft around instead of actively fixing
whatever depends on old behavior; months from now, or even years, we'll
still have this switch around that does nothing -- that's more confusing
for users than actively moving forward.
That said, I'll defer to Colin and add the
** Changed in: software-properties (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852772
Title:
test_updates_interval fails on focal
To manage
issues in the code, code that is not necessarily
very portable or that might be hard to maintain in the future. I'll let
the Security Team give their opinion on it and decide.
** Changed in: tcmu (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-secur
ntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
** Changed in: tcmu (Ubuntu)
Status: New => In Progress
** Changed in: tcmu (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notifica
That's not /really/ helpful anyway. You'd have installed an extra
application, for a wholly unrelated issue, and still have to set the
profile to A2DP yourself.
Alistair, there are messages in your logs that seem to point to a firmware
issue:
Nov 26 16:56:25 albatross bluetoothd[1010]: Unable to
I see no objection at all; that fix looks obviously correct and does fix
the test.
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Corey Bryant (corey.bryant)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: urwid (Ubuntu)
Status: New => In Progress
** Changed in: urwid (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851064
Title:
[SRU] Update WALinuxAgent to 2.2.44
To manage notifications about this bug go to:
There are multiple reports of chainload working again with the fix
uploaded to eoan-proposed; marking as verification-done for Eoan with
2.04-1ubuntu12.1
** Tags removed: id-5d978799ba24715c5ddcabc5 verification-needed
verification-needed-eoan
** Tags added: id-5d978799ba24715c5ddcabc
** Description changed:
[Background]
Many packages are affected by the requirement to support the new era "Reiwa"
(令和）
This is the meta bug to track packages that need fixes; which packages
have already been SRUd to previous releases, how to prioritize the work
needed, and general
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: grub2 (Ubuntu Eoan)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847458
Are the systems getting this set up for dual-booting at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848797
Title:
After upgrading to 19.10, boot screen shows: "Error: symbol
The code does look like it will chainload via shim:
linuxefi_secure_validate() runs, checks that the image is valid against
firmware stores and the MokList.
Then
grub_cmd_chainloader -> (grub_linuxefi_secure_validate() find the image
valid) -> grub_secureboot_chainloader_boot() ->
Removed block-proposed tag after doing one last smoketest to make sure
grub was booting fine.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848892
Title:
"error:
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848892
Title:
"error: Unknown TPM error." after upgrading to grub 2.04
To manage notifications about this bug go to:
Should be done very soon; we're waiting for the shim review board to
review, then it can be submitted to Microsoft for signing. Expect about
a week turnaround time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+ Some specific system (listed in upstream thread at
https://lists.gnu.org/archive/html/grub-devel/2019-10/msg00104.html)
+
+ Mostly ASUS systems, but also reported on some Dell systems.
+
+ The affected systems are used to boot in UEFI mode and will fail to
** Description changed:
+ [Impact]
+ Dual-boot users who have somehow had shim uninstalled from their system /
Secure Boot disabled.
+
+ [Test case]
+ (system with dual-boot setup for Ubuntu and Windows)
+ 1) uninstall shim/shim-signed from the system
+ 2) Run 'sudo grub-install -v'; ensure
It has nothing to do with whether the file handle is closed or not; this
is just confusing code because of how it's built.
Shim is supposed to be installed by the installer when you set up the
system in UEFI mode; this is done for you by the installer, and isn't a
dependency of grub because grub
I've already submitted a possible fix upstream for this issue (well, at
least something that will stop this breaking, and give us more
information to debug and fix it more permanently):
https://lists.gnu.org/archive/html/grub-devel/2019-10/msg00103.html
There isn't concensus there just yet, but
No; this patch is wrong.
For starters, you really ought to have shim installed, and that is the
primary cause for such failures -- somehow your install is incomplete,
and shim was removed either because the package was removed, or through
the use of boot-repair (IIRC it replaces shim with using
Public bug reported:
net-tools has been replaced by iproute2; so uses of ifconfig should be
replaced with ip ('ip link' or 'ip address').
Similarly, netstat is replaced by ss, and route is replaced by ip ('ip
route').
bind9 has already updated the uses of ifconfig (in ifconfig.sh) to be
able to
Public bug reported:
Hi,
As far as I can tell, the ubuntu-core-meta metapackage and the binary
packages it builds:
- ubuntu-core-libs
- ubuntu-core-libs-dev
Are no longer in use by snapcraft, the core snap or any other consumers;
and is out of date with that is considered the accepted list
This does not appear to be a new issue; but it is newly visible due to
the changes in 2.04: we've now upgraded to a new major release of GRUB,
and the modules are now no longer compatible with previous releases.
In other words, if you're running into this issue, your system was most
likely
Thanks. Let's put both tasks as Triaged again then, since it's obviously
not fixed in disco and bionic.
I don't think this qualifies as a regression though, since the feature
was never available before. It's just not finished since the systemd
side of this isn't complete.
** Changed in: systemd
What if you set SHIM_VERBOSE in firmware, using 'sudo mokutil --set-
verbosity true' after booting with just grub?
There should be debug messages showing up on screen to tell what is
going on in shim in this case, and having those will help in debugging
the issue.
** Changed in: shim (Ubuntu)
investigate why that
wasn't the case, first by trying to reproduce the issue.
** Changed in: debian-installer (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Tags added: writable-etc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849560
Title:
Please revise the files installed in /etc/
To manage notifications about this bug go to:
Public bug reported:
openssh-server and openssh-client install various files under /etc:
/etc/ssh/*
/etc/systemd/system/sshd.service
Please see if these files can be moved elsewhere, in accordance with
FHS: /etc should only contain files writable by the system
administrator, and in Ubuntu Core
** Tags added: writable-etc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849554
Title:
Please move cache files to a different location
To manage notifications about this bug go to:
Public bug reported:
The /etc/dbus-1/system.d/wpa_supplicant.conf is installed in the wrong
location. It is a system-wide default config for dbus, and as such
probably should be in /usr/share/dbus-1/system.d instead; like most
other DBus definitions installed on a typical system.
** Affects: wpa
Public bug reported:
On a typical install of an Ubuntu system, and in particular on a Ubuntu
Core system, there are various files under /etc/cloud.
Most of these files (especially on UC) appear to be default files that
are unmodified, and are furthermore bind-mounted such that they may be
Public bug reported:
/etc/apparmor.d/cache is currently used to keep cache files for
apparmor. Unfortunately, these files are in a location that is
inconsistent with FHS guidelines for cache.
Moreover, /etc is not a core path for Ubuntu Core 20, which means it is
planned to not be writable; and
This bug is *not* a duplicate of 1839317; since we're not looking at
ARM-based systems here.
Could you please update your grub-efi-amd64 and grub-efi-amd64-signed
packages (well, make sure your system is fully up to date), then run:
sudo grub-install -v
And include the output here.
Not all the
I really don't think this is ubiquity's fault; more aiming to grub-
installer, the d-i component we call as part of ubiquity.
And yes, it's not at all a new issue, but something that's been
difficult to handle for a number of years. Install happens properly, but
in some circumstances, grub-probe
If you use F8 or F12 (or whatever hotkey to get the firmware's boot
menu); can you then run "Windows Boot Manager" and successfully start
Windows?
How was the installation done? Could you please describe how the disk
was partitioned for dual-booting, and the steps taked in the installer?
At this
Immediately after installation and rebooting into the installed system,
are there any files in /var/lib/shim-signed/mok ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848142
Title:
package
There's clearly something odd happening then, because I am unable to
reproduce this on various hardware; installing from USB as I normally
do.
How are the drives partitioned to begin with? I wonder if something is
keeping grub from using the hard-drive on which it installed (as one
certainly
Setting back to Incomplete: it appears that /boot/efi is not mounted,
we're trying to figure out why not. Furthermore, the files installed
there are not up to date (probably because they were instaleld to the
mountpoint, not to the real location), and SecureBoot is disabled on the
system.
**
After further discussion with Chris; seems like this might have been a
misunderstanding, looking at two different source trees for the
software.
Chris; can you please confirm whether we've reached consensus on the
state of the chainloader code for SB? From my read, the patches look to
be properly
I'm not sure what to think about this failure; what's clear is it's not
'ubiquity', because we're dealing with debian-installer, but I'm not
sure what component. In fact, it looks more subtle than this, some sort
of more obscure failure:
Oct 11 18:42:06 base-installer: 'Ubuntu-Server 19.10 _Eoan
nee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: partman-efi (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubiquity (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
I could reproduce this trivially; a simple netplan config:
network:
version: 2
renderer: networkd
ethernets:
eth0:
dhcp: yes
Will show that my domain "cyphermox.net" here is not passed from DHCP in
networkd to resolved (and does not show in /run/systemd/resolve/stub-
resolv.conf
As long as any call of 'netplan apply' does not outright fail, that's
good, as this was a comment based on the changes to checking if "SNAP"
is set in the environment.
'netplan apply' was run as part of the autopkgtests, it does not fail
when SNAP environment is missing, and running the dbus
The automatically identified test failures are actually limitations of
the test infrastructure: on s390x and armhf (and arm64), wifi is not
available and this leads to the tests erroring out.
Verification-done for xenial:
ubuntu@ip-172-30-0-137:~$ sudo apt install nplan
sudo: unable to resolve
Autopkgtests have been run for both bionic and disco (attached, see
description), all are successful and were so without requiring to be re-
run.
Individual bugs have been verified for bionic and disco, despite not
being labeled for disco due to the reupload Brian did.
Marking verification-done
** Description changed:
[Impact]
This release contains both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these improvements.
The notable ones are:
- - Added new "feature flags" to identify new features
- - Added support
Verification-done on disco:
ubuntu@ip-172-30-0-243:~$ lsb_release -cs
disco
ubuntu@ip-172-30-0-243:~$ dpkg -l netplan.io systemd | grep ii
ii netplan.io 0.98-0ubuntu1~19.04.1 amd64YAML network
configuration abstraction for various backends
ii systemd240-6ubuntu5.7
Verification-done on bionic:
ubuntu@ip-172-30-0-140:/run/systemd/network$ lsb_release -cs
bionic
ubuntu@ip-172-30-0-140:/run/systemd/network$ dpkg -l netplan.io | grep ii
ii netplan.io 0.98-0ubuntu1~18.04.1 amd64YAML network
configuration abstraction for various backends
Verification-done on bionic:
ubuntu@ubuntu-XPS-15-9570:~$ lsb_release -cs
bionic
ubuntu@ubuntu-XPS-15-9570:/sys/class/net/bond0/bonding$ dpkg -l netplan.io |
grep ii
ii netplan.io 0.98-0ubuntu1~18.04.1 amd64YAML network
configuration abstraction for various backend
Verification-done for disco:
ubuntu@oddish:~$ lsb_release -cs
disco
ubuntu@oddish:~$ dpkg -l netplan.io | grep ii
ii netplan.io 0.98-0ubuntu1~19.04.1 amd64YAML network
configuration abstraction for various backends
ubuntu@oddish:~$ cat /etc/netplan/01-network-manager-all.yaml
Verification-done on bionic:
ubuntu@ubuntu-XPS-15-9570:~$ lsb_release -cs
bionic
ubuntu@ubuntu-XPS-15-9570:~$ cat /etc/netplan/01-network-manager-all.yaml
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: networkd
wifis:
wlp59s0:
access-points:
Verification-done on disco as well:
After applying the update I can successfully run 'netplan apply' on a
system on which a label exists; this would otherwise fail even if the
interface isn't mentioned in YAML:
ubuntu@oddish:~$ cat /etc/netplan/01-network-manager-all.yaml
# Let NetworkManager
Verification-done on disco:
ubuntu@oddish:~$ lsb_release -cs
disco
ubuntu@oddish:~$ cat /etc/netplan/01-network-manager-all.yaml
# Let NetworkManager manage all devices on this system
network:
version: 2
renderer: networkd
wifis:
wlp58s0:
access-points:
cyphermox.net:
Fix Released in eoan (where netplan is 'netplan.io'); Won't Fix for the
netplan.io xenial task, since the name of the source package is 'nplan'
there.
** Changed in: netplan.io (Ubuntu)
Status: New => Fix Released
** Changed in: netplan.io (Ubuntu Xenial)
Status: New => Won't Fix
** Tags removed: rls-y-incoming
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612906
Title:
cryptsetup does not support ZFS
To manage notifications about this bug
This has been fixed for a while; APT::Periodic::Unattended-Upgrade is
set to 0 if you pick No automatic updates; this is how we want things to
be. In the installer, the other option is to "install security updates
automatically".
** Changed in: pkgsel (Ubuntu)
Status: Confirmed => Fix
** Tags removed: rls-y-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go
** Tags removed: rls-y-incoming
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611256
Title:
X to Y upgrade fails with gconf2 depends on python3:any; however:
** Tags removed: rls-y-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366546
Title:
Ubuntu doesn't provide \EFI\BOOT\BOOTX64.EFI for UEFI systems
To manage notifications about this bug go
** Tags removed: rls-aa-incoming
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723390
Title:
lxd containers have become degraded
To manage notifications about this
Is this still an issue on supported releases?
** Changed in: systemd (Ubuntu)
Status: Confirmed => Incomplete
** Tags removed: rls-aa-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Please remove compiz-plugins-experimental 2:0.8.16-2
All architectures are in Dependency wait; compiz-plugins-experimental is
waiting on the whole compiz stack with 2:0.8.16-2. Past feature-freeze
and DI freeze, this is unlikely to land right now and may be re-synced
later
Public bug reported:
Please remove node-prismjs from eoan-proposed
- it's blocked on non-existing node-clipboard
- has an RC bug in Debian on that subject,
- only in unstable and blocked there for >200 days
** Affects: node-prismjs (Ubuntu)
Importance: Undecided
Status: New
--
I can't find who promoted this package to main; but it is there right
now, and it seems it also was in previous releases. Closing as Fix
Released based on the ack from Seb128 thatit would be subscribed to by
desktop-bugs.
** Changed in: gssdp (Ubuntu)
Status: New => Fix Released
--
You
So with my PPA version, what do you have in
/run/usb_modeswitch/current_cfg then?
I suspect the program is crashing, I probably made a small mistake in
the patch?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+ Snapd will want to make use of the DBus support to call on netplan to apply
network configuration changes live, when asked by snap applications.
+
+ [Test case]
+ Run the following command:
+ $ dbus-send --print-reply --system --type=method_call
MIR approved for both libio-async-loop-epoll-perl and liblinux-epoll-
perl.
Both have a subscriber, and I did a cursory review of the code. These
perl packages are well maintained by the Debian Perl team and the
packaging is simple. I'm approving these as per the usual process: Perl
packages are
Rather than pasting just a single error line, please include the full
debug log for running usb-modeswitch. You can do that by modifying
/etc/usb_modeswitch.conf:
EnableLogging=1
And looking under /var/log/ for the log file written by usb-modeswitch
after it has run.
Having the full file means
Public bug reported:
Please backport the DBus feature in netplan to Ubuntu 16.04's version of
netplan.
netplan is used on Core 16; DBus support would be used by snapd.
** Affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
Well, if it was a matter of never having been tested on 32-bits, that's
something we can also address by removing the builds for 32-bits.
The specific errors are here; when running autopkgtests which try to rebuild
the package and run unit tests:
Yes, those probably should be addressed. I don't necessarily do all the
work on these packages though; but I might have time next week to look
at them, and prepare a proper new release (with the testing that should
go with). Mario, let's see if we can block out just a bit of time to do
this?
--
Public bug reported:
link-grammar is blocking migration of some packages from eoan-proposed,
and has been for a number of days:
sqlite3 (3.29.0-1 to 3.29.0-2) in proposed for 14 days
Regressions
link-grammar/5.6.2-1ubuntu1: armhf (log, history), i386 (log, history)
python3.7 (3.7.4-2ubuntu1 to
** Description changed:
+ [Impact]
+ Users of netplan who need to configure multiple values for ARP IP targets.
+
+ [Test case]
+ Write a valid configuration for a bond with multiple ARP IP targets:
+
+ network:
+ version: 2
+ renderer: networkd
+ bond:
+ bd0:
+ [...]
+
** Description changed:
+ [Impact]
+ netplan users configuring a wireless connection; who would like to use
password hashes for the password (ie. they might not know the real password,
etc.)
+
+ [Test case]
+ Write configuration for netplan wireless interface:
+
+ network:
+ version: 2
+
** Description changed:
- # netplan apply
+ [Impact]
+ Running 'netplan apply' when an interface has an alias/label defined for it.
+
+ [Test case]
+ On a system which has a label set for an interface:
+ ip addr add 192.168.0.1/24 dev eth0 label eth0:0
+
+ 1) run 'netplan apply'
+ 2) verify
** Description changed:
+ = netplan.io =
+
+ [Impact]
+
+ * IPv6 traffic failing to send/receive due to incompatible/low MTU
+ setting. Specifically, IPv6 traffic may have higher MTU requirements
+ than IPv4 traffic and thus may need to be overridden and/or set to a
+ higher value than IPv6
Please describe the problem here, rather than in forum posts. It's not
helpful to have to go through various pages and posts from different
people, with information that is potentially irrelevant to the bug. To
compound to the situation, pastebins have disappeared by now.
Please include all the
** Also affects: netplan.io (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is this tested in VirtualBox or on hardware?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837934
Title:
There is no warning to remove install media when rebooting
To manage notifications about
Public bug reported:
[Impact]
This release contains both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these improvements.
The notable ones are:
- Added new "feature flags" to identify new features
- Added support for
** Changed in: netplan
Status: Fix Committed => Fix Released
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Are we sure that not include "local:" does the right thing with systemd-
networkd? I can't say that I saw any code that hinted towards the fact
that it would be figured out automatically.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671951
Title:
networkd should allow configuring IPV6 MTU
To manage notifications
** Changed in: netplan
Status: Triaged => Fix Released
** Changed in: netplan.io (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819831
Title:
Since netplan only does writing configuration to be consumed by the
backends like systemd, this would actually be a systemd bug;
reassigning.
I thought that worked though, in some setups, especially with use-
routes: false as it was being done in the config above.
Nevertheless, it needs
Current state appears to be that Desktop Team should look into the
Recommends (gstreamer plugins-ugly), and someone have a review of the
XML parser options (as pointed out in the security review, specifically
for NOENT and RECOVER... maybe NONET should be added?).
** Changed in: rygel (Ubuntu)
I will review this now; but I expect it might need security review as
well.
** Changed in: libbluray (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
'netplan info' can list features that have been added to netplan in
recent versions.
However, it does not list renderers. Should we list them? Does it make
sense to?
How do we think having the list of renderers exposed would actually
change the behavior of things like
There was a previous MIR approved, and as per the usual process we do
not require a new MIR bug and review if the package was in Main before
and we can point to the previous MIR bug.
This package is fine to promote back to main.
** Changed in: libnftnl (Ubuntu)
Status: New => Fix
** Also affects: icu (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838322
Title:
Support Japanese new era "令和 (Reiwa)"
To manage
1 - 100 of 8811 matches
Mail list logo
