Fixing is required in cosmic as well since the issue is with the patch
used for gnu-efi 3.0.8 support. Disco is "unaffected"; I've synced with
Debian which has already fixed the issue.
** Also affects: gnu-efi (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: syslinux
Verification-done with shim-signed in xenial-proposed:
ii shim-signed 1.33.1~16.04.3+15+1 amd64
Secure Boot chain-loading bootloader (Microsoft-signed binary)
I've checked that a Secure Boot-enabled system correctly validates the
shim binary that gets installed to disk, that
Verification done on xenial:
ii shim 15+1533136590.3beb971-0ubuntu1
ii shim-signed 1.33.1~16.04.2+15+1533136590.3beb971-0ubuntu1
Verified that shim + shim-signed boot normally on a Xenial system.
Timeout can be set (using a newer mokutil than is available on xenial),
and certificates can be
** Changed in: grub2 (Ubuntu Trusty)
Status: Won't Fix => In Progress
** Changed in: grub2-signed (Ubuntu Trusty)
Status: Won't Fix => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think we'll need to backport the UEFI Secure Boot patches to trusty
after all -- there's a large number of changes in them, but it seems
better than attempting to adapt other patches (such as Windws 7/10
chainloading fixes with new shim, and memory truncation fixes). Having
the patchset at the
There was a pull request for this:
https://github.com/CanonicalLtd/netplan/pull/29
It took a while to get it implemented and reviewed, but I've now merged
the branch into master. We'll ship a new release with all of this very
soon.
** Changed in: netplan
Status: Triaged => Fix Committed
MAAS picks up information at commissioning time about the system. This
would include the NIC driver, which could just as well be used as an
additional matching criterion in netplan YAML.
There's a limit to how much netplan can and should try to figure out
what one means: we're supposed to do
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783940
Title:
route type: docs say "prohibited", code accepts only "prohibit"
To
Unassigned; I have added a nicer test runner so the tests can be more
easily controlled; they can be retrieved directly from the netplan
source.
** Changed in: netplan.io (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
--
You received this bug notification beca
Autopkgtests failures for ubuntu-image appear to be unrelated, the tests
show the machine has already booted at that point -- this is some kind
of other networking issue post-boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I really don't like the fact that the tests are not being run for the
package. In comparison, I'm not as worried about the use of chown -R in
the maintainer scripts.
Since this MIR was opened, the package has landed in Debian. I think
we'd really benefit from attempting to reconcile the two
Since this is explicitly about security mitigation, let's get a review
from the Security team.
** Changed in: python-django-debreach (Ubuntu)
Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Fix Committed
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806379
Title:
AFAICT this has been released in xenial, bionic, cosmic, and disco, for
netplan.io versions 0.40 and above.
** Changed in: netplan.io (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: netplan.io (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: netplan.io
Clearing up bug statuses: We'll fix this for 18.04 and above, but first
it needs to land in the development release. Won't Fix is for the
releases before 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Won't Fix for nplan: we will not be backporting these fixes to releases
prior to 18.04.
** Changed in: nplan (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That is a different issue we're solving elsewhere. You should be able to
override the UseMTU= field.
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nplan (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: netplan.io (Ubuntu)
Please see if this is solved by the fix for
https://bugs.launchpad.net/netplan/+bug/1807273 (setting use-mtu: false)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1724895
Title:
MTU not applied on
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800668
Title:
Clarify MAC and MTU setting requirements
To manage notifications
Fair enough. I do credit you by name already in the commit messages:
https://gitlab.freedesktop.org/plymouth/plymouth/merge_requests/10
https://gitlab.freedesktop.org/cyphermox/plymouth/commit/c46f446fe44457f599805b685547c2258bb3fa96
Setting to Triaged: it's easily reproduced by developers, and we have
all the information we need to debug it -- nothing is secret or hidden,
just needs someone to look at the packets and what resolved does with
them.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Triaged
--
You
Sorry, we don't see it there. The emails are re-jiggled by Launchpad.
If you prefer, you can send it to me directly (cyphermox AT ubuntu.com),
or decline to provide one (since it would show up in the commit logs for
plymouth)
--
You received this bug notification because you are a member of
It doesn't matter which process we use, it will be a big SRU regardless.
Also, of course it's an easy fix in MAAS, and it obviously works. I've
shown that setting no "macaddress" field in the netplan syntax does what
it should. Just don't specify a default for that value, and don't write
the
** Package changed: ubiquity (Ubuntu Disco) => casper (Ubuntu Disco)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796275
Title:
Screen reader is not auto-enabled on first login if enabled when
Gert, could you provide us with an email address so we can correctly
attribute the changes to you, given that you contributed the major part
of the patches that will go in plymouth?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The problem is that DEVTYPE is unreliable at best. Using the MAC of one
of the member interfaces is fine, but only if you really know what
you're doing.
I think we're otherwise back to matching by name instead of by MAC
address (or matching both), if you want to match "like ifupdown was
doing".
Verification-done with the xenial grub2/grub2-signed versions:
$ dpkg -l grub\* | grep ii
ii grub-common 2.02~beta2-36ubuntu3.20 amd64GRand
Unified Bootloader (common files)
ii grub-efi-amd642.02~beta2-36ubuntu3.20 amd64GRand
Unified
I disagree.
We'd be working around a real design issue in systemd, rather that
possibly matching against Type=ethernet (if that existed). I think we
should instead prioritize on avoiding this broken case in the other
parts of the networking stack, and make sure we fix systemd to provide
the right
Looks like there are some cases where syslinux will fail to load modules
with the proposed rebuild patch with the new gnu-efi. This is a
regression in syslinux; marking as verification-failed.
** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic
** Tags removed:
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed:
Please help to validate this SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784347
Title:
ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting
partitions name for the mpath
To
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed:
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed:
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed:
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed:
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed:
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed:
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed:
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed:
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed:
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed:
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but we still consider the previous verification to be valid.
** Tags removed:
*** This bug is a duplicate of bug 1736965 ***
https://bugs.launchpad.net/bugs/1736965
Resetting the tags to verification-done as per the discussion in
https://bugs.launchpad.net/netplan/+bug/1770082/comments/95.
The SRU had been rolled back due to a regression that needed to be
fixed, but
Verification-done on bionic: netplan.io 0.40.1~18.04.3
Verification-done on cosmic: netplan.io 0.40.2.2
I have checked that the new package in proposed now skips devices that
can't be identified as physical interfaces or that are known to be
members of bonds/bridges, etc. so as not to attempt to
** Changed in: gnome-shell-extension-desktop-icons (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.
https://bugs.launchpad.net/bugs/1806379
Title:
[
This was already landed in a prior SRU. Closing as Fix Released.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done-xenial
** Changed in: grub2-signed (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug
Resetting the tags to verification-done as per the discussion above.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug notification because you are a member of
you switched to ifupdown.
Regards,
Mathieu Trudel-Lapierre
Freenode: cyphermox, Jabber: mathieu...@gmail.com
4096R/65B58DA1 818A D123 0992 275B 23C2 CF89 C67B B4D6 65B5 8DA1
--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
If you are seeing this issue, what image are you using? Have you tried
booting to Ubuntu without the ISO connected?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798171
Title:
System fails to boot
** Changed in: nplan (Ubuntu)
Status: In Progress => Triaged
** Summary changed:
- No virtual interfaces
+ No support for interface labels
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+ Usage of juju to deploy systems with bridge configurations is severely broken
if using layer3+4 bonding, as renaming might be attempted and break the
application of config.
+
+ [Test case]
+ 1) Deploy a system using MaaS and Juju, with a network
OK; upstream got to an idea similar to your patch. I'm away from my
usual desk right now and apparently missing some credentials to log back
in to gitlab, but I will update current PRs on gitlab to propose a fix
similar to your patch: iterating through keyboards to remove them when
freeing
Seems like this is caused by nvidia drivers not liking s2idle or forcing
the use of 'deep' leads to reliable suspend/resume cycles. Properly
removing nvidia drivers leads to a working system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Verification-done for xenial: mokutil 0.3.0+1538710437.fb6250f-0ubuntu2~16.04.1
Verification-done for trusty: mokutil 0.3.0+1538710437.fb6250f-0ubuntu2~14.04.1
Verified that 'mokutil --reset', 'mokutil --export --db', 'mokutil --export
--mok' as well as setting a timeout via 'mokutil --timeout'
I spent a couple of hours looking at the disassembly for your crash
file, and I think one of the patches I applied, moving
keyboard->is_active = false earlier when removing input watches, should
improve the situation a lot. Otherwise, my next question mark is
relevant to the code optimization.
I can't get behind sponsoring that patch as-is. It seems to me like this
is patching around symptoms of an underlying issue rather than fixing
the real problem. I haven't been able to open your apport crash file yet
due to it being for i386, and I'm not set up to test that.
Let's start by making
How was the system installed? Did this use d-i (the alternate installer
image), or ubiquity?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767527
Title:
[18.04] Installation boot failure. WARNING:
Public bug reported:
Dell XPS 15 (9750); it might eventually manage to suspend when the lid
is closed, but more often than not will not wake up again when the lid
is opened. Waking up using the power button often results in a system
that is apparently frozen (graphics displayed are the last on
eu Trudel-Lapierre (cyphermox)
** Changed in: netplan
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: netplan
Importance: Undecided => High
** Changed in: netplan
Status: New => Triaged
** Tags added: regression-release
** Tags removed:
But does it fix the crash for you? You shouldn't worry about the dates
on the files, those are in part caused by the changelog entry when
building the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For context:
It looks like the issue is really with the call to
"set_handler_for_input_source()" on a plugin. renderer->plugin_interface
is null, so dereferencing that fails:
https://paste.ubuntu.com/p/tmcVcvgGXw/
All in all, much easier to comprehend when I think of looking at the
disassembly,
Actually, according to the backtraces the issue isn't with
renderer->backend; we're not even reaching that point. It's still a
potential issue though.
Same ppa as before: ppa:cyphermox/ppa
I have uploaded a new plymouth there, which should mitigate the crash
exactly as reported in the
Please use bug 1768827 to track such "no IP at boot" issues; there's
nothing that currently indicates that this is a regression, it needs
further investigation, but not here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Marcos:
Please file a new bug for your own issue; include the output of
'networkctl', and report the bug number here so we can find it.
>From a quick look, I think there's no carrier detected. This could be a
driver bug.
--
You received this bug notification because you are a member of Ubuntu
Yes, that's because it doesn't appear like the issues you have are a
regression caused by the updates, and we don't know what's wrong. You
have a bug open for your issue, and we still need to figure out what
doesn't work there.
--
You received this bug notification because you are a member of
** Description changed:
[Impact]
- All UEFI users.
+ Shim needs to be updated for the latest fixes, security fixes, and new
features introduced upstream (see below). Shim is kept in sync across supported
releases to avoid subtle policy differences between releases, and because any
upload
Public bug reported:
[Impact]
All UEFI users.
[Test case]
Test plan is at
http://wiki.ubuntu.com/UEFI/SecureBoot/ShimUpdateProcess/TestPlan
[Regression potential]
---
Update shim in all supported releases of Ubuntu.
** Affects: shim (Ubuntu)
Importance: Undecided
Status:
Verification done on xenial:
ii shim 15+1533136590.3beb971-0ubuntu1
ii shim-signed1.33.1~16.04.2+15+1533136590.3beb971-0ubuntu1
Verified that shim + shim-signed boot normally on a Xenial system.
Timeout can be set (using a newer mokutil than is available on xenial),
and
** Description changed:
[Impact]
- All Ubuntu users on UEFI systems
+ Potentially any Ubuntu users on UEFI systems; as mokutil is used to control
from the userland the behavior of Secure Boot via shim.
+
+ New features have been introduced in mokutil that we'll want to make use
+ of in
Verification-done for cosmic using netplan.io 0.40.2.1:
I have verified that renames happen correctly with the config provided
in test cases and the config I have shown for the testing on bionic.
In all cases, set-name is applied as the new name for the interface, as
expected. On reboot, this is
Verification-done on bionic with netplan.io 0.40.1~18.04.2:
Using the following config:
network:
version: 2
ethernets:
maas0:
addresses:
- 10.3.21.29/20
gateway4: 10.3.16.1
match:
macaddress: 52:54:00:4d:3e:84
Verification done for bionic with netplan.io 0.40.1~18.04.2:
Autopkgtests are all passing (and passed first run); and invidividual
bugs for this backport are all verification-done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You
** Description changed:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
@Gert,
I've made some changes to your suggestion (we don't want to circumvent
creating more DRM devices than the first successful one, I think) and it
looks like the "right value" according to upstream for the compiler
warning is to return false.
Please try the new package on my ppa
Verification done on bionic with netplan.io
I was able to confirm that in an IPv6-only scenario, netplan now does
not render invalid dns-search for the IPv4 method.
root@working-guinea:~# cat /run/NetworkManager/system-connections/netplan-eth0
[connection]
id=netplan-eth0
type=ethernet
Identified as the system running out of memory, this was a VM with only
1G RAM, and with 2G it's behaving fine. Closing as Invalid.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Did you modify the allowed Secure Boot certificates in your machine's
firmware? What hardware did this error show up on?
** Changed in: secureboot-db (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Did the upgrade process fail?
If you run 'sudo apt -f install' is any change suggested there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800750
Title:
Error message during upgrade: "Error
Verification done on bionic with netplan.io 0.40.1~18.04.2:
I have checked that with ipv4 link-local enabled as per the use-case, an
ipv4 link-local address is correctly set up by systemd-networkd as
requested by the netplan config.
ubuntu@nice-baboon:~$ sudo vi /etc/netplan/50-cloud-init.yaml
Verification done on bionic with netplan.io 0.40.1~18.04.2:
I have verified that a route set to scope: link is correctly accepted
and adding to the main routing table:
ubuntu@nice-baboon:~$ sudo netplan --debug apply
** (generate:1231): DEBUG: 18:19:53.369: Processing input file
cp -a is supposed to preserve ownership. -a means "-dR --preserve=all".
Could someone look at what happens, by displaying more than just the
/run/systemd/resolve/stub-resolv.conf file? All files in
/run/systemd/resolve/ are relevant here.
This has more smells of being affected my UMASK and
Looks like it's depmod crashing; it's the only thing common between
linux-image and linux-modules postinst, and for linux-modules it's ||
true, thus we see the first "Killed" line but it doesn't fail the
package installation.
--
You received this bug notification because you are a member of
** Changed in: grub2 (Ubuntu)
Status: New => 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/1800722
Title:
EFI booting + /boot on LVM == inaccessible boot menu
To manage
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800703
Title:
kernel packages die while running postinst scripts
To manage
Public bug reported:
Get:1 http://archive.ubuntu.com/ubuntu cosmic/main amd64 libnl-3-200 amd64
3.4.0-1 [53.9 kB]
Get:2 http://archive.ubuntu.com/ubuntu cosmic/main amd64 libnl-genl-3-200 amd64
3.4.0-1 [11.1 kB]
Get:3 http://archive.ubuntu.com/ubuntu cosmic/main amd64 wireless-regdb all
Public bug reported:
Give more information about the error, including its exact location in
the code.
Make the error messages shorter but still understandable.
Present clear context so people understand what we found was wrong, if
not from line/column number, then from the extract from their
** Changed in: netplan
Status: New => Fix Committed
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu Disco)
Importance: Undecided
Public bug reported:
We already document that you should match by MAC when setting MTU.
Because MAC addresses are set in the link file as well, they should
also specify a MAC.
Also point out that the restriction only applies to networkd.
** Affects: netplan
Importance: High
Public bug reported:
- docs: example with complex routing should specify networkd renderer.
** 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.
-perl (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
** Changed in: percona-xtrabackup (Ubuntu)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
** Changed in: percona-xtradb-cluster-5.7 (
Verification-done with netplan.io 0.40.1~18.04.2 on bionic:
I have verified that with dhcp4: no, dhcp6: no, accept-ra: no on the
bridge interface and not static addresses set, the interface is brought
up correctly by networkd.
root@working-guinea:~# cat /etc/netplan/50-cloud-init.yaml
network:
Verification-done on bionic using netplan.io 0.40.1~18.04.2:
Verified that with umask set, netplan correctly generates the files for
systemd with 644 permissions, and they are succesfully read by systemd-
networkd.
root@working-guinea:~# umask
0077
root@working-guinea:~# cd /run/systemd/system/
Re-confirmed that netplan.io correctly reads "prohibit" instead of
"prohibited" in the manual, in accordance with the actual supported
values.
Verification-done on bionic using netplan.io 0.40.1~18.04.2.
** Tags removed: verification-needed verification-needed-bionic
** Tags added:
Oh, I know you didn't. It was a comment about Will's suggestion on his
bug (I marked duplicate of this one).
FWIW, I'm all for changing the default if testing shows there's a
benefit, and my suggestion was that if we're to do it, do it sooner
rather than later; but it *does* require concerted,
Marking verification-done for bionic using 0.40.1~18.04.2.
root@working-guinea:~# sudo vi /etc/netplan/50-cloud-init.yaml
root@working-guinea:~# sudo netplan try
Error in network definition /etc/netplan/50-cloud-init.yaml line 6 column 4:
unknown key verion
An error occurred: the configuration
Marking verification-done for bionic using 0.40.1~18.04.2.
Re-confirmed that 'netplan ip leases ' behaves correctly:
When the device is managed by networkd using DHCP, you get a lease
output. Otherwise, if managed by networkd, you will have the "No lease
found" error message (as expected), and if
Marking verification-done for bionic using 0.40.1~18.04.2.
'netplan try' now correctly restores terminal state again; in Control-C
case as well as when config is validated or the timeout expires.
** Tags removed: verification-needed verification-needed-bionic
** Tags added:
Re-confirming that the manpage now lists "gratuitous-arp" as the correct
field, along with the supported typo.
Marking verification-done for bionic using 0.40.1~18.04.2.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this
Marking verification-done for bionic using 0.40.1~18.04.2.
Re-confirming that 'mtu' is now correctly documented in the manual.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member
AFAIK at the moment there isn't proper WPA Enterprise support (well,
most TLS methods appears to be missing kernel patches). Let's please be
careful about changing the default wireless daemon to iwd, there's a
couple of moving parts there, it's not just about changing the software.
For instance,
501 - 600 of 8586 matches
Mail list logo
