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 Ubuntu
Touch seeded packages, which is subscribed to
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
Public bug reported:
[placeholder]
** Affects: usbmuxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to usbmuxd in Ubuntu.
https://bugs.launchpad.net/bugs/2034539
** Description changed:
- [placeholder]
+ The installation of this package as part of the upgrade process from
+ Lunar to Mantic is triggering an issue in Netplan
+ https://bugs.launchpad.net/netplan/+bug/1999178
+
+ This package will install a udev .rules file referring to a user that
+ will be
Running a "do-release-upgrade -d --allow-third-party" with this PPA (set
to Mantic) [1] works around the issue when upgrading a clean Lunar to
Mantic.
[1] - https://launchpad.net/~danilogondolfo/+archive/ubuntu/usbmuxd
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
The installation of this package as part of the upgrade process from
- Lunar to Mantic is triggering an issue in Netplan
+ Lunar to Mantic (it's already present in Desktop images so it's not a
+ problem there apparently) is triggering an issue in Netplan
Well, actually, there are tests from nm.py failing for the same
reason...
--
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/2033391
Title:
Some Netplan-related
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
** Changed in: netplan.io (Ubuntu Mantic)
Status: New => 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.
https://bugs.launchpad.net/bugs/2033391
Title:
Some Netplan-related
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'
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
Public bug reported:
tracking bug
** Affects: netcat-openbsd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/netcat-openbsd/+git/netcat-openbsd/+merge/454972
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/curl/+git/curl/+merge/455006
--
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/2039798
** 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 Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
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
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 Ubuntu
** Description changed:
The installation of this package as part of the upgrade process from
Lunar to Mantic (it's already present in Desktop images so it's not a
problem there apparently) is triggering an issue in Netplan
https://bugs.launchpad.net/netplan/+bug/1999178
This package
They might (likely to?) be related to libnetplan. I'm looking into it.
--
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/2038811
Title:
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 Ubuntu
Touch seeded packages, which is subscribed to network-manager
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
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
** 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
+
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
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
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
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
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 Ubuntu
Touch seeded packages, which is subscribed to fonts-dejavu in
More cases where the same linker flags caused issues
https://bugs.launchpad.net/ubuntu/+source/openblas/+bug/1860601
https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1898006
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Note: when testing this package with autopkgtest (or sbuild) locally,
you need to remove the .git directory (if there is one) or the build
will fail. One of the make files will detect the directory exists and
set the environment variable DYNAMIC to no. Because of that, static
binaries will be
Public bug reported:
Ubuntu will include -Wl,-Bsymbolic-functions in the build flags by
default. This option seems to break libcap2.
One of the autopkgtests that is supposed to prevent an exploitation
instance using capabilities fails:
https://autopkgtest.ubuntu.com/results/autopkgtest-
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 Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
More specifically, this test [1] is failing. It uses clone() to create a
process in a new user namespace and apparently it should fail.
I can't reproduce it with a LXD arhmf container on my own environment.
All the tests pass.
[1] -
As /etc/resolv.conf is a symlink, is it possible that the nameservers
received via DHCP in the early boot stages are never stored in
/etc/resolv.conf?
cloud-init tries to resolve that address before resolved is started and
there is nothing at /etc/resolv.conf.
Does that make sense?
--
You
It doesn't seem to be caused by a race between networkd and
NetworkManager.
I reproduced the issue with qemu here and I see the name resolution
failure happening few seconds before NetworkManager started.
>From /var/log/cloud-init.log:
2023-03-09 19:17:58,443 - util.py[DEBUG]: Getting data from
** Changed in: netplan
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/2008952
Title:
DNS failure while trying to fetch user-data
Status in
** Attachment added: "systemd_journal.txt"
https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654392/+files/systemd_journal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Attachment added: "timeline.txt"
https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654394/+files/timeline.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I attached some logs that might be useful. After checking it again I
realized that the syslog timestamps are a little off when compared to
the systemd journal.
As shown in the timeline.txt (attached), cloud-init and systemd-resolved
are starting at the same time.
So the name resolution might not
** Attachment added: "cloud-init.log"
https://bugs.launchpad.net/cloud-init/+bug/2008952/+attachment/5654393/+files/cloud-init.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
PPA available at
https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo
** Affects: sudo (Ubuntu)
Importance: Undecided
Status: New
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/437505
--
** Attachment added: "sudo autopkgtests"
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+attachment/5648890/+files/autopkgtests.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
** Summary changed:
- Please merge 1.9.12p2-1 into lunar
+ Please merge 1.9.13p1-1 into lunar
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/437587
--
You received this bug notification because you are a member of Ubuntu
Touch
Hi Marc, thanks a lot for taking a look at this. I misunderstood how the
changelog must be constructed.
I believe the Build-Conflicts can just be dropped as the problem with
fakeroot was fixed (LP: #1915250) and sudo doesn't require root to be
built anymore (and the file permissions seem to be
Autopkgtests are passing (tested on ppc64 and amd64)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2007698
Title:
Please merge 1.9.12p2-1 into lunar
Status in sudo package
Public bug reported:
PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/curl/
** Affects: curl (Ubuntu)
Importance: Undecided
Status: New
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/curl/+git/curl/+merge/437707
--
You received
The problem is reproducible on Focal (kernel 5.4) in an armhf LXD
container. The armhf architecture seems to be the only one using hosts
with kernel 5.4. I believe the best approach is to skip only the test
that is failing rather than the entire test script. So we will need to
patch
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/libcap2/+git/libcap2/+merge/436832
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
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:
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
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:
Public bug reported:
[placeholder]
** Affects: netcat-openbsd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu.
** Changed in: sudo (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2020470
Title:
Please merge 1.9.13p3-1 into mantic
** Changed in: sudo (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2007698
Title:
Please merge 1.9.13p1-1 into lunar
Public bug reported:
[placeholder]
** Affects: sudo (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2025655
Title:
Public bug reported:
Autopkgtests are consistently failing on s390x.
More specifically, the test 04-getroot-sssd is failing.
The reason is not evident because the stderr is being redirected to
/dev/null. After testing a PPA without the redirection, I was able to
see the error below:
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 Ubuntu
Touch seeded packages, which is
** Description changed:
- [placeholder]
+
+ PPA: https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo2
+
+ Autopkgtests https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-
+ danilogondolfo-sudo2/mantic/s390x/s/sudo/20230705_144943_c8ec0@/log.gz
+
+ This merge includes a workaround
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/446052
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2025655
Thank you, Lucas. I split that merge commit.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu.
https://bugs.launchpad.net/bugs/2025666
Title:
Please merge 1.225-1 into mantic
Status in
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/netcat-openbsd/+git/netcat-openbsd/+merge/445940
** Description changed:
- [placeholder]
+ PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/netcat-openbsd
+
+ Autopkgtest
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
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 Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
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 Ubuntu
Touch seeded packages, which
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/443422
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2020470
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/libcap2/+git/libcap2/+merge/443409
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
Public bug reported:
tracking bug
** Affects: sudo (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2020470
Title:
PPA
https://launchpad.net/~danilogondolfo/+archive/ubuntu/libcap2/+packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020460
Title:
Please merge 1:2.66-4 into
Public bug reported:
tracking bug
** Affects: libcap2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
https://bugs.launchpad.net/bugs/2020460
** Attachment added: "Autopkgtests logs for armhf"
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+attachment/5675001/+files/libcap2_armhf_log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in
** Attachment added: "Autopkgtests logs for amd64"
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+attachment/5675000/+files/libcap2_amd64_log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in
** Attachment added: "Autopkgtest logs for amd64"
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2020470/+attachment/5675003/+files/autopkgtest_logs.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
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)
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 Ubuntu
Touch seeded packages, which
** 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/2024661
Title:
Unable to configure Wireguard
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
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
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
** Tags added: 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/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask for
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 =>
** Also affects: netplan.io (Ubuntu)
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/2046158
Title:
Updating
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/curl/+git/curl/+merge/457830
--
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/2045886
The problem seems to be fixed in 8.5.0-2 by
https://github.com/curl/curl/commit/fa6e123929de94064f1b1cb135f30b0a945ba399
--
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/2045886
** Summary changed:
- Please merge 8.5.0-1 into noble
+ Please merge 8.5.0-2 into noble
--
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/2045886
Title:
Please merge 8.5.0-2
** Tags added: foundations-todo
--
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/1746419
Title:
bond parameters are not changed by 'netplan apply'
Status in netplan:
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 =>
Public bug reported:
tracking bug
** Affects: curl (Ubuntu)
Importance: Undecided
Status: New
--
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/2045886
Title:
hmm an autopkgtest is segfaulting (also in Debian)
2813s ldap_send_server_request
2813s ## Something failed, gathering logs
2813s
2813s ## syslog
2813s Segmentation fault (core dumped)
...
2813s curl-ldapi-test FAIL non-zero exit status 139
--
You received this bug notification because
Public bug reported:
tracking bug
** Affects: sudo (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2051576
Title:
** Merge proposal linked:
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/459624
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2051576
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
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
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
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
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 Ubuntu
Touch seeded packages, which is subscribed to audit in Ubuntu.
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 Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
To get you configuration working you need to remove the match and set-
name stanzas (which were never required really). Using the definition ID
as the interface name (the "lo" inside "ethernets") is enough to
configure an interface using its name. And by removing that it will work
on Jammy.
As
I just updated and rebooted but I'm also still seeing the same problem:
Failed to backup /etc/group: Operation not supported. It's reproducible
with "apt install tomcat10".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Oh the new kernel wasn't built with the new zfs-dkms =/
II: dkms-build downloading zfs (zfs-dkms_2.2.2-0ubuntu7_all.deb)
II: fetching
https://launchpad.net/ubuntu/+archive/primary/+files/zfs-dkms_2.2.2-0ubuntu7_all.deb
II: fixing
1 - 100 of 102 matches
Mail list logo
