I think I've found another way to reproduce the problem.
I installed docker in a VM and it created its "docker0" interface. Then
I changed the property ignore-auto-routes for the transient connection
Network Manager created for the docker0 interface.
By doing that, the connection will be turned i
Hi there, have you tried the workaround provided above? It's basically
adding a 3 seconds sleep as you said. It's not ideal but I hope it helps
while we investigate the issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manage
There is definitely a "daemon-reload" happening in the same second when
the problem happens. So it is probably caused by a race condition:
Sep 5 05:55:40 MonacoSIT4 systemd[1]: Reloading.
Sep 5 05:55:40 MonacoSIT4 snapd[3467]: overlord.go:271: Acquiring state lock
file
Sep 5 05:55:40 MonacoSI
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
** Changed in: network-manager (Ubuntu Jammy)
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.lau
Hello,
Can you provide the steps you are performing to reproduce the problem?
It would help a lot if we could easily reproduce the issues from our
side.
Thanks!
** Summary changed:
- [Lenovo Ubuntu 24.04.4 Bug] netplan static IP address assignment use
NetworkManager as renderer would be lost
*** This bug is a duplicate of bug 2089930 ***
https://bugs.launchpad.net/bugs/2089930
It's a duplicate of https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/2089930
** This bug has been marked a duplicate of bug 2089930
NetworManager crashes when modifing connection (ipv4.ign
Hi, I might have found a way to reproduce the problem.
I believe that, at some point, the FortiClient plugging is trying to
create a Network Manager connection for a virtual interface (such as a
dummy device or something like that) that already exists. That is not a
problem with FortiClient though
*** This bug is a duplicate of bug 2089930 ***
https://bugs.launchpad.net/bugs/2089930
** This bug has been marked a duplicate of bug 2089930
NetworManager crashes when modifing connection (ipv4.ignore-auto-routes yes)
--
You received this bug notification because you are a member of Desk
Hi,
If you run 'sudo netplan generate' in your terminal, do you see any
errors?
--
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/2089930
Title:
NetworManager crashes when modif
The first crash could be fixed by handling that case inside libnetplan.
The "ipvX.method" defaults to "disabled" and it will be added to the
"passthrough" section. At some point post-merging we'd need to check if
there are addresses in the list and if "ipvX.method" is in the
passthrough section an
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => Triaged
** Changed in: network-manager (Ubuntu)
Status: New => Triaged
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => Medium
** C
Interesting. According to the discussion [1], it seems to be "fixable"
by changing the OpenSSL configuration to enable older (and insecure)
protocols. Note this is not ideal and might break again in the future.
[1] - https://bbs.archlinux.org/viewtopic.php?pid=2104492#p2104492
--
You received th
This may be related to a WPA security fix present in Oracular. It's
related to PEAP authentication, but I'm not really sure if that is the
root cause.
This is the upstream fix
https://w1.fi/cgit/hostap/commit/?id=8e6485a1bcb0baffdea9e55255a81270b768439c
And the wpa source package changelog from O
Hi Dirk,
Have you successfully connected to a 6GHz network on Oracular (or
Noble)?
I'm trying to understand what is the impact on Netplan and if there is
something that needs to be fixed there.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is
Pull Request https://github.com/canonical/netplan/pull/524
** 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/b
Hi, thank you for reporting this problem.
It's a bug on Netplan. We'll work on a fix for that.
Reproducer:
root@oracular-nm:/etc/netplan# nmcli con add type wifi ssid asdasdadasd
wifi-sec.key-mgmt wpa-psk wifi-sec.psk adadsadadasdasd
802-11-wireless.cloned-mac-address stable-ssid
Error: Faile
We started to see a different error since netplan.io 0.107 landed in
jammy-proposed:
ModuleNotFoundError: No module named 'netplan._netplan_cffi'
https://errors.ubuntu.com/problem/fae8a1deccaf9b2c8aac5d038dfbe8ab9ea9d506
The root cause is probably the same.
Phasing is paused for netplan.io 0.107
That sounds bad.
Does any other command work?
Do you see any zombie () process in "ps aux"?
Does it hang forever? If you wait, let's say, 2 minutes, does it
unblock?
I'm asking this because there is one known issue with netplan that can
cause some commands to hang when the problem happens (and
Thanks for the logs.
It might not be a problem with Network Manager. It's indeed not crashing
nor emitting errors.
I missed the part from your bug description where you said that
"ifconfig" hangs when the problem happens. That points to some issue in
the kernel or driver.
You can also try the co
Also, it would be helpful if you could attach the full journal for
NetworkManager:
journalctl -u NetworkManager > networkmanager.log
Or at least the parts where you see a crash or errors.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
Thank you for confirming the new package fixed the problem for you (and
sorry for the inconvenience ;))
It should land in -updates in the next few days.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
ht
I forgot to mention that you'll need to restart Network Manager after
updating netplan.io.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/2077515
Title:
Network Manager
Hello,
This is related to a regression in netplan.io caused by a security fix.
The fix for this regression is in the -proposed pocket for 24.04 [1].
Can you install the update from -proposed [2] and let us know if it
fixes the problem for you? You might need to delete the connections with
bad na
I can confirm this is an issue, although it's not caused by Network
Manager so I'll go ahead and set it as invalid.
After trying to do a "do-release-upgrade -d" from a brand new
installation of Jammy 22.04.4, gnome-shell crashed and interrupted the
upgrade.
After that, this is what "dpkg --list |
Probably fixed in the last network-manager upload:
debian/tests/control: add Depends: python3-gi for nm_netplan.py (LP:
#2060221)
--
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/
Please refer to https://lists.ubuntu.com/archives/ubuntu-
devel/2024-March/042954.html for more information about the current
state of upgrades.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad
So, I believe the best solution here would be to add options to DNS
addresses, similar to what we do with IP addresses. Something like this
nameservers:
addresses:
- 1.2.3.4:
sni: domain
port: 1234
interface: eth123
- 1.1.1.1
with this we'd fully support both Net
I can confirm the problem. Here is a reproducer:
# nmcli con add ifname dummy0 type dummy ipv4.dns 1.1.1.1#lxd
Error: Failed to add 'dummy-dummy0' connection: Message recipient disconnected
from message bus without replying
This is the crash related to this issue:
Mar 15 09:46:40 noble-vm Netwo
Hi,
If you press ESC when the splash screen shows up, do you see the
console? We need to know where it's getting stuck to better understand
the problem.
If you manage to see the console during boot, can you describe what you
see?
--
You received this bug notification because you are a member of
Hi Martin, thanks so much for your bug report.
I can confirm it's a problem in libnetplan. I created a small fix for it
https://github.com/canonical/netplan/pull/428
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
** Changed in: netplan.io (Ubuntu)
Status: New => Conf
** 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/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask for
IPv6 address
** Also affects: netplan.io (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/2046158
Title:
Updating wireguard-peer.allowed-
Hello, thanks for your bug report.
Can you collect and attach the Network Manager's systemd journal?
You can get it with "journalctl -u NetworkManager > network-manager.log"
It will help us to identify the problem.
Thank you!
** Changed in: network-manager (Ubuntu)
Status: New => Triage
Hi,
I can't find anything wrong in your configuration. And that makes me
wonder if you have another YAML with the same wg0 interface in it. We
recently fixed a bug in Network Manager that was leading to duplication
in the configuration. You might have been affected by this bug when you
upgraded to
Hi Sebastian, thanks for your bug report.
I can see the following error in your syslog.log:
[1700508393.5530] BUG: the profile cannot be stored in keyfile
format without becoming unusable: invalid connection: ipv4.dns: This
property is not allowed for "method=disabled"
What steps did you follow
As far as I can see, the only tests failing now are related to
differences in MAC addresses on veth interfaces. I created an MP to
address these failures. See more details in the related MP.
** Also affects: network-manager (Ubuntu Noble)
Importance: Undecided
Status: Confirmed
** Also
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/network-manager/+git/network-manager/+merge/454594
--
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/2023183
The autopkgtest failures on arm64 are not related to these changes and
it's happening for a while now. So they are not regressions.
I'm running network-manager from proposed on my main machine and the
problem is resolved.
--
You received this bug notification because you are a member of Desktop
** Description changed:
+ [ Impact ]
+
+ Desktop users, or any users with YAML files in /usr/lib/netplan, can't delete
+ Network Manager connections persistently. That means that, when the
connection is
+ deliberately deleted by the user, it will re-appear when the system is
rebooted or
+ netpl
Public bug reported:
When a connection is deleted using any NM facility, libnetplan is
failing to delete the YAML file. Because of that, the connection will be
recreated when "netplan generate" runs again.
This is probably being caused by a combination of two things. First, the
NM's systemd unit
I'm working on the SRU of a couple of fixes for Netplan. This ticket is
being user for the SRU
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039825
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
ht
hm Ok, in this case, the problem was the suffix actually:
root@mantic:/etc/NetworkManager/system-connections# nmcli con load
/etc/NetworkManager/system-connections/UPTOWN.guests
Could not load file '/etc/NetworkManager/system-connections/UPTOWN.guests'
root@mantic:/etc/NetworkManager/system-conne
Is the only problem the filename extension? Renaming it to
UPTOWN.guests.nmconnection makes it loadable.
Should we still try to load these files by renaming them first? Or,
should we iterate over the *.nmconnection files only instead of *?
--
You received this bug notification because you are a
Hello, thank you for reporting that.
May I ask you to attach the full NetworkManager journal so we can
understand better what is happening?
You can collect it with the command below:
journalctl -u NetworkManager > network-manager.log
It would be very helpful. Thanks!
--
You received this bug
They might (likely to?) be related to libnetplan. I'm looking into it.
--
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:
/usr/sbin/NetworkManager:6:g_assertion_me
** Changed in: netplan.io (Ubuntu Mantic)
Status: New => 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/2033391
Title:
Some Netplan-related autopkgtests ar
The patch helped with nm.py and nm_netplan.py tests but the ones that
require building kernel modules are still failing due to the gcc
version.
1749s autopkgtest [00:14:05]: summary
1749s wpa-dhclient PASS
1749s nm.pyPASS
1749s killswitches-no-urfkill F
Both tests that require building a kernel module are failing due to the
new default gcc
794s autopkgtest [10:41:29]: test killswitches-no-urfkill:
[---
794s make -C /lib/modules/6.3.0-7-generic/build
KBUILD_SRC=/lib/modules/6.3.0-7-generic/build
M=/tmp/autopkgtest.6Iru72/bui
I'm running some tests with the linked MP.
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/network-manager/+git/network-manager/+merge/450220
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubu
Well, actually, there are tests from nm.py failing for the same
reason...
--
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/2033391
Title:
Some Netplan-related autopkgtests are f
Public bug reported:
The root cause appears to be NM not being ready yet when the test
starts.
# /usr/bin/python3
/tmp/autopkgtest.kW7u4i/build.K7E/src/debian/tests/nm_netplan.py
test_nmcli_add_device_and_change_it
(__main__.TestNetplan.test_nmcli_add_device_and_change_it)
Uses the nmcli to add
Might be related to https://gitlab.gnome.org/GNOME/glib/-/issues/2927
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2927
https://gitlab.gnome.org/GNOME/glib/-/issues/2927
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gli
So,
the problem appears to be the value of "cloned-mac-address". Netplan
only accepts a MAC address, but Network Manager also supports some
special settings ("preserve", "permanent", "random" and "stable").
I prepared a fix for that https://github.com/canonical/netplan/pull/376
** Also affects:
Thank for your bug report.
Based on the core dump you provided, the problem seems to be related to
libnetplan.
Can you collect the NetworkManager's systemd journal and attach to the
ticket, please?
journalctl -u NetworkManager > network-manager.log
Thanks!
--
You received this bug notificatio
Based on the files attached to the bug report, the Wifi interface is not
present in the system.
I can see the system tried to initialize it:
jún 20 08:37:40 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi
:02:00.0: retry init count 0
jún 20 08:37:40 peter-ROG-Zephyrus-G14-GA401IV-GA40
After some more digging, turns out it's not a problem with Netplan.
Although, the problem will manifest depending on how Netplan generates
the configuration for Network Manager.
When selecting the option to store the private key in the KDE wallet
agent, the option "private-key-flags=1" will be add
** 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/2024661
Title:
Unable to configure Wireguard connection at
Ok, I think I see what the problem is.
The GUI tool will, by default, not add the private key to the
.nmconnection file. It will use some existing key chain agent to do
that.
We will need to take this into account when parsing the keyfile in
Netplan.
** Changed in: netplan.io (Ubuntu)
Importa
Thanks for your bug report.
May I ask you to attach the NetworkManager's journal (journalctl -u
NetworkManager) to the ticket, please?
I can't reproduce it in Ubuntu Mantic using the NM GUI...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
Thanks for your bug report.
This problem seems to be caused by the netplan migration logic in the
postinst script. I'm looking into it.
--
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
Thanks, Julian.
This behavior was introduced by the netplan integration where we create
a backup of the existing network manager connections. I'll look for a
better place to store the backups.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
After taking another look at this I noticed that the function where we
create the Netplan YAML is called when the connection is created AND
when the connection is going down as though it was being updated.
The first time it's called the parameters is_volatile, is_nm_generated
and is_external are a
Public bug reported:
I enabled lunar-proposed today (with APT::Default-Release "lunar-
proposed";) and got the error below during update:
Preparing to unpack .../39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ...
Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ...
dpkg: err
The same problem happens if you spin up an OpenVPN server and kill it.
An yaml file will be created for the tun interface used by the server.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpa
Digging a bit more on that, the problem might be the font build system.
The most recent fonts-dejavu-extra package is shared across Jammy,
Kinetic and Lunar and it appears to be broken on all of them.
Rebuilding the package on Kinetic seems to be enough to fix the problem.
But that's not true for
These fonts are working fine in Focal (fonts-dejavu-
extra_2.37-1_all.deb) and broken in Jammy, Kinetic and Lunar (fonts-
dejavu-extra_2.37-2build1_all.deb).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-font-viewer in Ubuntu.
htt
It turns out the font files in our package are probably corrupt. I
tested with the files from the original source [0] and the problem
doesn't happen.
I also replaced the broken ones with the original ones, cleaned my font
cache and the problem appears to be gone.
Will try to find out when it happ
I just noticed that this font (and many others) are marked as
"experimental" even in the most recent version of the source [0] [1]. So
it might be broken in some scenarios.
I opened an issue to clarify if that might be the case [2].
Meanwhile, if you change your XFCE font settings like mentioned
Not sure where the problem is exactly but it can be reproduced like Juha
suggested.
On Xubuntu 22.04 if you go to Settings -> Appearance -> Fonts and set
"Hinting" to "Medium" or "Full" and have
FREETYPE_PROPERTIES="truetype:interpreter-version=35", all the
DejaVuSerif...Italic fonts appear to bre
69 matches
Mail list logo
