[Touch-packages] [Bug 2058976] Re: Configuration files for networkd are created when NetworkManager is the default renderer
I have found another case where reloading networkd will not be enough to
apply the configuration. I'm not sure if it's the same root cause but it
looks similar so I'll use this ticket to document it.
The scenario looks like this (it's all done in a LXD VM running
Oracular):
1) Start with the default ethernet configuration
2) Add the ethernet interface to a bond and apply
3) Remove the bond from the configuration and apply
4) Add the interface back to the bond and apply
5) At this point the configuration will not be applied anymore and one needs to
either restart networkd or delete the bond.
It smells like some state is not being dropped and causing the issue.
Details on how to reproduce:
Start with this config:
network:
version: 2
ethernets:
enp5s0:
dhcp4: true
Add a bond:
network:
version: 2
ethernets:
enp5s0: {}
bonds:
bond0:
dhcp4: true
interfaces:
- enp5s0
Apply the config and observe it worked as intended.
Now restore the initial config and netplan apply again:
network:
version: 2
ethernets:
enp5s0:
dhcp4: true
At this point enp4s0 will get an IP address and the bond0 interface will
be left behind as netplan apply will not delete it.
Now add the bond back and netplan apply again:
network:
version: 2
ethernets:
enp5s0: {}
bonds:
bond0:
dhcp4: true
interfaces:
- enp5s0
At this point the configuration will not by applied anymore.
The bond state will get stuck at "State: no-carrier (configuring)".
One needs to either delete the bond or restart networkd to make it work again.
--
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/2058976
Title:
Configuration files for networkd are created when NetworkManager is
the default renderer
Status in Netplan:
New
Status in systemd package in Ubuntu:
New
Bug description:
This is happening in a UC image created with a gadget that disables
console-conf:
$ ubuntu-image snap --snap=network-manager=22 --snap pc_22.snap
The snaps are:
$ snap list
Name Version RevTracking Publisher Notes
core22 202403211344 latest/edge canonical✓ base
network-manager 1.36.6-987622/stablecanonical✓ -
pc 22-0.3 x1 --
gadget
pc-kernel5.15.0-102.112.1+1 1731 22/beta canonical✓
kernel
snapd2.62+git2017.g1afc063e 21490 latest/edge canonical✓ snapd
On first boot, the content in /etc/netplan is:
ubuntu@ubuntu:~$ cat /etc/netplan/00-default-nm-renderer.yaml
network:
renderer: NetworkManager
ubuntu@ubuntu:~$ cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
ens3:
dhcp4: true
match:
macaddress: '52:54:00:12:34:56'
set-name: ens3
version: 2
But we have a configuration file for systemd-networkd that should not be
there:
ubuntu@ubuntu:~$ cat /run/systemd/network/10-netplan-ens3.link
[Match]
PermanentMACAddress=52:54:00:12:34:56
[Link]
Name=ens3
WakeOnLan=off
ubuntu@ubuntu:~$ networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 ens3 etherroutableconfigured
While having to:
ubuntu@ubuntu:~$ sudo cat
/run/NetworkManager/system-connections/netplan-ens3.nmconnection
[connection]
id=netplan-ens3
type=ethernet
interface-name=ens3
[ethernet]
wake-on-lan=0
[ipv4]
method=auto
[ipv6]
method=ignore
ubuntu@ubuntu:~$ nmcli c
NAME UUID TYPE DEVICE
netplan-ens3 bec3d02a-c9e5-3283-92ab-ee43a4246c85 ethernet ens3
ubuntu@ubuntu:~$ nmcli d
DEVICE TYPE STATE CONNECTION
ens3ethernet connected netplan-ens3
lo loopback unmanaged --
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2058976/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
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 | grep systemd" looks like: ii dbus-user-session 1.14.10-4ubuntu4 amd64simple interprocess messaging system (systemd --user integration) ii gnome-logs42.0-1 amd64viewer for the systemd journal ii libnss-systemd:amd64 249.11-0ubuntu3.12 amd64nss module providing dynamic user and group name resolution ii libpam-systemd:amd64 249.11-0ubuntu3.12 amd64system and service manager - PAM module ii libsystemd-shared:amd64 255.4-1ubuntu8 amd64systemd shared private library ii libsystemd0:amd64 255.4-1ubuntu8 amd64systemd utility library ii networkd-dispatcher 2.1-2ubuntu0.22.04.2 all Dispatcher service for systemd-networkd connection status changes ii python3-systemd 235-1build4 amd64Python 3 bindings for systemd ii systemd 255.4-1ubuntu8 amd64system and service manager ii systemd-dev 255.4-1ubuntu8 all systemd development files ii systemd-hwe-hwdb 249.11.5 all udev rules for hardware enablement (HWE) ii systemd-oomd 249.11-0ubuntu3.12 amd64Userspace out-of-memory (OOM) killer ii systemd-sysv 249.11-0ubuntu3.12 amd64system and service manager - SysV links ii systemd-timesyncd 255.4-1ubuntu8 amd64minimalistic service to synchronize local time with NTP servers and /etc/resolv.conf is a broken link as systemd-resolved is not installed and /run/systemd/resolve doesn't exist: /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf ** Changed in: network-manager (Ubuntu) Status: Confirmed => 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/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Confirmed Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half hour to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified]
[Touch-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Kernel -31 fixed the problem for me. Thanks!
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Released
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
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
https://launchpadlibrarian.net/718392332/zfs-dkms_2.2.2-0ubuntu7_all.deb
II: following
http://launchpadlibrarian.net/718392332/zfs-dkms_2.2.2-0ubuntu7_all.deb
II: dkms-build-configure dkms-build-configure--zfs found, executing
--
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/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2058179
Title:
Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
Status in Native ZFS for Linux:
Fix Released
Status in systemd package in Ubuntu:
Fix Committed
Status in zfs-linux package in Ubuntu:
Fix Released
Status in systemd source package in Noble:
Fix Committed
Status in zfs-linux source package in Noble:
Fix Released
Bug description:
As per https://github.com/openzfs/zfs/issues/15930
ZFS and kernel 6.8 seem to throw EOPNOTSUPP on calling
copy_file_range, breaking a multitude of applications.
Upcoming noble (24.04) appears to currently include kernel 6.8 and ZFS
2.2.2.
One notable issue is when running Root on ZFS: systemd-sysusers will
always fail to create users/groups with the error "Failed to backup
/etc/{group,passwd}: Operation not supported" due to the call to
copy_file_range.
To manage notifications about this bug go to:
https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055333] Re: netplan.io 0.106.1-7ubuntu0.22.04.2 fails to manage additional loopback addresses on Ubuntu 2204 Jammy
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 you noticed, there seem to be some change in behavior in newer versions of systemd. The configuration that uses match.macaddress I wouldn't expect to work actually works on Noble. Although, I've found this by accident: --- Apr 15 14:14:58 noble (udev-worker)[382]: dummy123: Could not set WakeOnLan to off, ignoring: Operation not supported Apr 15 14:14:58 noble (udev-worker)[382]: dummy123: Failed to rename network interface 3 from 'dummy123' to 'lo': File exists Apr 15 14:14:58 noble (udev-worker)[382]: dummy123: Failed to process device, ignoring: File exists --- I also have a dummy interface in my configuration and it doesn't have a permanent mac address as well. Although, udev apparently tried to apply the set-name from ethernets.lo to this interface as if the match.macaddress matched both. -- 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 0.106.1-7ubuntu0.22.04.2 fails to manage additional loopback addresses on Ubuntu 2204 Jammy Status in netplan.io package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Attempting to add additional loopback addresses to 22.04 jammy fails with the latest netplan.io package. Previous versions (.104) work correctly as well as newer versions (0.107) in 23.10 mantic. Behavior does not change if default loopback addresses are or are not present in the address list (127.0.0.1/8 and ::1/128). Netplan is configured via cloudinit in our environment but for simplicity I'll provide output from a manual configuration on a test vm in virtual box. root@ubuntu-jammy-test:~# cat /etc/netplan/10-loopback.yaml network: version: 2 ethernets: lo: addresses: - 10.10.10.10/32 match: macaddress: 00:00:00:00:00:00 set-name: lo root@ubuntu-jammy-test:~# netplan apply WARNING:root:Cannot call Open vSwitch: ovsdb-server.service is not running. root@ubuntu-jammy-test:~# ip addr show lo 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever root@ubuntu-jammy-test:~# networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 enp0s3 etherroutableconfigured 2 links listed. root@ubuntu-jammy-test:~# apt-get install -y --allow-downgrades netplan.io=0.104-0ubuntu2 libnetplan0=0.104-0ubuntu2 Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: network-manager | wpasupplicant openvswitch-switch The following packages will be DOWNGRADED: libnetplan0 netplan.io 0 upgraded, 0 newly installed, 2 downgraded, 0 to remove and 0 not upgraded. Need to get 0 B/181 kB of archives. After this operation, 163 kB disk space will be freed. dpkg: warning: downgrading netplan.io from 0.106.1-7ubuntu0.22.04.2 to 0.104-0ubuntu2 (Reading database ... 69845 files and directories currently installed.) Preparing to unpack .../netplan.io_0.104-0ubuntu2_amd64.deb ... Unpacking netplan.io (0.104-0ubuntu2) over (0.106.1-7ubuntu0.22.04.2) ... dpkg: warning: downgrading libnetplan0:amd64 from 0.106.1-7ubuntu0.22.04.2 to 0.104-0ubuntu2 Preparing to unpack .../libnetplan0_0.104-0ubuntu2_amd64.deb ... Unpacking libnetplan0:amd64 (0.104-0ubuntu2) over (0.106.1-7ubuntu0.22.04.2) ... Setting up libnetplan0:amd64 (0.104-0ubuntu2) ... Setting up netplan.io (0.104-0ubuntu2) ... Processing triggers for libc-bin (2.35-0ubuntu3.6) ... Processing triggers for man-db (2.10.2-1) ... Processing triggers for dbus (1.12.20-2ubuntu4.1) ... Scanning processes... Scanning linux images... Running kernel seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on
[Touch-packages] [Bug 2060241] Re: prosposed migration audit 1:3.1.2-2.1build1 vs network-manager 1.46.0-1ubuntu1
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. https://bugs.launchpad.net/bugs/2060241 Title: prosposed migration audit 1:3.1.2-2.1build1 vs network-manager 1.46.0-1ubuntu1 Status in audit package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: The autopkgest for network-manager fail due to the missing module dependency: 3988s autopkgtest [18:31:02]: test nm_netplan.py: [--- 3988s Traceback (most recent call last): 3988s File "/tmp/autopkgtest.Q1jKoU/build.9D4/src/debian/tests/nm_netplan.py", line 18, in 3988s import gi 3988s ModuleNotFoundError: No module named 'gi' 3988s autopkgtest [18:31:02]: test nm_netplan.py: ---] 3989s autopkgtest [18:31:03]: test nm_netplan.py: - - - - - - - - - - results - - - - - - - - - - 3989s nm_netplan.pyFAIL non-zero exit status 1 --- [1] [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-noble/noble/amd64/n/network-manager/20240404_183130_7a1cc@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/2060241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade
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. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: network-manager gets uninstalled on apt full-upgrade I've tried two Noble systems this evening and both got their network- manager packages removed. So wifi is gone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055148] Re: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan
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 Network Manager and networkd backends. Right now NM seems to support only the SNI parameter (1.2.3.4#domain) but networkd supports more: "111.222.333.444:9953%ifname#example.com" for IPv4 and "[:::]:9953%ifname#example.com" for IPv6. Alternatively, to keep things simpler, we could just accept the string 1.2.3.4#domain (and possibly the full notation used by networkd too). What do you think, Lukas? -- 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 supported with Netplan Status in netplan: New Status in netplan.io package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: 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 Server Name Indication (SNI) in the form server_address#SNI, e.g. 1.2.3.4#dns.myhome.com as nameserver addresses to Netplan. As a result, subsequent Netplan config applications fail because DNS servers don’t have the expected dotted decimal (IPv4) or colon’ed hex (IPv6) form. ``` nmcli> describe ipv4.dns === [dns] === [NM property description] Array of IP addresses of DNS servers. For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2055148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2055148] Re: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan
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 NetworkManager[7091]: /etc/netplan/90-NM-2116bb84-fa09-461a-a923-e04bc2648898.yaml:8:9: Error in network definition: malformed address '1.1.1.1#lxd', must be X.X.X.X or X:X:X:X:X:X:X:X Mar 15 09:46:40 noble-vm NetworkManager[7091]: - 1.1.1.1#lxd Mar 15 09:46:40 noble-vm NetworkManager[7091]: ^ Mar 15 09:46:40 noble-vm NetworkManager[7051]: [1710496000.8273] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Mar 15 09:46:40 noble-vm NetworkManager[7051]: ** Mar 15 09:46:40 noble-vm NetworkManager[7051]: nm:ERROR:src/core/settings/plugins/keyfile/nms-keyfile-writer.c:551:_internal_write_connection: assertion failed: (unreachable) Mar 15 09:46:40 noble-vm NetworkManager[7051]: Bail out! nm:ERROR:src/core/settings/plugins/keyfile/nms-keyfile-writer.c:551:_internal_write_connection: assertion failed: (unreachable) Mar 15 09:46:40 noble-vm systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT Mar 15 09:46:40 noble-vm systemd[1]: NetworkManager.service: Failed with result 'core-dump'. Mar 15 09:46:41 noble-vm systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 1. Mar 15 09:46:41 noble-vm systemd[1]: Starting NetworkManager.service - Network Manager... I also noticed another crash already reported here https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490 Mar 15 09:45:30 noble-vm systemd[1]: Stopping NetworkManager.service - Network Manager... Mar 15 09:45:30 noble-vm NetworkManager[6790]: [1710495930.0746] caught SIGTERM, shutting down normally. Mar 15 09:45:30 noble-vm NetworkManager[6790]: ** Mar 15 09:45:30 noble-vm NetworkManager[6790]: nm:ERROR:src/core/nm-policy.c:2937:dispose: assertion failed: (!c_list_is_empty(>policy_auto_activate_lst_head)) Mar 15 09:45:30 noble-vm NetworkManager[6790]: Bail out! nm:ERROR:src/core/nm-policy.c:2937:dispose: assertion failed: (!c_list_is_empty(>policy_auto_activate_lst_head)) Mar 15 09:45:30 noble-vm NetworkManager[6790]: [1710495930.0751] exiting (success) Mar 15 09:45:31 noble-vm systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT Mar 15 09:45:31 noble-vm systemd[1]: NetworkManager.service: Failed with result 'core-dump'. Mar 15 09:45:31 noble-vm systemd[1]: Starting NetworkManager.service - Network Manager... ** 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/2055148 Title: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan Status in netplan: New Status in netplan.io package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: 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 Server Name Indication (SNI) in the form server_address#SNI, e.g. 1.2.3.4#dns.myhome.com as nameserver addresses to Netplan. As a result, subsequent Netplan config applications fail because DNS servers don’t have the expected dotted decimal (IPv4) or colon’ed hex (IPv6) form. ``` nmcli> describe ipv4.dns === [dns] === [NM property description] Array of IP addresses of DNS servers. For DoT (DNS over TLS), the SNI server name can be specified by appending "#example.com" to the IP address of the DNS server. This currently only has effect when using systemd-resolved. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2055148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051576] Re: Please merge 1.9.15p5-3 into noble
** 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 Title: Please merge 1.9.15p5-3 into noble Status in sudo package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2051576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2051576] [NEW] Please merge 1.9.15p5-3 into noble
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: Please merge 1.9.15p5-3 into noble Status in sudo package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2051576/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1746419] Re: bond parameters are not changed by 'netplan apply'
** 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: Triaged Status in nplan package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: I have a yaml file as follows: network: version: 2 ethernets: bonddevs: match: name: ens[78] bonds: bond0: interfaces: [bonddevs] parameters: mode: active-backup mii-monitor-interval: 1 addresses: - 10.10.10.1/24 Say I decide that 1s is too frequent for the MII interval, and I want to change the interval to 2s. If I change that in the yaml, then run # netplan generate # netplan apply # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)" MII Polling Interval (ms): 1000 In other words, the change has not been applied. Running netplan --debug apply prints: DEBUG:device bond0 operstate is up, not replugging So I wondered if bringing the bond down would help. It does not: # ip link set dev bond0 down # netplan apply # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)" MII Polling Interval (ms): 1000 However, deleting the link works: # ip link del dev bond0 # netplan apply # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)" MII Polling Interval (ms): 2000 This is counter-intuitive behaviour. Ideally, I would like a regular netplan apply to work without deleting the bond. However, a changed to the docs to make this clear would be OK. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nplan 0.32~17.10.1 ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Jan 31 05:47:42 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: nplan UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1746419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045886] Re: Please merge 8.5.0-2 into noble
** 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 Title: Please merge 8.5.0-2 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045886] Re: Please merge 8.5.0-2 into noble
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 Title: Please merge 8.5.0-2 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045886] Re: Please merge 8.5.0-2 into noble
** 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 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046436] Re: Ubuntu won't boot after enabling jumbo packets on network device
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 Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2046436 Title: Ubuntu won't boot after enabling jumbo packets on network device Status in network-manager package in Ubuntu: New Bug description: Ubuntu Desktop 23.10 Asrock IMB-X1714 main board, with Intel I226V and I226LM ethernet controllers network-manager 1.44.2-1ubuntu1.2 When enabling jumbo packets on a wired network device by setting MTU to 9000, Ubuntu will not boot anymore. The Ubuntu splash screen, with rotating wheel, appears, at a lower resolution than ordinary, but freezes after a few seconds. I can only revert this by disabling the ethernet devices in BIOS. After that Ubuntu will boot normally. I can then manually edit the .yaml configuration files in /etc/netplan to disable jumbo packets again. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Dec 14 11:04:19 2023 IfupdownConfig: InstallationDate: Installed on 2023-12-13 (1 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) IpRoute: default via 192.168.0.1 dev enp4s0 proto dhcp src 192.168.0.208 metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.208 metric 100 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled missing enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2046436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
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 => Confirmed
** 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/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong default netmask for
IPv6 addresses
Status in netplan.io package in Ubuntu:
Confirmed
Status in network-manager package in Ubuntu:
Invalid
Bug description:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only
connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
allowed-ips:
- "10.0.0.1/32"
networkmanager:
uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
name: "con-wg0"
passthrough:
ipv6.addr-gen-mode: "default"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
"2001::1"]. Notably the addresses do *not* have a netmask, neither in
the original config nor that update. Unfortunately that update cannot
be done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
But this generates a wrong "/32" default netmask in the netplan config
for the IPv6 address:
allowed-ips:
- "10.0.0.1/32"
- "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is
not added on this call. The netplan backend should do that (not
second-guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour or so trying to stitch
it together, but I hope your unit tests make this easier somehow.
This was fine until 22.10, but with NM's new "netplan by default"
backend this regressed.
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1.2
To manage notifications about this bug go to:
[Touch-packages] [Bug 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
** 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
IPv6 addresses
Status in netplan.io package in Ubuntu:
New
Status in network-manager package in Ubuntu:
New
Bug description:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only
connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
allowed-ips:
- "10.0.0.1/32"
networkmanager:
uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
name: "con-wg0"
passthrough:
ipv6.addr-gen-mode: "default"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
"2001::1"]. Notably the addresses do *not* have a netmask, neither in
the original config nor that update. Unfortunately that update cannot
be done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
But this generates a wrong "/32" default netmask in the netplan config
for the IPv6 address:
allowed-ips:
- "10.0.0.1/32"
- "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is
not added on this call. The netplan backend should do that (not
second-guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour or so trying to stitch
it together, but I hope your unit tests make this easier somehow.
This was fine until 22.10, but with NM's new "netplan by default"
backend this regressed.
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2046158/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2046158] Re: Updating wireguard-peer.allowed-ips gets wrong default netmask for IPv6 addresses
** 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 wireguard-peer.allowed-ips gets wrong default netmask for
IPv6 addresses
Status in netplan.io package in Ubuntu:
New
Status in network-manager package in Ubuntu:
New
Bug description:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only
connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
addresses:
- "10.0.0.2/24"
mode: "wireguard"
port: 51820
keys:
private: "KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E="
peers:
- keys:
public: "RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI="
allowed-ips:
- "10.0.0.1/32"
networkmanager:
uuid: "b5edee2d-c736-4827-bae3-c95e349cb73b"
name: "con-wg0"
passthrough:
ipv6.addr-gen-mode: "default"
ipv6.method: "disabled"
ipv6.ip6-privacy: "-1"
proxy._: ""
which gets rendered as
# cat /run/NetworkManager/system-connections/netplan-wg0.nmconnection
[connection]
id=con-wg0
type=wireguard
uuid=b5edee2d-c736-4827-bae3-c95e349cb73b
interface-name=wg0
[wireguard]
private-key=KDI3xiJN6uthba43AMm7EBBxjPPNeamjlV3xXT5Zh0E=
listen-port=51820
[wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=]
allowed-ips=10.0.0.1/32;
[ipv4]
method=manual
address1=10.0.0.2/24
[ipv6]
#Netplan: passthrough override
method=disabled
#Netplan: passthrough setting
addr-gen-mode=default
[proxy]
Now the UI modifies the "allowed-ips" setting to ["10.0.0.1",
"2001::1"]. Notably the addresses do *not* have a netmask, neither in
the original config nor that update. Unfortunately that update cannot
be done on the CLI:
# nmcli con modify con-wg0
"wireguard-peer.RsfKtJHMIAYs/i2i/TZUfRSWF1LmAEXzc3UyidXZTnI=.allowed-ips"
"2001::1"
Error: invalid or not allowed setting 'wireguard-peer': 'wireguard-peer' not
among [connection, wireguard, match, ipv4, ipv6, hostname, link, tc, proxy].
So it has to happen via D-Bus:
"/org/freedesktop/NetworkManager/Settings/5","org.freedesktop.NetworkManager.Settings.Connection","Update",[{"connection":{"id":{"v":"con-
wg0","t":"s"},"interface-
name":{"v":"wg0","t":"s"},"permissions":{"t":"as","v":[]},"timestamp":{"t":"t","v":1702299778},"type":{"v":"wireguard","t":"s"},"uuid":{"v":"04237010-9663-4064-aa06-bcde279b67da","t":"s"},"autoconnect":{"v":true,"t":"b"},"autoconnect-
slaves":{"v":-1,"t":"i"}},"wireguard":{"listen-
port":{"v":51820,"t":"u"},"peers":{"v":[{"public-
key":{"t":"s","v":"2CvDKtc8k94LLpabq6rZdYh1Co8fzjhoAD61ESMfjSc="},"allowed-
ips":{"t":"as","v":["10.0.0.1/32","2001::1"]}}],"t":"aa{sv}"},"private-
key":{"v":"iDM1BknhsROJt8TpJnBNNHVCAqWnfqZEkL20+sVfXlA=","t":"s"}},"ipv4":{"address-
data":{"t":"aa{sv}","v":[{"address":{"t":"s","v":"10.0.0.2"},"prefix":{"t":"u","v":24}}]},"addresses":{"v":[[33554442,24,0]],"t":"aau"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"manual","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"t":"aau","v":[]},"dns":{"v":[],"t":"au"}},"ipv6":{"address-
data":{"t":"aa{sv}","v":[]},"addresses":{"v":[],"t":"a(ayuay)"},"dns-
search":{"v":[],"t":"as"},"method":{"v":"disabled","t":"s"},"route-
data":{"t":"aa{sv}","v":[]},"routes":{"v":[],"t":"a(ayuayu)"},"ignore-
auto-dns":{"v":false,"t":"b"},"ignore-auto-
routes":{"v":false,"t":"b"},"dns":{"v":[],"t":"aay"}},"proxy":{}}]]
But this generates a wrong "/32" default netmask in the netplan config
for the IPv6 address:
allowed-ips:
- "10.0.0.1/32"
- "2001::1/32"
On Fedora, with NM's default .nmconnection files, such a netmask is
not added on this call. The netplan backend should do that (not
second-guessing NM) or at least default to /128 for an IPv6 address.
Doing this D-Bus call with `busctl` is a nuisance. If you need a
reproducer at this level, I can spend an hour or so trying to stitch
it together, but I hope your unit tests make this easier somehow.
This was fine until 22.10, but with NM's new "netplan by default"
backend this regressed.
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2046158/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045886] Re: Please merge 8.5.0-1 into noble
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 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-1 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2045886] [NEW] Please merge 8.5.0-1 into noble
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: Please merge 8.5.0-1 into noble Status in curl package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044270] Re: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10
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 => Triaged -- 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/2044270 Title: Wi-Fi connection lost and reestablished every 3 minutes after upgrade from Lubuntu 22.10 to 23.10 Status in network-manager package in Ubuntu: Triaged Bug description: In Lubuntu 22.10 (Kinetic) Wi-Fi connection on my laptop was stable. A couple of days ago I upgraded Lubuntu (installed it afresh) to 23.10 (Mantic Minotaur). Now the connection is lost every couple of minutes and reestablished again in 3-20 seconds automatically. The same issue with two different internet providers (two different routers). Network manager version as told by command "apt-cache policy network- manager" is 1.44.2-1ubuntu1.2. My laptop model is Digma CITI E401. sudo lshw -class network *-network description: Wireless interface physical id: e bus info: mmc@2:0001:1 logical name: wlan0 serial: 80:5e:4f:02:97:70 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8723bs driverversion=6.5.0-13-generic ip=192.168.0.13 multicast=yes wireless=IEEE 802.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
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 Mantic. If you grep /etc/netplan by the interface name, do you see more than one file? Something like this "sudo grep wg0 /etc/netplan/*". If you find the same interface in more than one file, try to remove them and create the connection again using the GUI. The problem might be that you have multiple YAMLs with the same interface. Netplan will merge them in a single configuration and the result might be a broken config. Let me know if it helps. Thanks! -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2044014] Re: networkmanager crashes on configuring wireguard connection via nm-connection-editor
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 to setup the connection? I want to understand how you managed to set the ipv4.dns property with ipv4.method set to disabled using the GUI interface. May I ask you to watch the Network Manager's journal while you reproduce the crash and add the relevant part of the logs here? journalctl -u NetworkManager.service -f Also, you will probably find a YAML in /etc/netplan that was created for the problematic connection. Can you find it, remove all the keys and IPs from it, and paste it here? I'm running netplan.io 0.107-5ubuntu0.1 and I can create Wireguard connections just fine. But maybe you are using some settings that's triggering another bug that we are not aware of. Thank you. ** Changed in: network-manager (Ubuntu) Status: New => Triaged ** Changed in: network-manager (Ubuntu) Importance: Undecided => Medium -- 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/2044014 Title: networkmanager crashes on configuring wireguard connection via nm- connection-editor Status in network-manager package in Ubuntu: Triaged Bug description: when configuring a new wireguard connection both via nm-connection-editor and the settings app, NetworkManager crashes and restarts, with the error message "Message recipient disconnected from message bus without replying". Currently, I'm unable to add wireguard connections at all. Also, I have netplan.io/now 0.107-5ubuntu1~ppa3 installed to outrule https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2039821 Ubuntu 23.10 network-manager/mantic-updates,now 1.44.2-1ubuntu1.2 amd64 netplan.io/now 0.107-5ubuntu1~ppa3 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1.2 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 20 20:10:40 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-15 (2015 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via dev enp0s31f6 proto dhcp src metric 100 /24 dev enp0s31f6 proto kernel scope link src metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=false ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: network-manager UpgradeStatus: Upgraded to mantic on 2023-11-05 (15 days ago) http_proxy: http://:3128 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled disabled missing disabled no_proxy: 127.0.0.1,172.16.0.0/12,10.0.0.0/8,192.168.0.0/16, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039798] Re: please merge from debian instable 8.4 to address vulnerability
** 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 Title: please merge from debian instable 8.4 to address vulnerability Status in curl package in Ubuntu: Confirmed Bug description: Actually Mantic has 8.2.1 version A huge security issue is fixed with 8.4 : https://linuxsecurity.com/news/security-vulnerabilities/curl-8-4-released-for-addressing-a-big-security-vulnerability changelog: https://curl.se/changes.html Available on Debian Sid: https://packages.debian.org/sid/curl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2039798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2042431] Re: Please merge 1.226-1 into noble
** 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. https://bugs.launchpad.net/bugs/2042431 Title: Please merge 1.226-1 into noble Status in netcat-openbsd package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/2042431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2042431] [NEW] Please merge 1.226-1 into noble
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. https://bugs.launchpad.net/bugs/2042431 Title: Please merge 1.226-1 into noble Status in netcat-openbsd package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/2042431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2023183] Re: network-manager autokpgtest failure (nm.py)
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 affects: network-manager (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Mantic) Status: New => Confirmed ** Changed in: network-manager (Ubuntu Lunar) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu Mantic) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu Noble) Importance: Undecided => Low -- 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/2023183 Title: network-manager autokpgtest failure (nm.py) Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Lunar: Confirmed Status in network-manager source package in Mantic: Confirmed Status in network-manager source package in Noble: Confirmed Bug description: This fails only on arm64. https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/arm64/n/network-manager/20230522_141200_71ac4@/log.gz To be determined if there is a bug in the package or linux kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2023183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2023183] Re: network-manager autokpgtest failure (nm.py)
** 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. https://bugs.launchpad.net/bugs/2023183 Title: network-manager autokpgtest failure (nm.py) Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Lunar: Confirmed Status in network-manager source package in Mantic: Confirmed Status in network-manager source package in Noble: Confirmed Bug description: This fails only on arm64. https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/arm64/n/network-manager/20230522_141200_71ac4@/log.gz To be determined if there is a bug in the package or linux kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2023183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2040153] Re: Network Manager will not remove Netplan YAMLs when connections are deleted
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 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 deleted Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: In Progress Status in netplan.io source package in Mantic: Invalid Status in network-manager source package in Mantic: Fix Committed Bug description: [ 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 netplan apply is executed. This is happening because the systemd service unit is setting the property "ProtectSystem" to true. Because of that, /usr is being presented to the Network Manager daemon as read-only. When connections are deleted, libnetplan will try to open its YAML files with writing permissions and will fail for files from /usr/lib/netplan. Even if the user hasn't added any files there manually, the file /usr/lib/netplan/00-network-manager-all.yaml will be installed by the package ubuntu-settings. This issue is fixed by allow-listing /usr/lib/netplan with ReadWritePaths=/usr/lib/netplan in systemd so the Network Manager's daemon will be able to write to that directory. This upload also improves the autopkgtests related to Netplan. Network Manager will be started by systemd, which ensures we are testing in the same environment conditions used by a desktop installation. It also adds a few more instances of connections deletions so we can test a bit more that YAML files are being removed. It also adds all the dependencies required by the test script (which sadly was causing the nm_netplan.py tests to be skipped). [ Test Plan ] Launch a new Mantic VM: $ lxc launch ubuntu:mantic --vm Install network-manager and ubuntu-settings: # apt install network-manager ubuntu-settings Run Netplan # netplan apply Create a dummy connection via nmcli: # nmcli con add type dummy connection.interface-name dummy0 Check a new YAML will be created in /etc/netplan Delete the connection with nmcli # nmcli con del dummy-dummy0 Check the YAML WAS NOT removed from /etc/netplan You will see the error below in the NetworkManager's journal netplan_delete_connection: Cannot write output state: Read-only file system Add the PPA containing the fix and run the same test described above # add-apt-repository ppa:danilogondolfo/network-manager # apt update # apt upgrade Check that the YAML will be created when the connection is added and deleted and the connection is removed. [ Where problems could occur ] As the only change is a relaxation of the restrictions applied by systemd on the environment where Network Manager runs, we are not expecting any regression. As for the changes in the autopkgtest related to Netplan, they are passing on all architectures. Autopkgtests amd64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/amd64/n/network-manager/20231023_175203_b2798@/log.gz ppc64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/ppc64el/n/network-manager/20231023_182332_f0497@/log.gz s390x - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/s390x/n/network-manager/20231023_190810_ced8d@/log.gz arm64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/arm64/n/network-manager/20231024_084542_ac017@/log.gz armhf - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/armhf/n/network-manager/20231024_083545_ac017@/log.gz [ Other Info ] --- Original description --- 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 has this setting "ProtectSystem=true", which will mount /usr as read-only for NM. Second, we migrated the default "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1]. When libnetplan tries to open this file for writing, the open system fails with EROFS: --- 22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system) 22517
[Touch-packages] [Bug 2040153] Re: Network Manager will not remove Netplan YAMLs when connections are deleted
** 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 + netplan apply is executed. + + This is happening because the systemd service unit is setting the property "ProtectSystem" + to true. Because of that, /usr is being presented to the Network Manager daemon as read-only. + When connections are deleted, libnetplan will try to open its YAML files with writing permissions + and will fail for files from /usr/lib/netplan. Even if the user hasn't added any files there manually, + the file /usr/lib/netplan/00-network-manager-all.yaml will be installed by the package ubuntu-settings. + + This issue is fixed by allow-listing /usr/lib/netplan with ReadWritePaths=/usr/lib/netplan in systemd + so the Network Manager's daemon will be able to write to that directory. + + This upload also improves the autopkgtests related to Netplan. Network Manager will be + started by systemd, which ensures we are testing in the same environment conditions + used by a desktop installation. It also adds a few more instances of connections deletions so + we can test a bit more that YAML files are being removed. It also adds all the dependencies + required by the test script (which sadly was causing the nm_netplan.py tests to be skipped). + + [ Test Plan ] + + Launch a new Mantic VM: + + $ lxc launch ubuntu:mantic --vm + + Install network-manager and ubuntu-settings: + + # apt install network-manager ubuntu-settings + + Run Netplan + + # netplan apply + + Create a dummy connection via nmcli: + + # nmcli con add type dummy connection.interface-name dummy0 + + Check a new YAML will be created in /etc/netplan + + Delete the connection with nmcli + + # nmcli con del dummy-dummy0 + + Check the YAML WAS NOT removed from /etc/netplan + + You will see the error below in the NetworkManager's journal + + netplan_delete_connection: Cannot write output state: Read-only file + system + + Add the PPA containing the fix and run the same test described above + + # add-apt-repository ppa:danilogondolfo/network-manager + # apt update + # apt upgrade + + Check that the YAML will be created when the connection is added and + deleted and the connection is removed. + + [ Where problems could occur ] + + As the only change is a relaxation of the restrictions applied by systemd on the environment where Network Manager + runs, we are not expecting any regression. + + As for the changes in the autopkgtest related to Netplan, they are + passing on all architectures. + + Autopkgtests + + amd64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/amd64/n/network-manager/20231023_175203_b2798@/log.gz + ppc64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/ppc64el/n/network-manager/20231023_182332_f0497@/log.gz + s390x - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/s390x/n/network-manager/20231023_190810_ced8d@/log.gz + arm64 - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/arm64/n/network-manager/20231024_084542_ac017@/log.gz + armhf - https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-danilogondolfo-network-manager/mantic/armhf/n/network-manager/20231024_083545_ac017@/log.gz + + [ Other Info ] + + + --- Original description --- + 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 has this setting "ProtectSystem=true", which will mount /usr as read-only for NM. Second, we migrated the default "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1]. When libnetplan tries to open this file for writing, the open system fails with EROFS: --- 22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system) 22517 write(2, "netplan_delete_connection: Canno"..., 76) = 76 --- - [1] - https://launchpad.net/ubuntu/+source/ubuntu-settings/23.10.1 -- 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 deleted Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Triaged Status in netplan.io source package in Mantic: Invalid Status in network-manager source package in Mantic: Triaged Bug description: [
[Touch-packages] [Bug 2040153] [NEW] Network Manager will not remove Netplan YAMLs when connections are deleted
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 has this setting "ProtectSystem=true", which will mount /usr as read-only for NM. Second, we migrated the default "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1]. When libnetplan tries to open this file for writing, the open system fails with EROFS: --- 22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system) 22517 write(2, "netplan_delete_connection: Canno"..., 76) = 76 --- [1] - https://launchpad.net/ubuntu/+source/ubuntu-settings/23.10.1 ** Affects: netplan.io (Ubuntu) Importance: Critical Status: Triaged ** Affects: network-manager (Ubuntu) Importance: Critical Status: Triaged ** Affects: netplan.io (Ubuntu Mantic) Importance: Critical Status: Triaged ** Affects: network-manager (Ubuntu Mantic) Importance: Critical Status: Triaged ** Tags: foundations-todo ** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: netplan.io (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu Mantic) Importance: Undecided => Critical ** Changed in: network-manager (Ubuntu Mantic) Importance: Undecided => Critical -- 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 deleted Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Triaged Status in netplan.io source package in Mantic: Triaged Status in network-manager source package in Mantic: Triaged Bug description: 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 has this setting "ProtectSystem=true", which will mount /usr as read-only for NM. Second, we migrated the default "00-network-manager-all.yaml" file to, /usr/lib/netplan recently [1]. When libnetplan tries to open this file for writing, the open system fails with EROFS: --- 22517 openat(AT_FDCWD, "/lib/netplan/00-network-manager-all.yaml", O_WRONLY|O_CREAT|O_TRUNC, 0600) = -1 EROFS (Read-only file system) 22517 write(2, "netplan_delete_connection: Canno"..., 76) = 76 --- [1] - https://launchpad.net/ubuntu/+source/ubuntu-settings/23.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2040153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038811] Re: NetworkManager crashes when updating wpa-eap connections
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 in Ubuntu. https://bugs.launchpad.net/bugs/2038811 Title: NetworkManager crashes when updating wpa-eap connections Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding network-manager. This problem was most recently seen with package version 1.44.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/0185fff02c2976262de9f862e539829420f9c737 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2038811/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 1
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-connections# mv /etc/NetworkManager/system-connections/UPTOWN.guests /etc/NetworkManager/system-connections/UPTOWN root@mantic:/etc/NetworkManager/system-connections# nmcli con load /etc/NetworkManager/system-connections/UPTOWN root@mantic:/etc/NetworkManager/system-connections# nmcli con show NAMEUUID TYPE DEVICE netplan-enp5s0 e1419a5e-5e1d-3fff-a17c-b2fc6d2cef99 ethernet enp5s0 lo e71fd408-7b42-49a1-af17-072edc915266 loopback lo UPTOWN.guests 491fa5c8-68ef-4140-8679-dca422f5c262 wifi -- root@mantic:/etc/NetworkManager/system-connections# It's considering the .guests a bad extension as far as I can see. Only removing the .guests makes it loadable. So we shouldn't load only .nmconnection files. -- 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/2039503 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 Status in network-manager package in Ubuntu: New Status in network-manager source package in Mantic: New Bug description: lunar to mantic upgrade, exciting to see output from network-manager postinst migrating connections to /etc/netplan one by one. But then: Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess returned error exit status 10 That UUID appears in a file /etc/NetworkManager/system- connections/UPTOWN.guests that hasn't been touched since 2015. Contents of the file were: [connection] id=UPTOWN.guests uuid=491fa5c8-68ef-4140-8679-dca422f5c262 type=wifi [wifi] ssid=UPTOWN.guests mode=infrastructure mac-address=E0:9D:31:09:84:54 [ipv6] method=auto [ipv4] method=auto I've removed it from disk and the migration continued to completion. Then I got another failure on: [connection] id=belkin.1e4.guests uuid=2c77e512-f3e3-4238-b401-c94559cc6db0 type=802-11-wireless [802-11-wireless] ssid=belkin.1e4.guests mode=infrastructure mac-address=00:24:D7:1F:EA:20 [ipv6] method=auto [ipv4] method=auto Is it unhappy because of the . in the names? ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 16 16:12:43 2023 ErrorMessage: installed network-manager package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-12-23 (1393 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: network-manager Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039503/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 1
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 member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2039503 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 Status in network-manager package in Ubuntu: New Status in network-manager source package in Mantic: New Bug description: lunar to mantic upgrade, exciting to see output from network-manager postinst migrating connections to /etc/netplan one by one. But then: Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile. dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess returned error exit status 10 That UUID appears in a file /etc/NetworkManager/system- connections/UPTOWN.guests that hasn't been touched since 2015. Contents of the file were: [connection] id=UPTOWN.guests uuid=491fa5c8-68ef-4140-8679-dca422f5c262 type=wifi [wifi] ssid=UPTOWN.guests mode=infrastructure mac-address=E0:9D:31:09:84:54 [ipv6] method=auto [ipv4] method=auto I've removed it from disk and the migration continued to completion. Then I got another failure on: [connection] id=belkin.1e4.guests uuid=2c77e512-f3e3-4238-b401-c94559cc6db0 type=802-11-wireless [802-11-wireless] ssid=belkin.1e4.guests mode=infrastructure mac-address=00:24:D7:1F:EA:20 [ipv6] method=auto [ipv4] method=auto Is it unhappy because of the . in the names? ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Oct 16 16:12:43 2023 ErrorMessage: installed network-manager package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-12-23 (1393 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: network-manager Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039503/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2039371] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Termin
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 notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2039371 Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Terminated) Status in network-manager package in Ubuntu: New Bug description: With do-release-upgrade -d, Setting up network-manager hanged indefinitely with [...] Setting up network-manager (1.44.2-1ubuntu1) ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... ^[[CSKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... SKIP: NetworkManager is not ready ... [...] Killing it resulted in Terminated SKIP: NetworkManager is not ready ... dpkg: error processing package network-manager (--configure): installed network-manager package post-installation script subprocess was killed by signal (Terminated) ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.44.2-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Sun Oct 15 00:40:40 2023 ErrorMessage: installed network-manager package post-installation script subprocess was killed by signal (Terminated) InstallationDate: Installed on 2023-01-13 (274 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IpRoute: default via 192.168.0.254 dev wlp2s0 proto dhcp src 192.168.0.29 metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.29 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5 PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.0ubuntu1 apt 2.7.3 SourcePackage: network-manager Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Terminated) UpgradeStatus: Upgraded to mantic on 2023-10-14 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.44.2 connected starting full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039371/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2038811] Re: /usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:_internal_write_connection:nms_keyfile_writer_connection:nms_keyfile_plugin_update_connection
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: /usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:_internal_write_connection:nms_keyfile_writer_connection:nms_keyfile_plugin_update_connection Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding network-manager. This problem was most recently seen with package version 1.44.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/0185fff02c2976262de9f862e539829420f9c737 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2038811/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034539] Re: Create the usbmux user in the preinst script
** 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 will install a udev .rules file referring to a user that will be created only in the final steps of the upgrade process. As systemd daemon-reload is called a number of times during the process. The issue is triggered many times and makes the upgrade take way longer than it should. In resume, Netplan is calling udevadm reload from a systemd generator, it will process .rules files. When it tries to check the users defined in these files, if they don't exist in /etc/passwd, it will go to systemd (thanks to our nsswitch.conf). But because we are in the middle of a daemon-reload, the userdb is not ready yet and the process will stuck until it times out (for like 2 minutes). The workaround would be to create the user sooner. But the problem will continue to happen if another package does the same thing. While this is an issue with Netplan, the proper fix is complicated and we are working on it https://github.com/canonical/netplan/pull/304 + + + How to reproduce the issue: launch a LXD Lunar default or cloud image and try to do a do-release-upgrade to mantic. You'll notice that at some point during the "setting up" phase the process will stuck every time a install script calls a systemctl daemon-reload. -- 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 Title: Create the usbmux user in the preinst script Status in usbmuxd package in Ubuntu: New Bug description: 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 will install a udev .rules file referring to a user that will be created only in the final steps of the upgrade process. As systemd daemon-reload is called a number of times during the process. The issue is triggered many times and makes the upgrade take way longer than it should. In resume, Netplan is calling udevadm reload from a systemd generator, it will process .rules files. When it tries to check the users defined in these files, if they don't exist in /etc/passwd, it will go to systemd (thanks to our nsswitch.conf). But because we are in the middle of a daemon-reload, the userdb is not ready yet and the process will stuck until it times out (for like 2 minutes). The workaround would be to create the user sooner. But the problem will continue to happen if another package does the same thing. While this is an issue with Netplan, the proper fix is complicated and we are working on it https://github.com/canonical/netplan/pull/304 How to reproduce the issue: launch a LXD Lunar default or cloud image and try to do a do-release-upgrade to mantic. You'll notice that at some point during the "setting up" phase the process will stuck every time a install script calls a systemctl daemon-reload. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/2034539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034539] Re: Create the usbmux user in the preinst script
** 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 https://bugs.launchpad.net/netplan/+bug/1999178 This package will install a udev .rules file referring to a user that will be created only in the final steps of the upgrade process. As systemd daemon-reload is called a number of times during the process. The issue is triggered many times and makes the upgrade take way longer than it should. In resume, Netplan is calling udevadm reload from a systemd generator, it will process .rules files. When it tries to check the users defined in these files, if they don't exist in /etc/passwd, it will go to systemd (thanks to our nsswitch.conf). But because we are in the middle of a daemon-reload, the userdb is not ready yet and the process will stuck until it times out (for like 2 minutes). The workaround would be to create the user sooner. But the problem will continue to happen if another package does the same thing. While this is an issue with Netplan, the proper fix is complicated and we are working on it https://github.com/canonical/netplan/pull/304 -- 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 Title: Create the usbmux user in the preinst script Status in usbmuxd package in Ubuntu: New Bug description: 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 will install a udev .rules file referring to a user that will be created only in the final steps of the upgrade process. As systemd daemon-reload is called a number of times during the process. The issue is triggered many times and makes the upgrade take way longer than it should. In resume, Netplan is calling udevadm reload from a systemd generator, it will process .rules files. When it tries to check the users defined in these files, if they don't exist in /etc/passwd, it will go to systemd (thanks to our nsswitch.conf). But because we are in the middle of a daemon-reload, the userdb is not ready yet and the process will stuck until it times out (for like 2 minutes). The workaround would be to create the user sooner. But the problem will continue to happen if another package does the same thing. While this is an issue with Netplan, the proper fix is complicated and we are working on it https://github.com/canonical/netplan/pull/304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/2034539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034539] Re: Create the usbmux user in the preinst script
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 Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/2034539 Title: Create the usbmux user in the preinst script Status in usbmuxd package in Ubuntu: New Bug description: 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 created only in the final steps of the upgrade process. As systemd daemon-reload is called a number of times during the process. The issue is triggered many times and makes the upgrade take way longer than it should. In resume, Netplan is calling udevadm reload from a systemd generator, it will process .rules files. When it tries to check the users defined in these files, if they don't exist in /etc/passwd, it will go to systemd (thanks to our nsswitch.conf). But because we are in the middle of a daemon-reload, the userdb is not ready yet and the process will stuck until it times out (for like 2 minutes). The workaround would be to create the user sooner. But the problem will continue to happen if another package does the same thing. While this is an issue with Netplan, the proper fix is complicated and we are working on it https://github.com/canonical/netplan/pull/304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/2034539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034539] Re: Create the usbmux user in the preinst script
** 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 created only in the final steps of the upgrade process. As + systemd daemon-reload is called a number of times during the process. + The issue is triggered many times and makes the upgrade take way longer + than it should. + + In resume, Netplan is calling udevadm reload from a systemd generator, + it will process .rules files. When it tries to check the users defined + in these files, if they don't exist in /etc/passwd, it will go to + systemd (thanks to our nsswitch.conf). But because we are in the middle + of a daemon-reload, the userdb is not ready yet and the process will + stuck until it times out (for like 2 minutes). + + The workaround would be to create the user sooner. But the problem will + continue to happen if another package does the same thing. + + While this is an issue with Netplan, the proper fix is complicated and + we are working on it https://github.com/canonical/netplan/pull/304 -- 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 Title: Create the usbmux user in the preinst script Status in usbmuxd package in Ubuntu: New Bug description: 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 created only in the final steps of the upgrade process. As systemd daemon-reload is called a number of times during the process. The issue is triggered many times and makes the upgrade take way longer than it should. In resume, Netplan is calling udevadm reload from a systemd generator, it will process .rules files. When it tries to check the users defined in these files, if they don't exist in /etc/passwd, it will go to systemd (thanks to our nsswitch.conf). But because we are in the middle of a daemon-reload, the userdb is not ready yet and the process will stuck until it times out (for like 2 minutes). The workaround would be to create the user sooner. But the problem will continue to happen if another package does the same thing. While this is an issue with Netplan, the proper fix is complicated and we are working on it https://github.com/canonical/netplan/pull/304 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/2034539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2034539] [NEW] Create the usbmux user in the preinst script
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 Title: Create the usbmux user in the preinst script Status in usbmuxd package in Ubuntu: New Bug description: [placeholder] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/2034539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033391] Re: Some Netplan-related autopkgtests are failing on armhf
** 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 autopkgtests are failing on armhf Status in netplan.io package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in netplan.io source package in Mantic: Fix Released Status in network-manager source package in Mantic: Fix Released Bug description: 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 a connection and validates if the ... Warning: nmcli (1.44.0) and NetworkManager (Unknown) versions don't match. Restarting NetworkManager is advised. Error: NetworkManager is not running. FAIL We need to wait until Network Manager is ready before starting the test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033391] Re: Some Netplan-related autopkgtests are failing on armhf
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 FAIL non-zero exit status 2 1749s urfkill-integration FAIL non-zero exit status 2 1749s nm_netplan.pyPASS -- 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 autopkgtests are failing on armhf Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in netplan.io source package in Mantic: New Status in network-manager source package in Mantic: New Bug description: 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 a connection and validates if the ... Warning: nmcli (1.44.0) and NetworkManager (Unknown) versions don't match. Restarting NetworkManager is advised. Error: NetworkManager is not running. FAIL We need to wait until Network Manager is ready before starting the test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033391] Re: Some Netplan-related autopkgtests are failing on armhf
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/build.A2V/src/debian/tests 794s make[1]: Entering directory '/usr/src/linux-headers-6.3.0-7-generic' 794s warning: the compiler differs from the one used to build the kernel 794s The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1) 12.3.0 794s You are using: 794s CC [M] /tmp/autopkgtest.6Iru72/build.A2V/src/debian/tests/fake-rfkill.o 794s /bin/sh: 1: gcc-12: not found 794s make[2]: *** [scripts/Makefile.build:260: /tmp/autopkgtest.6Iru72/build.A2V/src/debian/tests/fake-rfkill.o] Error 127 794s make[1]: *** [Makefile:2030: /tmp/autopkgtest.6Iru72/build.A2V/src/debian/tests] Error 2 794s make[1]: Leaving directory '/usr/src/linux-headers-6.3.0-7-generic' 794s make: *** [debian/tests/Makefile:5: fake-rfkill] Error 2 -- 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 autopkgtests are failing on armhf Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in netplan.io source package in Mantic: New Status in network-manager source package in Mantic: New Bug description: 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 a connection and validates if the ... Warning: nmcli (1.44.0) and NetworkManager (Unknown) versions don't match. Restarting NetworkManager is advised. Error: NetworkManager is not running. FAIL We need to wait until Network Manager is ready before starting the test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033391] Re: Some Netplan-related autopkgtests are failing on armhf
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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2033391 Title: Some Netplan-related autopkgtests are failing on armhf Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in netplan.io source package in Mantic: New Status in network-manager source package in Mantic: New Bug description: 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 a connection and validates if the ... Warning: nmcli (1.44.0) and NetworkManager (Unknown) versions don't match. Restarting NetworkManager is advised. Error: NetworkManager is not running. FAIL We need to wait until Network Manager is ready before starting the test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033391] Re: Some Netplan-related autopkgtests are failing on armhf
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 autopkgtests are failing on armhf Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in netplan.io source package in Mantic: New Status in network-manager source package in Mantic: New Bug description: 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 a connection and validates if the ... Warning: nmcli (1.44.0) and NetworkManager (Unknown) versions don't match. Restarting NetworkManager is advised. Error: NetworkManager is not running. FAIL We need to wait until Network Manager is ready before starting the test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2033391] [NEW] Some Netplan-related autopkgtests are failing on armhf
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 a connection and validates if the ... Warning: nmcli (1.44.0) and NetworkManager (Unknown) versions don't match. Restarting NetworkManager is advised. Error: NetworkManager is not running. FAIL We need to wait until Network Manager is ready before starting the test. ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: netplan.io (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu Mantic) Importance: Undecided 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/2033391 Title: Some Netplan-related autopkgtests are failing on armhf Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in netplan.io source package in Mantic: New Status in network-manager source package in Mantic: New Bug description: 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 a connection and validates if the ... Warning: nmcli (1.44.0) and NetworkManager (Unknown) versions don't match. Restarting NetworkManager is advised. Error: NetworkManager is not running. FAIL We need to wait until Network Manager is ready before starting the test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2033391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026888] [NEW] Autopkgtest failing on s390x
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: ldap_sasl_interactive_bind: Can't contact LDAP server (-1) The reason seems to be that the slapd daemon is not ready yet when the test calls ldapmodify. Adding a simple "sleep", as already done in another place in the same test, is enough to workaround the issue. Ideally it should try the command again if it fails using some sort of exponential backoff. A sleep-based workaround was proposed as part of https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2025655 ** 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/2026888 Title: Autopkgtest failing on s390x Status in sudo package in Ubuntu: New Bug description: 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: ldap_sasl_interactive_bind: Can't contact LDAP server (-1) The reason seems to be that the slapd daemon is not ready yet when the test calls ldapmodify. Adding a simple "sleep", as already done in another place in the same test, is enough to workaround the issue. Ideally it should try the command again if it fails using some sort of exponential backoff. A sleep-based workaround was proposed as part of https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2025655 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2026888/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build
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 subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2026826 Title: glib2.0 (2.77.0 ) breaks Netplan build Status in glib2.0 package in Ubuntu: New Bug description: 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 libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1 libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1 The build also works fine in Debian unstable, which is using glib2.0 2.74.6-2. Netplan is using plenty of GLib's keyfile functions (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to producing a different output with this newer release (some strange line breaks injected in the middle of a keyfile). Example keyfile from the test_wifis.test_wifi_wowlan test, that should be generated by Netplan and the way it fails: Expected output: ``` [connection] id=netplan-wl0-homenet type=wifi interface-name=wl0 [wifi] wake-on-wlan=330 ssid=homenet mode=infrastructure [ipv4] method=link-local [ipv6] method=ignore ``` Failure: ``` E AssertionError: '[con[88 chars]330\n\nssid=homenet\nmode=infrastructure\n[ipv[44 chars]re\n' != '[con[88 chars]330\nssid=homenet\nmode=infrastructure\n\n[ipv[44 chars]re\n' E [connection] E id=netplan-wl0-homenet E type=wifi E interface-name=wl0 E E [wifi] E wake-on-wlan=330 E - E ssid=homenet E mode=infrastructure E + E [ipv4] E method=link-local E E [ipv6] E method=ignore ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2026826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026230] Re: error when setting up after upgrading
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: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => In Progress
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
--
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/2026230
Title:
error when setting up after upgrading
Status in netplan.io package in Ubuntu:
In Progress
Status in network-manager package in Ubuntu:
Invalid
Bug description:
I received an error from apport about a programme not working. I
collected the data to submit. Hope this helps.
ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: network-manager 1.42.6-2ubuntu1
Uname: Linux 6.2.0-24-generic x86_64
Architecture: amd64
Date: Wed Jul 5 23:11:14 2023
ExecutablePath: /usr/sbin/NetworkManager
ExecutableTimestamp: 1687429583
ProcCmdline: /usr/sbin/NetworkManager --no-daemon
ProcCwd: /
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
Signal: 6
SourcePackage: network-manager
UserGroups: N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2026230/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2026230] Re: error when setting up after upgrading
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 notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2026230 Title: error when setting up after upgrading Status in network-manager package in Ubuntu: New Bug description: I received an error from apport about a programme not working. I collected the data to submit. Hope this helps. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: network-manager 1.42.6-2ubuntu1 Uname: Linux 6.2.0-24-generic x86_64 Architecture: amd64 Date: Wed Jul 5 23:11:14 2023 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1687429583 ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 6 SourcePackage: network-manager UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2026230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025655] Re: Please merge 1.9.13p3-3 into mantic
** 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 for a problem with autopkgtest + affecting s390x for a long while. See + https://git.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/commit/?id=ad1796726eb71d17d4ef983c96735092b522a3dd + + See the history of tests on s390x + https://autopkgtest.ubuntu.com/packages/sudo/mantic/s390x + + It's not reproducible locally though. Sleeping for a couple of seconds + between the start of the ldap server and the first ldapmodify command + seems to fix the problem reliably for us. -- 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: Please merge 1.9.13p3-3 into mantic Status in sudo package in Ubuntu: New Bug description: 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 for a problem with autopkgtest affecting s390x for a long while. See https://git.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/commit/?id=ad1796726eb71d17d4ef983c96735092b522a3dd See the history of tests on s390x https://autopkgtest.ubuntu.com/packages/sudo/mantic/s390x It's not reproducible locally though. Sleeping for a couple of seconds between the start of the ldap server and the first ldapmodify command seems to fix the problem reliably for us. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2025655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025655] Re: Please merge 1.9.13p3-3 into mantic
** 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 Title: Please merge 1.9.13p3-3 into mantic Status in sudo package in Ubuntu: New Bug description: [placeholder] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2025655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025666] Re: Please merge 1.225-1 into mantic
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 netcat-openbsd package in Ubuntu: New Bug description: PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/netcat- openbsd Autopkgtest https://autopkgtest.ubuntu.com/results/autopkgtest-mantic- danilogondolfo-netcat-openbsd/mantic/amd64/n/netcat- openbsd/20230703_202110_fccf3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/2025666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025666] Re: Please merge 1.225-1 into mantic
** 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 https://autopkgtest.ubuntu.com/results/autopkgtest-mantic- + danilogondolfo-netcat-openbsd/mantic/amd64/n/netcat- + openbsd/20230703_202110_fccf3@/log.gz -- 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 netcat-openbsd package in Ubuntu: New Bug description: PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/netcat- openbsd Autopkgtest https://autopkgtest.ubuntu.com/results/autopkgtest-mantic- danilogondolfo-netcat-openbsd/mantic/amd64/n/netcat- openbsd/20230703_202110_fccf3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/2025666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025666] [NEW] Please merge 1.225-1 into mantic
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. https://bugs.launchpad.net/bugs/2025666 Title: Please merge 1.225-1 into mantic Status in netcat-openbsd package in Ubuntu: New Bug description: [placeholder] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/2025666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020470] Re: 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/2020470 Title: Please merge 1.9.13p3-1 into mantic Status in sudo package in Ubuntu: Fix Released Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2020470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007698] Re: Please merge 1.9.13p1-1 into lunar
** 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 Status in sudo package in Ubuntu: Fix Released Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025655] [NEW] Please merge 1.9.13p3-3 into mantic
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: Please merge 1.9.13p3-3 into mantic Status in sudo package in Ubuntu: New Bug description: [placeholder] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2025655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2025027] Re: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Ther
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-GA401IV kernel: iwlwifi :02:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 jún 20 08:37:40 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi :02:00.0: retry init count 1 jún 20 08:37:40 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi :02:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340 jún 20 08:37:41 peter-ROG-Zephyrus-G14-GA401IV-GA401IV kernel: iwlwifi :02:00.0: retry init count 2 Run the command "rfkill list", does your wifi interface show up in the output? Also check the output of "ip link". If it's not showing up it might be a problem with the kernel driver or the hardware itself. You could try to install the kernel 5.19 to see if it fixes the problem. But as far as I can see it's not a problem with Network Manager. -- 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/2025027 Title: When I disconnect PC from LAN, I can't turn on Wi-Fi software-wise. The option to enable Wi-Fi is not available (does not pop up and it is hidden while on LAN). Therefore, I can't see any available WiFi networks. The issue gets resolved when I reboot the PC. Status in network-manager package in Ubuntu: Incomplete Bug description: See my public question open here: https://askubuntu.com/questions/1474771/wifi-control-gone-after-used-lan-cable-22-04-mate I'd expect, to see the option "dis/enable wifi" at least when I disconnect from LAN, (if not regardless on LAN connection). But I can not see that option to enable wifi, nor available wifi networks even when I disconnect the LAN cable.. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-75.82-generic 5.15.99 Uname: Linux 5.15.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Mon Jun 26 09:48:33 2023 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source /etc/network/interfaces.d/* InstallationDate: Installed on 2023-02-09 (136 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IpRoute: default via 192.168.1.1 dev enx00051b9a09b6 proto dhcp metric 100 169.254.0.0/16 dev enx00051b9a09b6 scope link metric 1000 192.168.1.0/24 dev enx00051b9a09b6 proto kernel scope link src 192.168.1.2 metric 100 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2025027/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface
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 added to the resulting .nmconnection file and the private key will be omitted. In this case, all the properties set in the group [wireguard] in the keyfile are not supported by the netplan's keyfile parser and will be left to be added to the keyfile *after* the wireguard peers, like this: - [connection] id=wg0 type=wireguard ... [wireguard-peer.M9nt4YujIOmNrRmpIRTmYSfMdrpvE7u6WkG8FY8WjG4=] endpoint=10.20.30.40:51820 allowed-ips=0.0.0.0/0; [wireguard] #Netplan: passthrough setting private-key-flags=1 #Netplan: passthrough setting listen-port=51820 --- For some reason, Network Manager will load the connection but *will not* load the wireguard-peer section. Moving the [wireguard] section to above [wireguard-peer...] resolves the issue. I can't find a reference that says that [wireguard] is supposed to come before [wireguard-peer]. A workaround you can use while we work on a fix is not use the option to encrypt the private key and store it in the network manager .nmconnection file. -- 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 connection at NetworkManager interface Status in netplan.io package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Invalid Bug description: Repro steps: 1) Open NetworkManager GUI. 2) Click "Add new Connection" and select "Wireguard" connection type. 3) Then you have to configure new connection. Basic configuration looks like that: a) Write down connection name, b) Write down local private key, c) Create new peer and populate peer's parameters: public key of the peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port. 4) Click "OK" and "Save". 5) Open "Peers" again. Ensure that settings were not stored. All fields are empty. Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager interface. netplan.io 0.106.1-2 network-manager 1.42.4-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2024661/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface
** 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 connection at NetworkManager interface Status in netplan.io package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Invalid Bug description: Repro steps: 1) Open NetworkManager GUI. 2) Click "Add new Connection" and select "Wireguard" connection type. 3) Then you have to configure new connection. Basic configuration looks like that: a) Write down connection name, b) Write down local private key, c) Create new peer and populate peer's parameters: public key of the peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port. 4) Click "OK" and "Save". 5) Open "Peers" again. Ensure that settings were not stored. All fields are empty. Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager interface. netplan.io 0.106.1-2 network-manager 1.42.4-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2024661/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface
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) Importance: Undecided => High ** Changed in: netplan.io (Ubuntu) Status: New => Confirmed -- 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 connection at NetworkManager interface Status in netplan.io package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Repro steps: 1) Open NetworkManager GUI. 2) Click "Add new Connection" and select "Wireguard" connection type. 3) Then you have to configure new connection. Basic configuration looks like that: a) Write down connection name, b) Write down local private key, c) Create new peer and populate peer's parameters: public key of the peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port. 4) Click "OK" and "Save". 5) Open "Peers" again. Ensure that settings were not stored. All fields are empty. Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager interface. netplan.io 0.106.1-2 network-manager 1.42.4-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2024661/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface
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 is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2024661 Title: Unable to configure Wireguard connection at NetworkManager interface Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Repro steps: 1) Open NetworkManager GUI. 2) Click "Add new Connection" and select "Wireguard" connection type. 3) Then you have to configure new connection. Basic configuration looks like that: a) Write down connection name, b) Write down local private key, c) Create new peer and populate peer's parameters: public key of the peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port. 4) Click "OK" and "Save". 5) Open "Peers" again. Ensure that settings were not stored. All fields are empty. Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager interface. netplan.io 0.106.1-2 network-manager 1.42.4-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2024661/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2022023] Re: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 8
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. https://bugs.launchpad.net/bugs/2022023 Title: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 8 Status in network-manager package in Ubuntu: New Bug description: I am using netplan for my network config. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.42.4-1ubuntu4 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Thu Jun 1 12:05:16 2023 ErrorMessage: installed network-manager package post-installation script subprocess returned error exit status 8 InstallationDate: Installed on 2020-04-25 (1131 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IpRoute: default via 192.168.56.1 dev enp7s0 proto static 192.168.56.0/30 dev enp7s0 proto kernel scope link src 192.168.56.2 IwConfig: lono wireless extensions. enp7s0no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.3, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.22ubuntu1 apt 2.7.0 RfKill: SourcePackage: network-manager Title: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 8 UpgradeStatus: Upgraded to mantic on 2023-06-01 (0 days ago) nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 8: Error: NetworkManager is not running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2022023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2021937] Re: preinst writes to /root
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 is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2021937 Title: preinst writes to /root Status in network-manager package in Ubuntu: New Bug description: As part of my sandboxed APT I noticed that the package failed to install as it was trying to write to /root. /root is a user directory, not a system one, which may not even exist because the administrator changed it to like /home/root, for example, and we definitely should not be writing system files in user directories. Preparing to unpack .../16-network-manager_1.42.4-1ubuntu4_amd64.deb ... mkdir: cannot create directory ‘/root/NetworkManager.bak’: Read-only file system cp: cannot create directory '/root/NetworkManager.bak/system-connections_1.42.4-1ubuntu2': No such file or directory dpkg: error processing archive /tmp/apt-dpkg-install-x9x0Qo/16-network-manager_1.42.4-1ubuntu4_amd64.deb (--unpack): new network-manager package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2021937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020470] Re: Please merge 1.9.13p3-1 into mantic
** 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. https://bugs.launchpad.net/bugs/2020470 Title: Please merge 1.9.13p3-1 into mantic Status in sudo package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2020470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020460] Re: Please merge 1:2.66-4 into mantic
** 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 Ubuntu. https://bugs.launchpad.net/bugs/2020460 Title: Please merge 1:2.66-4 into mantic Status in libcap2 package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020460] Re: Please merge 1:2.66-4 into mantic
** 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 Ubuntu. https://bugs.launchpad.net/bugs/2020460 Title: Please merge 1:2.66-4 into mantic Status in libcap2 package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020460] Re: Please merge 1:2.66-4 into mantic
** 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. https://bugs.launchpad.net/bugs/2020460 Title: Please merge 1:2.66-4 into mantic Status in libcap2 package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020470] Re: Please merge 1.9.13p3-1 into mantic
** 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 Title: Please merge 1.9.13p3-1 into mantic Status in sudo package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2020470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020470] [NEW] Please merge 1.9.13p3-1 into mantic
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: Please merge 1.9.13p3-1 into mantic Status in sudo package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2020470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020460] Re: Please merge 1:2.66-4 into mantic
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 mantic Status in libcap2 package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2020460] [NEW] Please merge 1:2.66-4 into mantic
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 Title: Please merge 1:2.66-4 into mantic Status in libcap2 package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
** 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. https://bugs.launchpad.net/bugs/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
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 be working yet when cloud-init needs it. -- 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 cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
** 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. https://bugs.launchpad.net/bugs/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
** 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. https://bugs.launchpad.net/bugs/2008952 Title: DNS failure while trying to fetch user-data Status in cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
** 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 cloud-init: Triaged Status in netplan: Invalid Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
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 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 cloud-init: Triaged Status in netplan: New Status in subiquity: New Status in systemd package in Ubuntu: New Bug description: In testing netboot + autoinstall of the new ubuntu desktop subiquity based installer for 23.04 I found cloud-init is failing to retrieve user-data because it can't resolved the hostname in the URL. This same configuration does work for 22.04 based subiquity, so seems a regression. From the ipxe config: imgargs vmlinuz initrd=initrd \ ip=dhcp \ iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso \ fsck.mode=skip \ layerfs-path=minimal.standard.live.squashfs \ autoinstall \ 'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \ That fails, but if we replace boot.linuxgroove.com with the IP it works. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data
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 failed
Traceback (most recent call last):
...
cloudinit.url_helper.UrlError: HTTPConnectionPool(host='boot.linuxgroove.com',
port=80): Max retries exceeded with url: /ubuntu/23.04/meta-data (Caused by
NewConnectionError(':
Failed to establish a new connection: [Errno -3] Temporary failure in name
resolution'))
>From systemd's journal
Mar 09 19:18:01 ubuntu systemd[1]: Starting NetworkManager.service - Network
Manager...
(edit)
resolved wasn't running as well
2023-03-09T19:18:01.712656+00:00 ubuntu systemd[1]: Starting systemd-
resolved.service - Network Name Resolution...
--
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 cloud-init:
Triaged
Status in netplan:
New
Status in subiquity:
New
Status in systemd package in Ubuntu:
New
Bug description:
In testing netboot + autoinstall of the new ubuntu desktop subiquity
based installer for 23.04 I found cloud-init is failing to retrieve
user-data because it can't resolved the hostname in the URL. This
same configuration does work for 22.04 based subiquity, so seems a
regression.
From the ipxe config:
imgargs vmlinuz initrd=initrd \
ip=dhcp \
iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso
\
fsck.mode=skip \
layerfs-path=minimal.standard.live.squashfs \
autoinstall \
'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \
That fails, but if we replace boot.linuxgroove.com with the IP it
works.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2008123] [NEW] Please merge 7.88.1-1 into lunar
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 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/2008123 Title: Please merge 7.88.1-1 into lunar Status in curl package in Ubuntu: New Bug description: PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/curl/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2008123/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007698] Re: Please merge 1.9.13p1-1 into lunar
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 correct in my PPA). I updated the merge request. Thanks! -- 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 Status in sudo package in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007698] Re: Please merge 1.9.13p1-1 into lunar
** 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. https://bugs.launchpad.net/bugs/2007698 Title: Please merge 1.9.13p1-1 into lunar Status in sudo package in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007698] Re: Please merge 1.9.13p1-1 into lunar
** 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 seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/2007698 Title: Please merge 1.9.13p1-1 into lunar Status in sudo package in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007698] Re: Please merge 1.9.12p2-1 into lunar
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 in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2007698] [NEW] Please merge 1.9.12p2-1 into lunar
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 -- 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 in Ubuntu: New Bug description: PPA available at https://launchpad.net/~danilogondolfo/+archive/ubuntu/sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2007698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
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 all set to true so we skip the libnetplan calls. Although when it's called when the connection is going down they are all false. And that's when the Netplan file is created and network-manager gets to a point in the code it shouldn't reach, so it crashes and the files are never removed. Not sure if calling the plugin writer in this case is a bug or not as the connection is volatile and is going to be deleted anyway. Maybe lost tracking of the connection nature (volatile, nm_generated and external) is the actual bug, not sure yet. One way to work around this is generating Netplan YAMLs regardless if the connection is volatile. If network-manager will create a file for it we could create a file for Netplan too. In fact, after removing the conditions to call libnetplan, the files are created and deleted when the OpenVPN client and/or server is stopped. Note that from network-manager 1.42.0 on, even the loopback interface can be represented as a connection, so we will have a Netplan file for it as well. -- 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/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Triaged Status in network-manager package in Ubuntu: Triaged Bug description: *** Note: This bug is mostly about comment #10, now *** When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006744] [NEW] libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict
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: error processing archive /tmp/apt-dpkg-install-AkyzpG/39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Then it will be broken: root@deleteme-lunar:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libglapi-mesa (= 22.2.5-0ubuntu1) but 22.3.4-1ubuntu1 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@deleteme-lunar:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libicu71 libpython3.10-minimal libpython3.10-stdlib python3.10 python3.10-minimal Use 'apt autoremove' to remove them. The following additional packages will be installed: libgl1-mesa-dri The following packages will be upgraded: libgl1-mesa-dri 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62 not fully installed or removed. Need to get 0 B/7806 kB of archives. After this operation, 809 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 81205 files and directories currently installed.) Preparing to unpack .../libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (22.3.4-1ubuntu1) over (22.2.5-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Errors were encountered while processing: /var/cache/apt/archives/libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) How to reproduce: 1. Spin up a Lunar VM 2. Enable -proposed 3. Install libgl1-mesa-dri and libgl1-amber-dri 4. Add APT::Default-Release "lunar-proposed"; to /etc/apt/apt.conf.d/somefile 5. Try to upgrade ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2006744 Title: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict Status in mesa package in Ubuntu: New Bug description: 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: error processing archive /tmp/apt-dpkg-install-AkyzpG/39-libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Then it will be broken: root@deleteme-lunar:~# apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libgl1-mesa-dri : Depends: libglapi-mesa (= 22.2.5-0ubuntu1) but 22.3.4-1ubuntu1 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@deleteme-lunar:~# apt --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: libicu71 libpython3.10-minimal libpython3.10-stdlib python3.10 python3.10-minimal Use 'apt autoremove' to remove them. The following additional packages will be installed: libgl1-mesa-dri The following packages will be upgraded: libgl1-mesa-dri 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 62 not fully installed or removed. Need to get 0 B/7806 kB of archives. After this operation, 809 kB of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 81205 files and directories currently installed.) Preparing to unpack .../libgl1-mesa-dri_22.3.4-1ubuntu1_amd64.deb ... Unpacking
[Touch-packages] [Bug 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
** 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. https://bugs.launchpad.net/bugs/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: In Progress Bug description: 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- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
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 d/t/upstream-root. Once we upgrade the hosts used for armhf tests we can drop the patch. -- 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/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: In Progress Bug description: 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- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
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] - https://git.launchpad.net/ubuntu/+source/libcap2/tree/tests/uns_test.c -- 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/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: In Progress Bug description: 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- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1998207] Re: netplan network-manager plugin tries to save temporary connections
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. https://bugs.launchpad.net/bugs/1998207 Title: netplan network-manager plugin tries to save temporary connections Status in netplan: Triaged Status in network-manager package in Ubuntu: Triaged Bug description: *** Note: This bug is mostly about comment #10, now *** When creating an OpenVPN connection, a temporal connection called tunN is created. For instance, after activating a connection called vpntest, I have: NAME UUID TYPE DEVICE vpntest 458856e6-8f0f-4dc6-82f2-dd72868252a0 vpn ens3 tun0 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 tun tun0 tun0 is created/removed after activating/deactivating vpntest and should not really be saved, but I see netplan adding it in /etc/netplan. And while doing so the plugin also reports some errors (I see these when stopping the connection): Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] BUG: the profile cannot be stored in keyfile format without becoming unusable: cannot access file: No such file or directory Nov 28 16:16:57 ubuntu NetworkManager[11752]: ((src/libnm-core-impl/nm-connection.c:342)): assertion '' failed Nov 28 16:16:57 ubuntu NetworkManager[11752]: [1669652217.2920] keyfile: commit: failure to write 1eb1dbe8-5678-4818-9adf-fb2dc01ed132 ((null)) to "/run/NetworkManager/system-connections/tun0-1eb1dbe8-5678-4818-9adf-fb2dc01ed132.nmconnection": keyfile writer produces an invalid connection: cannot access file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1998207/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
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 to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: New Bug description: 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- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003892] Re: libcap2 seems to not work correctly when linked with -Bsymbolic-functions
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 generated and the command chrpath in debian/rules will fail. -- 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/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: New Bug description: 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- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003892] [NEW] libcap2 seems to not work correctly when linked with -Bsymbolic-functions
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- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0 ** Affects: libcap2 (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- 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/2003892 Title: libcap2 seems to not work correctly when linked with -Bsymbolic- functions Status in libcap2 package in Ubuntu: New Bug description: 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- lunar/lunar/amd64/libc/libcap2/20230123_094238_95088@/log.gz The solution is to exclude this flag from the set of flags: debian/rules: export DEB_LDFLAGS_MAINT_STRIP = -Wl,-Bsymbolic-functions Debian seems to not be affected by that as they don't include this flag in their build: https://buildd.debian.org/status/fetch.php?pkg=libcap2=amd64=1%3A2.66-3=1671660323=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2003892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken
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 Jammy. So I suppose whatever was broken (maybe it fontforge?) was fixed in the version we use in Kinetic. A no-change build is probably enough to fix the issue on Kinetic and Lunar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Confirmed Status in gnome-font-viewer package in Ubuntu: Invalid Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken
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 Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Confirmed Status in gnome-font-viewer package in Ubuntu: Invalid Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---==> ii fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
