You filed the bug report against NetworkManager. But the "up.d" hook is
called differently in NM, see https://netplan.io/faq#use-pre-up-post-up-
etc-hook-scripts
If this is about /etc/network/if-up.d then it should be targeted towards
the "ifupdown" package. I'm adding a corresponding bug task.
** Changed in: netplan
Status: In Progress => Fix Committed
--
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/2060311
Title:
Setting "optional: true" to overcome he
Arguably, the "/usr/lib/netplan/00-network-manager-all.yaml" should be
shipped by the network-manager package, instead of ubuntu-settings...
The community flavors using Calamares, might be covered by this PR:
https://github.com/calamares/calamares/pull/2284
** Also affects: ubuntu-settings
** Also affects: e2fsprogs (Ubuntu Noble)
Importance: Critical
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/2055012
Title:
When I upgraded from 22.04 to
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
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/2045096
Title:
Error in network definition:
Thanks for the additional details!
In this case the output of "resolvectl" after "netplan apply" and after
resume (no "netplan apply") might be useful. In addition to debug-logs
of your systemd-resolved
$ sudo systemctl edit systemd-resolved
Adding:
```
[Service]
I didn't hear about any blocker and in the "Foundation Leadership Sync"
meeting people were overall positive about the change. I'm dropping the
"block-proposed" tag.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: netplan.io (Ubuntu Noble)
Status: In Progress => Fix Committed
--
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/2060311
Title:
Setting "optional:
Extensive testing, from different teams and individuals, has happened in
this bug report and especially in the upstream PR
https://github.com/canonical/netplan/pull/456. This is in addition to
the newly added build-time tests and autopkgtests.
This change affects the
signee: (unassigned) => Lukas Märdian (slyon)
--
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/2060311
Title:
Setting "optional: true" to overcome he timeout "Job
> In the past it was okay to NOT have "optional: true" set for both: encc000
> and encc000.2653 (and I found that logical, since both interfaces are needed
> in a VLAN context).
>
> Knowing now what's missing, I could live with that (even if it's a change in
> behavior).
Interesting.. I
With version ~ppa5 we're now skipping the activation of systemd-
networkd-wait-online.service in case all Netplan interfaces are defined
to be "optional: true", using "ConditionPathIsSymbolicLink=" on
Netplan's s-n-wait-online.service enablement link, that's only set when
we have non-optional
Thanks for testing! There is a failure in your
systemd-networkd-wait-online.service logs:
> systemd-networkd-wait-online.service: Main process exited, code=exited,
> status=1/FAILURE
I fixed this failure in the ~ppa4 version. Could you confirm the failure
is gone with that newer version and
New attempt, that should be transparent to cloud-init, as we're just
creating a /run/systemd/systemd-networkd-wait-
online.service.d/10-netplan.conf override config, specifiying non-
optional interfaces as "/lib/systemd/systemd-networkd-wait-online -i
eth0 -i eth2 -i ..", but keeping the overall
cloud-init seems to order After=sytemd-networkd-wait-online.service AND
Before=network-online.target. So the proposed solution is a no-go.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Are you using NetworkManager in parallel here? Could you please provide
the output of `nmcli dev`? The applications you mention (App Store,
Settings/Online Accounts,...) seem to be Desktop centric and might rely
on NetworkManager functionality for the connectivity checker, which
systemd-networkd
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/2060778
Title:
netplan, multiple dhcp route
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
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/2055333
Title:
netplan.io
Thanks for testing!
Heinrich confirmed offline, that the IPv4 address will come online
asynchronously, as expected for an "optional: true" definition.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Can somebody please confirm that Netplan from this PPA fixes the
problem?
https://launchpad.net/~slyon/+archive/ubuntu/lp2060311/+packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I started some work to help with this here:
https://github.com/canonical/netplan/pull/455
** Changed in: netplan
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.
** Changed in: netplan
Assignee: (unassigned) => Lukas Märdian (slyon)
--
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/2060311
Title:
Setting "option
Here I produced some networkd debug logs on a UC22 system.
** Attachment added: "networkd-debug.log"
https://bugs.launchpad.net/netplan/+bug/2058976/+attachment/5762821/+files/networkd-debug.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I think I can reporudce this on classic...
lxc launch --vm ubuntu-daily:jammy nd-reload
lxc shell nd-reload
root@nd-reload:~# netplan get
network:
version: 2
ethernets:
enp5s0:
dhcp4: true
root@nd-reload:~# networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback
Alfonso, do you have any debug-logs for sytemd-networkd and udev to see
what happens when the interface enters the "failed" state?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Also see bug #2036358
--
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/2060311
Title:
Setting "optional: true" to overcome he timeout "Job systemd-networkd-
wait-online"
** Tags removed: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/2058930
Title:
Missing in i386 Packages index
Status in libvpx package in Ubuntu:
Fix
https://github.com/canonical/netplan/pull/447
** Changed in: netplan
Status: Triaged => Fix Committed
--
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/2055148
> alfonsosanchezbeato: to be clear, the networkctl reload/reconfigure commands
> seem to work, but after 6-8 minutes the state goes back to the one expressed
> by the old .network files
> alfonsosanchezbeato: you can even force the revert to happen sooner with sudo
> udevadm trigger, with that
A fix was deployed (cowboyed) to the autopkgtest-cloud today.
** Changed in: libvpx (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libvpx in Ubuntu.
Actually, this seems to be an issue of the source package not being
pulled from -proposed, as I can install the binaries just fine in a LXD
container:
root@nn:~# dpkg --add-architecture i386
root@nn:~# apt update
[...]
root@nn:~# apt install libvpx9:i386
Reading package lists... Done
Building
** Description changed:
- The new version of libvpx 1.14 seems to be missing in
- http://archive.ubuntu.com/ubuntu/dists/noble-
- proposed/main/binary-i386/Packages.xz, while it's still available in
- http://archive.ubuntu.com/ubuntu/dists/noble-
- proposed/main/binary-i386/Packages.gz.
-
- Grep
Public bug reported:
The new version of libvpx 1.14 seems not to be published to
http://ftpmaster.internal on i386 only.
This leads to the autopkgtest trigger "libvpx/1.14.0-1ubuntu1", not having any
effect on i386:
https://autopkgtest.ubuntu.com/packages/libvpx/noble/i386
** Affects: libvpx
** Tags added: fr-7190
--
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/2055148
Title:
NetworkManager connections with an explicit DoT (DNS over TLS) are not
Could you please provide journalctl debug logs from systemd-resolved, so
we can get more details of what's going on?
e.g. put this into the systemd-resolved override.conf
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug
$ sudo systemctl edit systemd-resolved
$ sudo systemctl restart
We should land a fix keeping the full string in
networkmanager.passthrough and additionaly work on a proper upstream
solution, as suggested by Danilo in comment #4, introducing new settings
as a longer term solution.
** Changed in: netplan
Status: New => Triaged
** Changed in: netplan
Thanks for the heads-up for Netplan! IIUC this will be fixed by a
systemd SRU, so closing it as "Invalid" for Netplan. Please re-open if
you feel there is something to do on our side.
** Changed in: netplan.io (Ubuntu)
Status: New => Invalid
--
You received this bug notification because
This will be part of 1.0-1
** Changed in: netplan.io (Ubuntu)
Status: New => Fix Committed
--
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/2045096
Title:
Public bug reported:
The intention of the previous avahi-autoipd integration was that on a
connection that does have dhcp configured, it will fall back to IPV4LL
if dhcp is unavailable.
This integration was recently dropped (and I think it never worked as intended
in the first place):
I confirmed the patch matches the upstream changes and builds find. I
see the bug description ([Test] section) was updated to mention pairing
of 7 audio and 2 non-audio devices. That pairing test needs to be re-run
with the final binaries, once they are build in the archive, as per the
usual SRU
This patch seems to resolve the situation locally.
For now I'll only go with the changes to tests/integration/base.py,
though. As that should be enough to avoid test failures, while the
service units shouldn't change (besides being re-generated 1:1).
I want to better understand what's going on
This is related:
https://github.com/canonical/netplan/commit/da6f776dd7e33050124fe2990b715db92c1ddee3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite
Public bug reported:
From: https://discourse.ubuntu.com/t/blog-netplan-developer-
diaries/35932/11
Hi all,
NetworkManager connections with an explicit DoT (DNS over TLS)
configuration are not supported with Netplan, but NetworkManager does
feed back the DoT DNS info with server address and
** Changed in: netplan
Status: In Progress => Fix Committed
--
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/2045096
Title:
Error in network definition:
https://launchpad.net/ubuntu/+source/ncurses/6.4+20240113-1ubuntu1
Unsubscribing ~ubuntu-sponsors
** Changed in: ncurses (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ncurses
** Changed in: netplan
Status: Triaged => In Progress
--
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/2045096
Title:
Error in network definition: Invalid
Upstream fix landed in:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7f2a32fa11d580ee65a0458f438018de12b6ae84
** Summary changed:
- FTBFS when rebuilding 1.44 with GCC-14
+ FTBFS when rebuilding 1.44 with glib2-2.79.1
--
You received this bug notification because you
Fixed in https://launchpad.net/ubuntu/+source/network-
manager/1.45.90-1ubuntu1
** Changed in: network-manager (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
** Summary changed:
- FTBFS when rebuilding 1.44
+ FTBFS when rebuilding 1.44 with GCC-14
--
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/2052959
Title:
FTBFS
Public bug reported:
FTBFS due to test failure after an unrelated autopkgtest change was
uploaded (https://launchpad.net/ubuntu/+source/network-
manager/1.44.2-7ubuntu2).
ok 7 /config/warnings
PASS: src/core/tests/config/test-config 7 /config/warnings
#
Looks like this has been fixed in upstream systemd, so there's probably
not a lot that we can do on the Netplan side.
** Changed in: netplan.io (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Please reopen if this is still an issue
** Changed in: netplan.io (Ubuntu)
Status: New => Invalid
--
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/1768088
Title:
Actually, we can further reduce the patch to the removal of
`.generate_mac = true`. This already fixes the issue we observe here.
** Patch added: "lp2037667.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+attachment/5741632/+files/lp2037667.patch
--
You received this
This seems to do the trick using the following Netplan config as a
testcase.
All 3 interfaces (tun[0-2]) are correctly created with their local &
remote properties set:
root@jj-abi:~/systemd# ip link show dev tun0
19: tun0@NONE: mtu 1448 qdisc noqueue state UNKNOWN mode
DEFAULT group default
So after bisecting systemd (v249..v251) on Jammy, this seems to be the
commit that changed behavior for the better:
https://github.com/systemd/systemd/commit/9f0cf80dd007491698978dbfe38158d74c1c9526
It probably needs some backporting for v249.11.
--
You received this bug notification because
** Changed in: systemd (Ubuntu Bionic)
Assignee: Lukas Märdian (slyon) => (unassigned)
--
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/1949089
Title:
systemd rando
We talked to our systemd maintainer inside foundations and also reached
out to upstream system [1], which didn't lead anywhere. We shouldn't
need to bisect systemd-networkd and do a high impact systemd SRU to fix
a regression in a kernel update, where we can pinpoint the exact (small)
git commit.
IMO the wpasupplicant trigger is a red herring, as we see the same
failure on a trigger=system/255... test case:
https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/s390x/n/netplan.io/20240104_111341_511f7@/log.gz
--
You received this bug notification because you are a member of
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite often fails with "systemd units changed without reload" on
s390x
Status in netplan:
Invalid
Another option/idea I'd like to provide here is the migration script
used by NetworkManager [1], to transfer NM keyfiles from
/etc/NetworkManager/system-conncetions/ into /etc/netplan. This script
is automatically run on package upgrade of NetworkManager. I understand
this does not exactly fit the
https://launchpad.net/ubuntu/+source/rsyslog/8.2312.0-2ubuntu1
** Changed in: rsyslog (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
Reducing to "Medium", as I don't think we can hit this situation through
the Netplan-everywhere integration, but manual steps (wrong YAML config)
must be involved in reaching this state.
We're working on a fix here:
https://github.com/canonical/netplan/pull/427
** Changed in: netplan
@vanillaoerba How did you end up in that situation? Did you modify
/etc/netplan/90-NM-X.yaml manually?
Those special values for the MAC address should have been handled by the
networkmanager.passthrough.cloned-mac-address=random setting for you..
--
You received this bug notification
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => Fix Committed
--
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/2046158
Title:
Updating
The RequiredForOnline=no flag can be controlled using Netplan's "optional:
true" setting.
In your specific case (cable not connected) you might also be interested in
Netplan's "ignore-carrier: true" setting, which brings up the interface
regardless.
Please check /etc/netplan/ for those
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Tags added: fr-6121
--
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/2045096
** Tags added: netplan-everywhere
** Changed in: netplan
Status: New => Triaged
** Changed in: netplan
Importance: Undecided => High
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Fixed in v0.107 https://github.com/canonical/netplan/releases/tag/0.107
** Changed in: netplan
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
So if I understand correctly, this does not affect Focal or Bionic.
It also does not affect Mantic or Noble.
We're just hitting this issue on Jammy = systemd v249.11 (and probably
Lunar = systemd v252.5).
Netplan's behavior seems to be correct, here. It writes sensible
configuration for
This should have been fixed upstream as of
https://github.com/canonical/netplan/pull/371 and should be fixed in
Mantic.
Can you still re-produce this issue today?
** Changed in: netplan.io (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are
Netplan is not involved with setting the hostname at all. Marking
invalid for that package.
** Changed in: netplan.io (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Changed in: netplan.io (Ubuntu)
Status: Triaged => Invalid
--
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/2040153
Title:
Network Manager will not remove
** Tags removed: rls-nn-incoming
--
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/2041491
Title:
Provide an option to avoid the yaml NM backend
Status in
Thank you for your thoughtful report!
This change was not just made to be useful in cloud environments, but
also is about unification of network configuration across the different
variants of Ubuntu (Desktop/Server/Core/Cloud/..), to improve the UX for
Ubuntu users. I understand this impacts the
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Tags added: netplan-everywhere
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Tags removed: foundations-todo
--
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/2040153
Title:
Network Manager will not remove Netplan YAMLs when connections are
** Changed in: network-manager (Ubuntu Noble)
Status: Confirmed => In Progress
** Changed in: network-manager (Ubuntu Noble)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Thank you for your investigation. This sounds very related to this
systemd/udev quirk:
https://github.com/canonical/netplan/commit/1413f0e7b8f4d068f817a009d998656de3224370
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Tags removed: block-proposed-mantic
--
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/2040292
Title:
network-manager SRU flags system for restart required but
** Tags added: block-proposed-mantic
--
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/2040292
Title:
network-manager SRU flags system for restart required but also
** Description changed:
+ [ Impact ]
+
+ * During an upgrade (or installation) of the network-manager package, its
debian/network-manager.postinst maintainer script restarts
NetworkManager.service and also requests users to reboot their system.
+ * It requests a reboot, by calling into
** Also affects: network-manager (Ubuntu Mantic)
Importance: Undecided
Status: New
--
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/2040292
Title:
I can confirm this fixes the issue for me, too, using network-manager
1.44.2-1ubuntu1.2 from mantic-proposed.
$ sudo apt install -t mantic-proposed network-manager
[...]
$ LC_ALL=C apt list -i network-manager
Listing... Done
network-manager/mantic-proposed,now 1.44.2-1ubuntu1.2 amd64 [installed]
I staged the changes for 'noble' in the 'ubuntu/master' branch:
https://git.launchpad.net/network-manager/log/
And uploaded the contents of the 'ubuntu-mantic' branch as an SRU:
https://git.launchpad.net/network-manager/log/?h=ubuntu-mantic
https://launchpad.net/ubuntu/mantic/+queue?queue_state=1
** Changed in: netplan.io (Ubuntu Mantic)
Status: Triaged => Invalid
** Changed in: netplan.io (Ubuntu Mantic)
Importance: Critical => Medium
** Changed in: netplan.io (Ubuntu)
Importance: Critical => Medium
--
You received this bug notification because you are a member of Ubuntu
** Tags added: foundations-todo
** Changed in: netplan.io (Ubuntu Mantic)
Status: New => Triaged
** Changed in: network-manager (Ubuntu Mantic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: systemd (Ubuntu)
Status: Invalid => Confirmed
--
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/2037667
Title:
Regression on Jammy's kernel 5.15 when
I tested network-manager 1.44.2-1ubuntu1.1 inside a Mantic LXD
container. Package installation/upgrade and Netplan migration of (valid)
connection profiles worked nicely, according to the "Test Plan":
# Previous version of NM is installed
root@mm-nm-sru:~# dpkg -l network-manager
After restoring git history for bug #2038439 I've now uploaded this SRU
into Mantic, using the `ubuntu-mantic` branch (tag:
ubuntu/1.44.2-1ubuntu1.1):
https://launchpad.net/ubuntu/mantic/+queue?queue_state=1_text=network-
manager
** Description changed:
[ Impact ]
* A failure to query
The bugfix was staged for the "devel" series, as the archive is still
frozen: https://git.launchpad.net/network-manager/log/
I'm uploading this into Mantic: https://git.launchpad.net/network-
manager/log/?h=ubuntu/mantic
** Description changed:
+ [ Impact ]
+
+ * A failure to query nmcli will
Right. The .guests suffix seems to be a problem here. But I don't know
which suffixes are accepted/ignored now and in the future, so I'd avoid
changing file names, as that will probably get us into other issues down
the road (e.g. overwriting an already existing file of that new name).
--
You
Targetted to the Focal series and removed the ~ubuntu-sponsors team, as
the debdiff got already sponsored into Focal and does not affect the
newer series (Jammy+):
https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=apparmor
** Changed in: apparmor (Ubuntu Focal)
Assignee:
** Also affects: apparmor (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2032851
Title:
package apparmor
Thank you! I confirmed that the added distro-patches match the upstream
patches. The feature looks useful, but it's not very common to backport
new features as part of an SRU... So I'll leave that decision to the SRU
team.
In either way, this should probably first be fixed in the current
"devel"
NM can load keyfiles without any suffix, AFAIR. With my proposed patch
it would migrate any keyfiles that are actually loaded by NM, skipping
the other. We should not try to make it load (re-activate) old keyfiles,
which NM isn't loading anymore itself, by renaming them.
--
You received this bug
I created a patch which should fix the issue:
https://code.launchpad.net/~slyon/network-manager/+git/network-
manager/+merge/453731
This also needs SRU
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
Thank you for providing the keyfiles as a reproducer!
I think this line in the migration script [1] is failing here. We need to catch
and handle the error.
> ORIG_NAME=$(nmcli --get-values connection.id con show "$UUID")
The issue is, that this connection profile is apparently very old and
I think this is related to a recent change in behavior in systemd.
It is supposed to be fixed, by implementing the "network-online.target"
specification. Which defines what should be waited for:
https://discourse.ubuntu.com/t/spec-definition-of-an-online-system/27838
But we first need to get
** Summary changed:
-
/usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:_internal_write_connection:nms_keyfile_writer_connection:nms_keyfile_plugin_update_connection
+ NetworkManager crashes when updating wpa-eap connections
--
You received this bug notification because
1 - 100 of 550 matches
Mail list logo
