What's the point of having 'kernel'? You have a boolean here
specifically because you'll likely want to override the default,
whatever it might be. I'm fine with *not writing* accept-ra if that
helps, but for most cases, this is just the kind of option that people
should avoid touching.
FWIW, as
unbound attempts to add itself as a local resolver (pointing to
127.0.0.1). I think this will require specific integration work so that
unbound can properly update/ tell systemd-networkd that it wants to be
able to serve as a resolver.
** Changed in: squid3 (Ubuntu)
Status: New => Invalid
There was a misunderstanding there: I never suggested we should use xkb-
keymap instead (or at least, that's not the message I was trying to
convey).
The intent was to reduce delta by not removing so much code, when
console-setup merges are already difficult. I didn't foresee that some
of that
This would be a systemd-networkd bug, which I suspect might have already
been fixed too. Reassigning to systemd.
** Package changed: nplan (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
Your original config in comment #1 is correct: you must specify the
underlying devices, because those names are matched later for
"interfaces:" in the bond config.
The issue with 802.3ad is likely a driver issue or a bug in systemd; the
right mode needs to be set by networkd (which may require
** Changed in: netplan
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1756322
Title:
'netplan apply' fails when trying to activate
postfix takes a copy of resolv.conf for its own use, in its own queue
directory. This is already well integrated by way of either resolvconf
triggering the copy on changes (using update-libc.d) or by if-up / if-
down. This will need work to "improve" the integration story; however
postfix should
Looks like the current behavior should be sufficient for postfix to
integrate as well as it did with resolvconf: marking this Invalid.
** Changed in: postfix (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
dhcpcd5 is redundant as a DHCP implementation in Ubuntu; but it does
"integrate" with resolvconf by way of its own shipped dhcpcd-
hooks/20-resolv.conf. It does check before calling 'resolvconf -a' and
'resolvconf -d' to add/remove its own interface file; and uses this hook
file in order to
nee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team
(ubuntu-security)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1747460
Title:
[MIR] py-macaroon-
py-macaroons-bakery looks good to me; MIR approved.
** Changed in: py-macaroon-bakery (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
Whether or not /e/n/i supports something correctly or just happens to
work by sheer luck has no bearing on what is technically correct and
sensical -- let's abstract this, what we need to concern ourselves with
here is netplan, cloud-init and maas.
In the network world, it is absolutely true that
libmpg123-0 's MIR is approved then.
** Changed in: mpg123 (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mpg123 in Ubuntu.
https://bugs.launchpad.net/bugs/1753450
Title:
04.
** Changed in: util-linux (Ubuntu)
Assignee: Canonical Foundations Team (canonical-foundations) => Mathieu
Trudel-Lapierre (cyphermox)
** Changed in: util-linux (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-power-systems
Assignee: Canonical Foundations Team (ca
** Description changed:
+
+ [Impact]
+ Any user of Ubuntu on multipath, where the default path separator has been
changed to something else. This possibly affects other scenarios where the
partition separator can be changed.
+
+ [Test case]
+ 1) Install Ubuntu on multipath system
+ 2) Change
This is working as designed.
NetworkManager now uses a metric "penalty" when connectivity cannot be
detected as full for a connection, and reduces the metric accordingly.
This makes it so that if you're connected to both wired and wireless,
and your wired connection becomes bad but the wireless
Marking Incomplete for now, in case there's more to it than a
connectivity checking issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1788659
Title:
network
No, this is dnsmasq:
udp 0 0 0.0.0.0:67 0.0.0.0:* 5382/dnsmasq
Please make sure you dnsmasq is correctly configured for your use case
(and probably, not configured at all if you want to use isc-dhcp)
** Changed in: isc-dhcp (Ubuntu)
Whether it's been running for 30 minutes or not doesn't change much
though; the connection *can* fail, and the connectivity checking is a
pretty simple HTTP check.
Could you please attach debug logs for NetworkManager (with the
connectivity checking enabled) -- see
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,
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
** 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:
Hi Kyle,
Can you help with verifying the that patch works as expected on 18.04?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784347
Title:
ISST-LTE:
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
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 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
*** This bug is a duplicate of bug 1800055 ***
https://bugs.launchpad.net/bugs/1800055
Marking as a duplicate to bug 1800055
** This bug has been marked a duplicate of bug 1800055
iwd does not work with network manager
--
You received this bug notification because you are a member of
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,
@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
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
Touch seeded packages, which is subscribed to
I'm unsure whether this is NM or n-m-openvpn. Looks more like NM, since
downgrading n-m-openvpn alone didn't seem to change anything.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Public bug reported:
I'm seeing some weird issue with the new NM + openvpn; if I create a new
VPN connection, and add certificate options (verify name exactly, plus
TLS auth), these options are not saved, leading to the connection
failing.
The following versions lead to an invalid connection:
ii
I'm not convinced that this patch is necessarily what's the right thing
to do -- in your examples, you have mpatha1, for instance -- using no
sparator at all. In this case, fdisk would still display the device
incorrectly.
--
You received this bug notification because you are a member of Ubuntu
Verification done with netplan.io 0.40.1~18.04.1:
I have verified that when using ip=dhcp / ip6=dhcp on the kernel cmdline
to boot to a remote filesystem; initramfs's scripts correctly write
"critical: true" in /run/netplan/.yaml, and that config is
correctly interpreted by netplan as being
Resetting to verification-done for bionic; using netplan.io
0.40.1~18.04.1:
I have run more tests and I can verify that renames at boot are behaving
correctly with netplan -- netplan follows exactly the configuration
provided on the system:
network:
version: 2
ethernets:
ens6:
Please help to validate this SRU.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784347
Title:
ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting
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
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
No need to re-test these; it's already been included in bionic/cosmic
and bug comments are a side-effect of the changelogs for the upload with
this backport.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic
This means we'll need to identify what patches need to be applied on top
of v237 to make this work.
Is this crippling? Are we able to verify that dhcp customization work
despite anything missing in systemd? I think it's the case; but I'd like
a second opinion. To be clear: I think we can verify
I also forgot to mention another entry I see in some of the configs:
set-name: ens3
If you do not need to explicitly rename the interfaces yourself to a
different name, I would avoid setting this at all. It *may* be being set
automatically by cloud-init (if that's in use, but the configs
** Description changed:
+ [Impact]
+ Minimal installs using netplan to configure the network.
+
+ [Test case]
+ 1) Install Ubuntu minimal server / cloud image
+ 2) Edit /etc/netplan/01-netcfg.yaml to configure the network as necessary.
+ 3) Run 'sudo netplan apply'. Verify that the network comes
hanged in: netplan.io (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1821867
Title:
network
All of these values should be coming directly from the netplan YAML. Are
all of these options required?
I see:
match:
macaddress: # Do you need to match the interface in this case? Is it
sufficient to match by name if only ens3 is being configured?
Also:
dhcp-identifier: mac #
Yes, that does explain it.
/run/netplan/.yaml is written automatically by initramfs-
tools when booting with a remote root (ie. iscsi); so this does check
out: for example, 'critical' is required in that case, otherwise as soon
as someone runs 'netplan apply' the network will go down and you
Reassigning to systemd -- netplan isn't limited, but if systemd-networkd
crashes that's a bug in systemd-networkd.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: netplan
--
You received this bug notification because you are a member of
That's odd. Let's dig in deeper, as it quite likely might be a systemd
bug, but I rather be certain it's not us doing something wrong.
Could you please attach the config files generated in
/run/systemd/network/ so we can confirm that the routes are created for
the right devices?
Thanks!
**
netplan is currently writing about as much as we can for the
networkd/udev configs; some values we don't know how to handle at all.
Looking at this, it feels to me like there will indeed be a need to find
a different data point to differentiate the interfaces, and MAC and
driver are not
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => Triaged
** Changed in: netplan.io (Ubuntu)
Status: New => Triaged
** Changed in:
This isn't netplan, it's systemd-networkd. Netplan only writes
configuration for the chosen renderer (in this case, systemd-networkd).
Either systemd needs to not wipe out foreign addresses (I believe there
is a PR in git for that) or keepalived should somehow interface with
systemd so they can
Kept a task for keepalived (Incomplete) in case it turns out there's
something we can do there.
Also added a task for systemd, since that would definitely require
development work.
Marked Invalid for netplan, as since netplan only translates config from
the YAML to what networkd or
*** This bug is a duplicate of bug 1798562 ***
https://bugs.launchpad.net/bugs/1798562
** This bug has been marked a duplicate of bug 1798562
After a side by side installation, resized filesystem is corrupted
--
You received this bug notification because you are a member of Ubuntu
Touch
** Also affects: e2fsprogs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: e2fsprogs (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+ - Users resizing filesystems using resize2fs.
+ - Resizing an existing Linux
Verification-done for bionic using e2fsprogs 1.44.1-1ubuntu1.1:
ubuntu@humble-cod:~$ qemu-img convert vda1b.qcow2 vda1b.raw
ubuntu@humble-cod:~$ e2fsck -f vda1b.raw
e2fsck 1.44.1 (24-Mar-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking
:Verification-done for cosmic:
ubuntu@superb-ram:~$ qemu-img convert vda1b.qcow2 vda1b.raw
ubuntu@superb-ram:~$ e2fsck -f vda1b.raw
e2fsck 1.44.4 (18-Aug-2018)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking
Okay, this bug has absolutely nothing to do with grub or netplan.
Changing the renderer couldn't possibly affect the behavior of X, and
the grub configuration looks, at a glace, to be run-of-the mill; pretty
much default if you disregard that there is any number of different
installs on the
This does not need re-testing, already in bionic/cosmic, just closed
again due to changelog for this big backport.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- netplan, keepalived, netplan-apply
+ Restarting systemd-networkd breaks keepalived clusters
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: keepalived (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
*** This bug is a duplicate of bug 1815101 ***
https://bugs.launchpad.net/bugs/1815101
** This bug has been marked a duplicate of bug 1815101
Restarting systemd-networkd breaks keepalived clusters
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Summary changed:
- netplan removes keepalived configuration
+ Restarting systemd-networkd breaks keepalived clusters
** Summary changed:
- Restarting systemd-networkd breaks keepalived clusters
+ [master] Restarting systemd-networkd breaks keepalived clusters
--
You received this bug
** Tags removed: rls-x-incoming
** Tags added: rls-ee-incoming
** Also affects: gnome-control-center (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: unity-control-center (Ubuntu
I believe we've fixed this already, especially since it is a bug that
was reported prior to the release of 16.04. We do have developers who
routinely use dvorak for keymap and would otherwise not have been able
to login to their systems.
Reassigning to console-setup, since it is the most likely
This appears to still be unresolved. What are the next steps? Do we
still want to add a Pre-Depends? How will d-i and image builds be
verified to not regress?
** Changed in: sysvinit (Ubuntu Xenial)
Status: In Progress => Triaged
** Changed in: sysvinit (Ubuntu Xenial)
Assignee:
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1668639
Title:
Add a trigger to reload rsyslog when a new configuration file is
dropped in
Assigning Dimitri who last updated this; is it still an issue?
** Changed in: console-setup (Ubuntu Xenial)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags removed: verification-done-artful verification-done-xenial
verification-done-zesty
** Changed in: systemd (Ubuntu)
Status: New => In Progress
** Changed in: systemd (Ubuntu Zesty)
Status: New =>
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1825448
Title:
gnupg2 autopkgtest 'simple-tests' should be included in x/b/c
Status in gnupg
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1825186
Title:
gpgv-win32 autopkgtest always fails
Status in gnupg package in Ubuntu:
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1806012
Title:
set-cpufreq: 'powersave' governor configuration sanity on ubuntu
server
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1828892
Title:
systemctl - alias service reports inactive while aliased is active
Status in
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/1825856
Title:
gnupg package 'gpgv-udeb' conflicts with gnupg2 (xenial)
Status in gnupg
This is a more complex issue; it's not just about LXD, but the general
story for installing "minimal" installs.
The fact that openssh-server was not installed as part of the ubuntu-
server is a separate bug we've covered in a different bug report.
Currently, desktops allow picking a "full"
** Tags added: rls-x-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1828901
Title:
add PTY support for runuser
Status in util-linux package in Ubuntu:
Fix
Kees,
I the fix in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766052 sufficient
to address the situation? Do we still need to do more to systemd (note,
the GH issue was closed upstream following Dimitri's input)?
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
** Tags removed: rls-dd-incoming
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1756595
Title:
disk space info inadvertently provides all
>From what I can tell, the routing is exactly how it should be:
[from the bug description]
root@search-3 /run/systemd/network # ip route
default via 95.216.96.129 dev enp0s31f6 proto static
10.0.0.0/24 dev tun0 proto kernel scope link src 10.0.0.13
10.0.2.0/24 dev vlan4000 proto kernel scope
Closing as Invalid for netplan: the config generated is exactly as it
should for the netplan YAML that was provided. This isn't a bug in
netplan.
** Changed in: netplan
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1798369
Title:
Reinstall Ubuntu (with preserving existing data) shows error message
due to
** Also affects: initramfs-tools (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: initramfs-tools (Ubuntu Bionic)
Status: New => Triaged
** Tags removed: rls-ee-incoming
** Tags
** Tags removed: rls-cc-incoming
** Tags added: rls-cc-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1791820
Title:
/usr/share/apport/apport-
** Tags removed: rls-dd-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1832882
Title:
libcurl-gnutls segfaults spotify client
Status in curl package in Ubuntu:
** Changed in: vim (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1823651
Title:
vim ftbfs in cosmic (i386 only)
Status in vim package
Looks like noto sources now have the right glyphs (since their April 9
release, actually). It will need an update both in Debian and Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
unicode-data in eoan does include Reiwa. Reverse-depends probably still
need to be rebuilt (I'm testing gucharmap which seemed easy enough to
patch to work).
** Changed in: unicode-data (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of
Oops; picked the wrong openjdk...
FWIW; according to the email by Mitsuya Shibata, openjdk 8 and 11 at
least are affected (so, everything prior to disco if updates are not
applied. Openjdk-8 updates appear to already be at 8u212, which should
include Reiwa support. Marking as Fix Released so we
mozc appears to be all done (LP: #1823444)
** Changed in: mozc (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: mozc (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: mozc (Ubuntu Cosmic)
Status: New => Fix Released
** Changed in: mozc (Ubuntu Disco)
** Tags removed: rls-ee-tracking
** Tags added: rls-ee-notfixing
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1543799
Title:
isc-dhcp-server & isc-dhcp-server6 systemd
After consideration, we're not going to prioritize fixing this for the
EE release (in other words, the Canonical Foundations time isn't going
to be actively working on fixing this). It doesn't mean the bug won't be
fixed, just that there is no company work assigned to the bug.
For now, there's a
I don't think it's *-control-center.
At the time, that was filed there by pitti, who correctly pointed out
that something might need to depend on libnss-myhostname (from systemd)
for a fallback to resolving hostname via just /etc/hostname (since
/etc/hosts isn't changed). At this point though, it
Seems like this would still apply to Eoan, marking rls-ee-tracking
** Tags removed: rls-x-incoming
** Tags added: rls-ee-tracking
** Changed in: isc-dhcp (Ubuntu)
Status: Confirmed => Triaged
** Also affects: isc-dhcp (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also
Still verification-done on bionic and cosmic; this hasn't changed with
the new revision in -proposed.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic verification-done-cosmic
--
You received this bug
** Description changed:
- * Impact
+ [Impact]
+ When using a VPN the DNS requests might still be sent to a DNS server outside
the VPN when they should not
- When using a VPN the DNS requests might still be sent to a DNS server
- outside the VPN when they should not
+ [Test case]
+ 1) Set up a
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1671951
Title:
networkd should allow configuring IPV6
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
** 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
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
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Tags removed: rls-aa-incoming
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1723390
Title:
lxd containers have become degraded
Status
There are mentions of Reiwa in icu in eoan. I'm not sure if this is a
complete fix, since the code appears to have changed somewhat from the
version of icu in Bionic and Disco.
Bionic certainly looks unfixed. Disco doesn't incldue the mentions of
"reiwa" that are present in the eoan code base.
icu split up into bug 1838322.
** Changed in: openjdk-8 (Ubuntu Xenial)
Status: New => Fix Released
** Changed in: openjdk-8 (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: openjdk-8 (Ubuntu Disco)
Status: New => Fix Released
** No longer affects: icu (Ubuntu)
601 - 700 of 718 matches
Mail list logo
