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.
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
Thanks! The rebased patches do still apply cleanly and build fine.
- I fixed the Mantic debdiff SRU version "2:21.1.7-3ubuntu3" ->
"2:21.1.7-3ubuntu2.10"
- I fixed the Jammy debdiff d/changelog to reference this bug report
Re-sponsoring for Mantic & Jammy and unsubcribing ~ubuntu-sponsors.
--
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager 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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2045096
Title:
Error in network definition: Invalid MAC
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/2028054
Title:
[MIR] python-rlpycairo
Status in hplip package in Ubuntu:
Confirmed
Status in
LGTM and matches upstream changes. Build OK. We'd also want this for
Mantic, before backporting to Jammy. The patch is simple enough that I
did that for you!
- Noble: https://launchpad.net/ubuntu/+source/xorg-server/2:21.1.11-2ubuntu2
- Mantic:
** Also affects: xorg-server (Ubuntu Mantic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2056331
Title:
[SRU] fix suspend/resume
** Tags removed: rls-nn-incoming
--
You received this bug notification because you are a member of Desktop
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 Released
Bug
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2055148
Title:
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 Desktop
Packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/2058930
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 Desktop
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
supported with
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
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2045096
Title:
Error in
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 Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/2048388
Title:
Test suite often fails
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2045096
Title:
Error in network definition: Invalid MAC
** Changed in: netplan
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2045096
Title:
Error in network definition: Invalid MAC address
** Also affects: wsl-pro-service (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: wsl-pro-service (Ubuntu Noble)
Importance: Undecided
Assignee: Lukas Märdian (slyon)
Status: New
** Also affects: wsl-pro-service (Ubuntu Focal)
Importance: Undecided
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** 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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2052959
Title:
FTBFS when rebuilding
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
#
(In reply to Jacob Garby from comment #816)
> (In reply to Lukas from comment #814)
> > (In reply to Jacob Garby from comment #813)
> > > I have a "Lenovo Legion Slim 7i 16", and several days ago, out of
> nowhere,
> > > the speaker started working
(In reply to Jacob Garby from comment #813)
> I have a "Lenovo Legion Slim 7i 16", and several days ago, out of nowhere,
> the speaker started working. I have no idea how -- I did not change anything
> manually. I suspect it's a new kernel version that did it.
>
> I'm on Arch Linux, and I can't
Hey, I have a Lenovo Yoga 7 16IAP7 with Fedora Workstation 39 installed.
Kernel Verion: Linux 6.6.11-200.fc39.x86_64
alsa-lib version: alsa-lib-1.2.10-3.fc39.x86_64
I installed alsa-tools and went into hdajackretask to see what is going
on. Then I noticed that my System is telling me that I have
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 Desktop
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
Status in
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
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158
Title:
Updating wireguard-peer.allowed-ips
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Tags added: fr-6121
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2045096
Title:
Error
** 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 Desktop
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
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
** Changed in: netplan.io (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2040153
Title:
Network Manager will not remove Netplan
** Tags removed: rls-nn-incoming
--
You received this bug notification because you are a member of Desktop
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 netplan.io package 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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Desktop
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
deleted
** 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 Desktop
Packages, which is subs
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 Desktop
Packages, which is subscribed to network-manager
** Tags removed: block-proposed-mantic
--
You received this bug notification because you are a member of Desktop
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
** Tags added: block-proposed-mantic
--
You received this bug notification because you are a member of Desktop
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
restarted
** 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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2040292
Title:
network-manager SRU
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 Desktop
** 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 Desktop
Packages, which is subscribed to
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
Thank you for this suggestion.
Even though bumping the epoch is a very big hammer, it sounds very sensible to
me.
The patch is looking mostly good, too.
But I wonder if we should rather change the version number to
"2:1snap1-0ubuntu1", in order to use a similar format as we have on
Firefox (LP:
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
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
** 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
Reproducer:
nmcli con add type wifi ifname wlan0 ssid asdasd wifi-sec.key-mgmt wpa-eap
802-1x.eap leap 802-1x.identity username 802-1x.password
The crash (SIGABRT) happens in NetworkManager's Netplan integration patch,
because of running into a "nm_assert_not_reached()" call. This
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2038811
Title:
** Changed in: python-rlpycairo (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/2028054
Title:
[MIR] python-rlpycairo
Status in hplip package
Thanks Till, for the detailed analysis in comment #3!
IMO src:hplip should be adopted accordingly, to avoid those new MIR
dependencies, as they don't seem to be necessary. Especially, as we're
moving to a CUPS snap based stack eventually.
What do Desktop people think about that?
We might want
** Changed in: python-reportlab (Ubuntu)
Status: Fix Released => Incomplete
** Changed in: python-reportlab (Ubuntu)
Assignee: Ubuntu Foundations Bugs (foundations-bugs) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2012902
Title:
netplan plugin: generated NM config when using globbing will be used
for only
Ok, we're not doing the MIR then and waiting for the desktop team to
demote the printing stack.
** Changed in: python-rlpycairo (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in
Public bug reported:
python-rlpycairo is a new dependency of python-reportlab (currently
owned by Foundations).
The only consumer of python-reportlab is hplip (owned by Desktop),
apparently it needs it for scanning: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=651240
$ reverse-depends
Thank you! The Netplan build seems to be fixed now. Removing the tag.
** Tags removed: block-proposed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2026826
Title:
glib2.0 (2.77.0 )
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3047
https://gitlab.gnome.org/GNOME/glib/-/issues/3047
** Also affects: glib via
https://gitlab.gnome.org/GNOME/glib/-/issues/3047
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
** Description changed:
Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
mantic-proposed.
See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3
When I downgrade glib in my sbuild environment, everything works as
expected:
$ apt install
I'm tagging this block-proposed to avoid this broken GLib to move into
mantic-release.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2026826
Title:
Public bug reported:
Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
mantic-proposed.
See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3
When I downgrade glib in my sbuild environment, everything works as
expected:
$ apt install libglib2.0-0=2.76.3-1ubuntu1
Merged upstream. Will be part of the next Netplan release.
** Also affects: netplan
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Summary changed:
- error when setting up after upgrading
+ libnetplan integration breaks "cloned-mac-address" special values
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://github.com/canonical/netplan/pull/371
** Changed in: netplan.io (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2024661
** Tags added: netplan-everywhere
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2024661
Thanks Simon, those are two good catches!
The "file" package/command is seeded in the Ubuntu desktop flavours:
$ seeded-in-ubuntu file
file (from file) is seeded in:
edubuntu: daily-live
kubuntu: daily-live
lubuntu: daily-live
ubuntu-budgie: daily-legacy, daily-live
ubuntu-mate:
Thank you @seth-arnold! I've updated the affected packages of this bug
and (bug #2019939) accordingly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2019940
Title:
Directly
** Also affects: scap-security-guide (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-user-docs in Ubuntu.
https://bugs.launchpad.net/bugs/2019939
Title:
Outdated documentation
cruft is not part of Ubuntu anymore (got dropped post Kinetic)
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: cruft (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cruft (Ubuntu)
Status: New => Won't Fix
--
You
** Changed in: netplan.io (Ubuntu)
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2019940
Title:
Directly manipulating NetworkManager
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2010561
Title:
The Netplan Everywhere
We should run the same query on the Ubuntu archive, too. The security
team (sespiros / sarnold) might be able to help with this in the future.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** Tags added: rls-mm-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-user-docs in Ubuntu.
https://bugs.launchpad.net/bugs/2019939
Title:
Outdated documentation about NetworkManager keyfiles
Status in debian-handbook
netcfg is not part of Ubuntu anymore (got dropped post Focal)
** Changed in: netcfg (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Netplan deals with keyfiles in /run/NetworkManager/system-connections
not /etc/...
** Changed in: netplan.io (Ubuntu)
Status: New => Won't Fix
** Tags added: rls-mm-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
The affected packages can manipulate NetworkManager keyfiles directly on
disk, which might not be appropriate anymore on Ubuntu, since the
Netplan integration was enabled in NetworkManager (starting with
Mantic), migrating any keyfile configuration from
Public bug reported:
The affected packages contain documentation or examples about
NetworkManager keyfiles, which might not be appropriate anymore on
Ubuntu, since the Netplan integration was enabled in NetworkManager
(starting with Mantic), migrating any keyfile configuration from
Merged. This fix should land in the "Netplan Everywhere" PPA today (for
Lunar):
https://launchpad.net/~canonical-
foundations/+archive/ubuntu/networkmanager-netplan
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: netplan
Status: Triaged
First part is fixed in https://git.launchpad.net/network-
manager/commit/?h=netplan/lunar-gu=ed1837f
Second part is up for review in:
https://code.launchpad.net/~slyon/network-manager/+git/network-
manager/+merge/440401
--
You received this bug notification because you are a member of Desktop
** Changed in: network-manager (Ubuntu)
Status: New => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-m
** Also affects: netplan
Importance: Undecided
Status: New
** Changed in: netplan
Status: New => Triaged
** Changed in: netplan
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
The issue seems to be related to
https://networkmanager.dev/blog/networkmanager-1-42/#managing-the-
loopback-interface
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2009543
1 - 100 of 369 matches
Mail list logo
