[Bug 2071949] Re: Missing frame pointers on Noble
** Attachment added: "buildlog_ubuntu-noble-amd64.ipvsadm_1_1.31-1ubuntu0.1~ppa1_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+attachment/5796624/+files/buildlog_ubuntu-noble-amd64.ipvsadm_1_1.31-1ubuntu0.1~ppa1_BUILDING.txt.gz ** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/ipvsadm/+git/ipvsadm/+merge/469312 ** Summary changed: - Missing frame pointers on Noble + [SRU] Missing frame pointers on Noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071949 Title: [SRU] Missing frame pointers on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071949] Re: Missing frame pointers on Noble
** Attachment added: "buildlog_ubuntu-noble-armhf.ipvsadm_1_1.31-1ubuntu0.1~ppa1_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+attachment/5796622/+files/buildlog_ubuntu-noble-armhf.ipvsadm_1_1.31-1ubuntu0.1~ppa1_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071949 Title: [SRU] Missing frame pointers on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071949] Re: Missing frame pointers on Noble
** Attachment added: "buildlog_ubuntu-noble-arm64.ipvsadm_1_1.31-1ubuntu0.1~ppa1_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+attachment/5796623/+files/buildlog_ubuntu-noble-arm64.ipvsadm_1_1.31-1ubuntu0.1~ppa1_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071949 Title: [SRU] Missing frame pointers on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071949] Re: Missing frame pointers on Noble
** Attachment added: "buildlog_ubuntu-noble-ppc64el.ipvsadm_1_1.31-1ubuntu0.1~ppa1_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+attachment/5796621/+files/buildlog_ubuntu-noble-ppc64el.ipvsadm_1_1.31-1ubuntu0.1~ppa1_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071949 Title: [SRU] Missing frame pointers on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071949] Re: Missing frame pointers on Noble
** Description changed: + [ Impact ] + + ipvsadm was not built with frame pointers in Noble. In fact, because + its build scripts are overriding the flags from package building framework, it's also + not built with hardening. + + Having frame pointers was one of the things we delivered with Noble and this is one + of the packages that are missing it. + + Note that this is already fixed in Debian and in Oracular. + + I pulled 3 commits from Debian for this SRU: + + 1) patch Makefiles to support build-flags + https://salsa.debian.org/pkg-netfilter-team/pkg-ipvsadm/-/commit/d066b671dc63fa8db402d0f8bc7d2ab3b655a30c + + 2) let dh manage build-flags + https://salsa.debian.org/pkg-netfilter-team/pkg-ipvsadm/-/commit/2058baf61b1ef2ea6fb7e54ce2f51cf13b10d827 + + 3) pass HAVE_NL=1 to make to enable libnl support + https://salsa.debian.org/pkg-netfilter-team/pkg-ipvsadm/-/commit/7bb81125d50aba2918be65c8d8d725f463437d26 + + [ Test Plan ] + + Unfortunately ipvsadm doesn't have any autopkgtests. I'm checking if it's still working + by running commands from its manual and checking they were installed. + + Here's how I tested it: + + Added a bunch of rules as found in ipvsadm(8) + + ipvsadm -A -t 207.175.44.110:80 -s rr + ipvsadm -a -t 207.175.44.110:80 -r 192.168.10.1:80 -m + ipvsadm -a -t 207.175.44.110:80 -r 192.168.10.2:80 -m + ipvsadm -a -t 207.175.44.110:80 -r 192.168.10.3:80 -m + ipvsadm -a -t 207.175.44.110:80 -r 192.168.10.4:80 -m + ipvsadm -a -t 207.175.44.110:80 -r 192.168.10.5:80 -m + + ipvsadm -A -f 1 -s rr + ipvsadm -a -f 1 -r 192.168.10.1:0 -m + ipvsadm -a -f 1 -r 192.168.10.2:0 -m + ipvsadm -a -f 1 -r 192.168.10.3:0 -m + ipvsadm -a -f 1 -r 192.168.10.4:0 -m + ipvsadm -a -f 1 -r 192.168.10.5:0 -m + + ipvsadm -A -t [2001:db8::80]:80 -s rr + ipvsadm -a -t [2001:db8::80]:80 -r [2001:db8::a0a0]:80 -m + + Check they were installed: + + ipvsadm -L -n + + Dump them to disk: + + ipvsadm-save -n > save + + Drop all the rules: + + ipvsadm -C + + Restore from disk: + + cat save | ipvsadm-restore + + Check again if they were installed: + + ipvsadm -L -n + + + [ Where problems could occur ] + + No source changes were made. Although, as it's now being built with hardening flags, such as + -fstack-protector-strong, -fstack-clash-protection and -D_FORTIFY_SOURCE=3, if the code has + any issues, such as buffer overflows, that were not causing crashes before, they will probably cause a + crash now. I don't see any bug report from Debian mentioning this kind of problem though. + + [ Other Info ] + + A PPA is provided here + https://launchpad.net/~danilogondolfo/+archive/ubuntu/ipvsadm/+packages + + Build logs are attached. + + + Old bug description + The compiler flags are being overwritten in the package Makefiles and it's not being built with none of $(dpkg-buildflags). This problem is already fixed in Oracular though. This package doesn't install any shared libraries. Related upstream fixes: https://salsa.debian.org/pkg-netfilter-team/pkg-ipvsadm/-/commit/d066b671dc63fa8db402d0f8bc7d2ab3b655a30c https://salsa.debian.org/pkg-netfilter-team/pkg-ipvsadm/-/commit/2058baf61b1ef2ea6fb7e54ce2f51cf13b10d827 ** Attachment added: "buildlog_ubuntu-noble-s390x.ipvsadm_1_1.31-1ubuntu0.1~ppa1_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+attachment/5796619/+files/buildlog_ubuntu-noble-s390x.ipvsadm_1_1.31-1ubuntu0.1~ppa1_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071949 Title: [SRU] Missing frame pointers on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071949] Re: Missing frame pointers on Noble
** Attachment added: "buildlog_ubuntu-noble-riscv64.ipvsadm_1_1.31-1ubuntu0.1~ppa1_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+attachment/5796620/+files/buildlog_ubuntu-noble-riscv64.ipvsadm_1_1.31-1ubuntu0.1~ppa1_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071949 Title: [SRU] Missing frame pointers on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071949] Re: Missing frame pointers on Noble
Hi Mitchell, yes I'll prepare an SRU for it :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071949 Title: Missing frame pointers on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071949] [NEW] Missing frame pointers on Noble
Public bug reported: The compiler flags are being overwritten in the package Makefiles and it's not being built with none of $(dpkg-buildflags). This problem is already fixed in Oracular though. This package doesn't install any shared libraries. Related upstream fixes: https://salsa.debian.org/pkg-netfilter-team/pkg-ipvsadm/-/commit/d066b671dc63fa8db402d0f8bc7d2ab3b655a30c https://salsa.debian.org/pkg-netfilter-team/pkg-ipvsadm/-/commit/2058baf61b1ef2ea6fb7e54ce2f51cf13b10d827 ** Affects: ipvsadm (Ubuntu) Importance: Undecided Status: New ** Affects: ipvsadm (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: ipvsadm (Ubuntu Noble) Importance: Undecided Status: New ** Description changed: The compiler flags are being overwritten in the package Makefiles and it's not being built with none of $(dpkg-buildflags). This problem is already fixed in Oracular though. This package doesn't install any shared libraries. + + Related upstream fixes: + https://salsa.debian.org/pkg-netfilter-team/pkg-ipvsadm/-/commit/d066b671dc63fa8db402d0f8bc7d2ab3b655a30c + https://salsa.debian.org/pkg-netfilter-team/pkg-ipvsadm/-/commit/2058baf61b1ef2ea6fb7e54ce2f51cf13b10d827 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071949 Title: Missing frame pointers on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2071333] Re: netplan.io causes systemctl enable to fail on systems without dbus
Hello, this is not caused by Netplan itself (but one of the things the update does will lead to the error). Below is a Dockerfile you can use to reproduce the problem. As you can see, netplan.io is not involved in it. FROM ubuntu:22.04 RUN apt-get update && apt-get install --yes --no-install-recommends \ systemd \ openssh-server ; mkdir /run/systemd/system RUN systemctl enable ssh Here is why it fails: The call to "systemctl enable ssh" gets redirected to "/lib/systemd/systemd-sysv-install enable ssh" which works, because the file "/etc/init.d/ssh" exists. "systemd-sysv-install" is a script that will call another script called "/usr/sbin/update-rc.d". This second script will check if /run/systemd/system exists and assume systemd is available if it does. Why it started to happen after the security update? One of the issues we fixed was a bad file permission we were using. To ensure that the permissions are set to the correct ones, the update calls the netplan generator to recreate the files. One of the things the generator does is create that directory. To workaround this you can just remove that directory before calling systemctl: FROM ubuntu:22.04 RUN apt-get update && apt-get install --yes --no-install-recommends \ systemd \ openssh-server \ netplan.io ; rm -rf /run/systemd/system RUN systemctl enable ssh ** Changed in: netplan.io (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2071333 Title: netplan.io causes systemctl enable to fail on systems without dbus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2071333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069293] Re: Autopkgtests failing due to new git 2.45
** Changed in: git (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069293 Title: Autopkgtests failing due to new git 2.45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/2069293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069304] Re: Autopkgtests failing due to new git 2.45
** Changed in: git (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069304 Title: Autopkgtests failing due to new git 2.45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/git/+bug/2069304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069293] Re: Autopkgtests failing due to new git 2.45
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/ikiwiki-hosting/+git/ikiwiki-hosting/+merge/467474 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069293 Title: Autopkgtests failing due to new git 2.45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ikiwiki-hosting/+bug/2069293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069304] [NEW] Autopkgtests failing due to new git 2.45
Public bug reported: The test is failing due to the message bellow being sent to stderr: 1491s autopkgtest [17:08:48]: test test-dh-gnulib-patch: ---] 1491s test-dh-gnulib-patch FAIL stderr: hint: Using 'master' as the name for the initial branch. This default branch name 1491s autopkgtest [17:08:48]: test test-dh-gnulib-patch: - - - - - - - - - - results - - - - - - - - - - 1491s autopkgtest [17:08:48]: test test-dh-gnulib-patch: - - - - - - - - - - stderr - - - - - - - - - - 1491s hint: Using 'master' as the name for the initial branch. This default branch name 1491s hint: is subject to change. To configure the initial branch name to use in all 1491s hint: of your new repositories, which will suppress this warning, call: 1491s hint: 1491s hint: git config --global init.defaultBranch 1491s hint: 1491s hint: Names commonly chosen instead of 'master' are 'main', 'trunk' and 1491s hint: 'development'. The just-created branch can be renamed via this command: 1491s hint: 1491s hint: git branch -m 1491s autopkgtest [17:08:48]: summary 1491s test-dh-gnulib-patch FAIL stderr: hint: Using 'master' as the name for the initial branch. This default branch name ** Affects: gnulib (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069304 Title: Autopkgtests failing due to new git 2.45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnulib/+bug/2069304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069293] Re: Autopkgtests failing due to new git 2.45
** Description changed: The step where the ikiwiki-hosting managed git repository is cloned is failing: git clone git://foo.example.com/source.git Cloning into 'source'... fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. The reason is that the new git doesn't trust it: 2024-06-13T12:06:08.678455+00:00 autopkgtest-lxd-xukspx git-daemon[7458]: [7458] Interpolated dir '/var/lib/ikiwiki-hosting-web/git/foo.example.com' 2024-06-13T12:06:08.678481+00:00 autopkgtest-lxd-xukspx git-daemon[7458]: fatal: detected dubious ownership in repository at '/var/lib/ikiwiki-hosting-web/git/foo.example.com.git' 2024-06-13T12:06:08.678504+00:00 autopkgtest-lxd-xukspx git-daemon[7458]: To add an exception for this directory, call: 2024-06-13T12:06:08.678526+00:00 autopkgtest-lxd-xukspx git-daemon[7458]: #011git config --global --add safe.directory /var/lib/ikiwiki-hosting-web/git/foo.example.com.git - - I suspect that this change in behavior is related to recent git CVEs: https://github.blog/2024-05-14-securing-git-addressing-5-new-vulnerabilities/ + I suspect that this change in behavior is related to recent git CVEs: + https://github.blog/2024-05-14-securing-git-addressing-5-new- + vulnerabilities/. More specifically this one + https://github.com/git/git/security/advisories/GHSA-xfc6-vwr8-r389 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069293 Title: Autopkgtests failing due to new git 2.45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ikiwiki-hosting/+bug/2069293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069293] [NEW] Autopkgtests failing due to new git 2.45
Public bug reported: The step where the ikiwiki-hosting managed git repository is cloned is failing: git clone git://foo.example.com/source.git Cloning into 'source'... fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. The reason is that the new git doesn't trust it: 2024-06-13T12:06:08.678455+00:00 autopkgtest-lxd-xukspx git-daemon[7458]: [7458] Interpolated dir '/var/lib/ikiwiki-hosting-web/git/foo.example.com' 2024-06-13T12:06:08.678481+00:00 autopkgtest-lxd-xukspx git-daemon[7458]: fatal: detected dubious ownership in repository at '/var/lib/ikiwiki-hosting-web/git/foo.example.com.git' 2024-06-13T12:06:08.678504+00:00 autopkgtest-lxd-xukspx git-daemon[7458]: To add an exception for this directory, call: 2024-06-13T12:06:08.678526+00:00 autopkgtest-lxd-xukspx git-daemon[7458]: #011git config --global --add safe.directory /var/lib/ikiwiki-hosting-web/git/foo.example.com.git I suspect that this change in behavior is related to recent git CVEs: https://github.blog/2024-05-14-securing-git-addressing-5-new-vulnerabilities/ ** Affects: ikiwiki-hosting (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069293 Title: Autopkgtests failing due to new git 2.45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ikiwiki-hosting/+bug/2069293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069110] Re: netplan breaks route_localnet set in /proc/sys/net/ipv4/conf after apply/try
*** This bug is a duplicate of bug 2069111 *** https://bugs.launchpad.net/bugs/2069111 ** This bug has been marked a duplicate of bug 2069111 netplan breaks route_localnet set in /proc/sys/net/ipv4/conf after apply/try -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069110 Title: netplan breaks route_localnet set in /proc/sys/net/ipv4/conf after apply/try To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/2069110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066700] Re: systemd-networkd is inactive by default since ubuntu 23.10?
If no renderer is set anywhere in your YAMLs it will default to networkd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066700 Title: systemd-networkd is inactive by default since ubuntu 23.10? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2066700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063094] Re: unattended-upgrades is running forever
Calling "strace" and "perf record" against the process would also help debugging it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063094 Title: unattended-upgrades is running forever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2063094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059292] Re: autopkgtest failure with libvmod-redis/15.1-1build2 on arm64
** Changed in: libvmod-redis (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059292 Title: autopkgtest failure with libvmod-redis/15.1-1build2 on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvmod-redis/+bug/2059292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865283] Re: gnome calendar icon missing Ubuntu 20.04
No icon on Gnome Calendar snap. I'm using ubuntu 24.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865283 Title: gnome calendar icon missing Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1865283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: Backport iproute2 6.8.0 to noble
Hi folks, do you think we are good to sync iproute2 from Debian to Oracular at this point? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: Backport iproute2 6.8.0 to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862481] Re: Cannot set accept-ra to 2, it keeps reseting it to 0
I was looking at this bug while working on another accept-ra related thing and found this: As far as I can tell, networkd will always set the per-interface accept_ra parameter to 0: https://github.com/systemd/systemd/blob/v255/src/network/networkd- sysctl.c#L146 The explanation for that is documented in an old version of this code (which was moved from networkd-link.c to networkd-sysctl.c): https://github.com/systemd/systemd/blob/v241/src/network/networkd- link.c#L2609 It's also described in different words on systemd.network(5): Note that kernel's implementation of the IPv6 RA protocol is always disabled, regardless of this setting. If this option is enabled, a userspace implementation of the IPv6 RA protocol is used, and the kernel's own implementation remains disabled... The Netplan documentation need to be updated. It currently says "If unset use the host kernel default setting" but, at least when networkd is used, the "default" will always be disabled because networkd itself will force it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862481 Title: Cannot set accept-ra to 2, it keeps reseting it to 0 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1862481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063973] Re: network-online.target is reached before netplan-configured interfaces are online
Hi Lucas, In your scenario the best approach would probably be relying on Netplan to rename the interface for you instead of creating an external udev rule. I'd suggest you use "set-name: eno1" and continue to use "match" in your configuration. Something like this: ``` network: version: 2 renderer: networkd ethernets: eno1np0: dhcp4: true match: macaddress: 98:03:9b:b0:a7:76 set-name: eno1 ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063973 Title: network-online.target is reached before netplan-configured interfaces are online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2063973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058179 Title: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058179 Title: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058179 Title: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060818] Re: FTBFS on Noble
stack trace after installing llvm-symbolizer ** Attachment added: "swift_crash_arm64.txt" https://bugs.launchpad.net/ubuntu/+source/swiftlang/+bug/2060818/+attachment/5766081/+files/swift_crash_arm64.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060818 Title: FTBFS on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swiftlang/+bug/2060818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060818] Re: FTBFS on Noble
With a few patches I got it working on amd64. The build fails on arm64 though, the swift compiler itself crashes during the build and the problem appears to be in the vendored LLVM 13 code. I put it in a PPA here https://launchpad.net/~danilogondolfo/+archive/ubuntu/swiftlang -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060818 Title: FTBFS on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swiftlang/+bug/2060818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2055333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060818] Re: FTBFS on Noble
** Tags added: ftbfs update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060818 Title: FTBFS on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swiftlang/+bug/2060818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060818] [NEW] FTBFS on Noble
Public bug reported: Source package is failing to build for different reasons: 1) - -- Check for working C compiler: /<>/build/buildbot_linux/llvm-linux-x86_64/./bin/clang -- Check for working C compiler: /<>/build/buildbot_linux/llvm-linux-x86_64/./bin/clang - broken CMake Error at /usr/share/cmake-3.28/Modules/CMakeTestCCompiler.cmake:67 (message): The C compiler "/<>/build/buildbot_linux/llvm- linux-x86_64/./bin/clang" is not able to compile a simple test program. It fails with the following output: Change Dir: '/<>/build/buildbot_linux/llvm-linux-x86_64/tools/clang/runtime/compiler-rt-bins/CMakeFiles/CMakeScratch/TryCompile-k2BXY5' Run Build Command(s): /usr/bin/ninja -v cmTC_45db0 [1/2][ 50%][0.017s] /<>/build/buildbot_linux/llvm-linux-x86_64/./bin/clang -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/<>=/usr/src/swiftlang-5.6.3-3 -MD -MT CMakeFiles/cmTC_45db0.dir/testCCompiler.c.o -MF CMakeFiles/cmTC_45db0.dir/testCCompiler.c.o.d -o CMakeFiles/cmTC_45db0.dir/testCCompiler.c.o -c /<>/build/buildbot_linux/llvm-linux-x86_64/tools/clang/runtime/compiler-rt-bins/CMakeFiles/CMakeScratch/TryCompile-k2BXY5/testCCompiler.c clang-13: warning: optimization flag '-ffat-lto-objects' is not supported [-Wignored-optimization-argument] [2/2][100%][0.029s] : && /<>/build/buildbot_linux/llvm-linux-x86_64/./bin/clang -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/<>=/usr/src/swiftlang-5.6.3-3 -Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -Wl,-z,relro CMakeFiles/cmTC_45db0.dir/testCCompiler.c.o -o cmTC_45db0 && : FAILED: cmTC_45db0 : && /<>/build/buildbot_linux/llvm-linux-x86_64/./bin/clang -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/<>=/usr/src/swiftlang-5.6.3-3 -Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -Wl,-z,relro CMakeFiles/cmTC_45db0.dir/testCCompiler.c.o -o cmTC_45db0 && : /usr/bin/ld: /<>/build/buildbot_linux/llvm-linux-x86_64/bin/../lib/LLVMgold.so: error loading plugin: /<>/build/buildbot_linux/llvm-linux-x86_64/bin/../lib/LLVMgold.so: cannot open shared object file: No such file or directory clang-13: error: linker command failed with exit code 1 (use -v to see invocation) ninja: build stopped: subcommand failed. - This issue can be workaround by disabling LTO. With LTO disabled, the build will proceed and fail to due strlcat and strlcpy, which the upstream project implements and are now also present in the new glibc. ** Affects: swiftlang (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060818 Title: FTBFS on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/swiftlang/+bug/2060818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060241 Title: prosposed migration audit 1:3.1.2-2.1build1 vs network-manager 1.46.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/2060241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059651 Title: network-manager gets uninstalled on apt full-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2059651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059415] Re: netplan crash when using command netplan
Thanks for the information. The crash you mentioned you were getting on Jammy, is that the same crash you reported? Did you manually upgrade netplan to 0.107 on Jammy for any chance? So, after upgrading to 0.107.1, the directory /usr/share/netplan/netplan should have been removed (or at least all the .py files should've been removed). The code from this directory was moved to the package python3-netplan, which you have installed. Try to rename this directory to something like /usr/share/netplan/netplan.old and try netplan again, it should fix the issue for you. Then you can just delete it. It's not clear to me yet how all the .py files from this directory were left behind... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059415 Title: netplan crash when using command netplan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2059415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059415] Re: netplan crash when using command netplan
Hello, can you explain how you got to this situation? Have you upgraded your system from Jammy to Noble? Can you paste the output of "dpkg --list | grep netplan", please? Can you also paste the output of "find /usr/share/netplan/netplan/"? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059415 Title: netplan crash when using command netplan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2059415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2053228] Re: software-properties-gtk does not start
For me it still not working, or it takes a while to be added to the updates? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2053228 Title: software-properties-gtk does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059299] [NEW] Autopkgtest failing on amd64 with "_FORTIFY_SOURCE redefined"
Public bug reported: autopkgtest [13:54:07]: test hello: [--- 833s info: compiling 833s : warning: "_FORTIFY_SOURCE" redefined 833s : note: this is the location of the previous definition 833s info: running 833s HELLO, WORLD 833s success: Able to run hello world program 834s autopkgtest [13:54:08]: test hello: ---] 834s helloFAIL stderr: : warning: "_FORTIFY_SOURCE" redefined 834s autopkgtest [13:54:08]: test hello: - - - - - - - - - - results - - - - - - - - - - 834s autopkgtest [13:54:08]: test hello: - - - - - - - - - - stderr - - - - - - - - - - 834s : warning: "_FORTIFY_SOURCE" redefined 834s : note: this is the location of the previous definition ** Affects: gnucobol3 (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059299 Title: Autopkgtest failing on amd64 with "_FORTIFY_SOURCE redefined" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucobol3/+bug/2059299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059131] Re: slurmdbd segfaults on armhf
I've got the (non-flaky) tests passing autopkgtest [10:47:08]: summary srun PASS sbatch FLAKY non-zero exit status 1 sacctPASS mpi PASS but the patch is getting ridiculous... I had to patch %ld -> %lld in 42 files. As I'm not changing the variable types, they will warn in non- armhf architectures as time_t is not a long long int there. In the end they have the same size but still... I'm inclined to request a binary package removal on armhf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059131 Title: slurmdbd segfaults on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slurm-wlm/+bug/2059131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059131] Re: slurmdbd segfaults on armhf
** Attachment added: "build log on armhf" https://bugs.launchpad.net/ubuntu/+source/slurm-wlm/+bug/2059131/+attachment/5759741/+files/buildlog_ubuntu-noble-armhf.slurm-wlm_23.11.4-1.2ubuntu6~ppa1_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059131 Title: slurmdbd segfaults on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slurm-wlm/+bug/2059131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059131] Re: slurmdbd segfaults on armhf
There are lots of instances of this issue. After fixing the one above it breaks in a different place root@autopkgtest-lxd-bqwqyd:~# slurmdbd -D slurmdbd: accounting_storage/as_mysql: _check_mysql_concat_is_sane: MySQL server version is: 5.5.5-10.11.7-MariaDB-2ubuntu1 slurmdbd: error: Database settings not recommended values: innodb_buffer_pool_size innodb_lock_wait_timeout slurmdbd: error: mysql_query failed: 167 Out of range value for column 'id' at row 3 insert into tres_table (creation_time, id, deleted, type) values (1711475131, 0, 0, 'cpu'), (1, -140242792, 0, 'mem'), (1711475131, 0, 0, 'energy'), (2, 0, 0, 'node'), (1711475131, 0, 0, 'billing'), (3, 0, 0, 'vmem'), (1711475131, 0, 0, 'pages'), (4, 0, 1, 'dynamic_offset') on duplicate key update deleted=VALUES(deleted), type=VALUES(type), id=VALUES(id); slurmdbd: fatal: problem adding static tres -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059131 Title: slurmdbd segfaults on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slurm-wlm/+bug/2059131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059131] Re: slurmdbd segfaults on armhf
The problem is the format string using %ld with the new time_t in armhf,
now it's long long int (%lld)...
query2 = xstrdup_printf("insert into %s (creation_time, "
"mod_time, table_name, definition) "
"values (%ld, %ld, '%s', '%s') "
"on duplicate key update "
"definition='%s', mod_time=%ld;",
table_defs_table, now, now,
table_name, quoted,
quoted, now);
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059131
Title:
slurmdbd segfaults on armhf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/slurm-wlm/+bug/2059131/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059131] Re: slurmdbd segfaults on armhf
The variable "now" used in xstrdup_printf is defined as "time_t now = time(NULL);" h -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059131 Title: slurmdbd segfaults on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slurm-wlm/+bug/2059131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059131] [NEW] slurmdbd segfaults on armhf
Public bug reported: The slurmdbd segfaults on armhf. This is from the autopkgtest logs: 613s × slurmdbd.service - Slurm DBD accounting daemon 613s Loaded: loaded (/usr/lib/systemd/system/slurmdbd.service; enabled; preset: enabled) 613s Active: failed (Result: core-dump) since Tue 2024-03-26 09:13:24 UTC; 19s ago 613sDuration: 627ms 613sDocs: man:slurmdbd(8) 613s Process: 3801 ExecStart=/usr/sbin/slurmdbd -D -s $SLURMDBD_OPTIONS (code=dumped, signal=SEGV) 613sMain PID: 3801 (code=dumped, signal=SEGV) 613s CPU: 28ms 613s 613s Mar 26 09:13:23 autopkgtest-lxd-kbbzor systemd[1]: Started slurmdbd.service - Slurm DBD accounting daemon. 613s Mar 26 09:13:23 autopkgtest-lxd-kbbzor (slurmdbd)[3801]: slurmdbd.service: Referenced but unset environment variable evaluates to an empty string: SLURMDBD_OPTIONS 613s Mar 26 09:13:23 autopkgtest-lxd-kbbzor slurmdbd[3801]: slurmdbd: error: Unable to open pidfile `/run/slurmdbd.pid': Permission denied 613s Mar 26 09:13:23 autopkgtest-lxd-kbbzor slurmdbd[3801]: slurmdbd: Not running as root. Can't drop supplementary groups 613s Mar 26 09:13:23 autopkgtest-lxd-kbbzor slurmdbd[3801]: slurmdbd: accounting_storage/as_mysql: _check_mysql_concat_is_sane: MySQL server version is: 5.5.5-10.11.7-MariaDB-2ubuntu1 613s Mar 26 09:13:23 autopkgtest-lxd-kbbzor slurmdbd[3801]: slurmdbd: error: Database settings not recommended values: innodb_buffer_pool_size innodb_lock_wait_timeout 613s Mar 26 09:13:24 autopkgtest-lxd-kbbzor systemd[1]: slurmdbd.service: Main process exited, code=dumped, status=11/SEGV 613s Mar 26 09:13:24 autopkgtest-lxd-kbbzor systemd[1]: slurmdbd.service: Failed with result 'core-dump'. 614s autopkgtest [09:13:44]: test sacct: ---] 617s sacctFAIL non-zero exit status 3 Trying to run the binary in an armhf LXD container also fails: root@autopkgtest-lxd-gzeypl:/tmp/autopkgtest.VdD4R7/build.sTW/src# slurmdbd -D slurmdbd: accounting_storage/as_mysql: _check_mysql_concat_is_sane: MySQL server version is: 5.5.5-10.11.7-MariaDB-2ubuntu1 slurmdbd: error: Database settings not recommended values: innodb_buffer_pool_size innodb_lock_wait_timeout Segmentation fault The database settings error seems to not be related as they are also happening on other archtectures. Running on gdb I get the following stack trace: (gdb) bt #0 __GI_strlen () at ../sysdeps/arm/armv6t2/strlen.S:126 #1 0xf7d8927a in __printf_buffer (buf=buf@entry=0xfffee780, format=, ap=..., mode_flags=mode_flags@entry=2) at vfprintf-process-arg.c:435 #2 0xf7d9cd26 in __vsnprintf_internal (string=, maxlen=maxlen@entry=100, format=, args=..., args@entry=..., mode_flags=2) at vsnprintf.c:96 #3 0xf7e02bba in ___vsnprintf_chk (s=, maxlen=maxlen@entry=100, flag=flag@entry=2, slen=slen@entry=4294967295, format=, ap=...) at vsnprintf_chk.c:34 #4 0xf7f62f2a in vsnprintf (__ap=..., __fmt=0xf7c6dc4c "insert into %s (creation_time, mod_time, table_name, definition) values (%ld, %ld, '%s', '%s') on duplicate key update definition='%s', mod_time=%ld;", __n=100, __s=) at /usr/include/arm-linux-gnueabihf/bits/stdio2.h:68 #5 _xstrdup_vprintf (str=str@entry=0xfffee87c, fmt=fmt@entry=0xf7c6dc4c "insert into %s (creation_time, mod_time, table_name, definition) values (%ld, %ld, '%s', '%s') on duplicate key update definition='%s', mod_time=%ld;", ap=ap@entry=...) at ../../../src/common/xstring.c:799 #6 0xf7f6384c in xstrdup_printf (fmt=0xf7c6dc4c "insert into %s (creation_time, mod_time, table_name, definition) values (%ld, %ld, '%s', '%s') on duplicate key update definition='%s', mod_time=%ld;") at ../../../src/common/xstring.c:511 #7 0xf7c58ed4 in _mysql_make_table_current (ending=, fields=0x0, table_name=0xf7c60020 "convert_version_table", mysql_conn=0x415468) at ../../../src/database/mysql_common.c:667 #8 mysql_db_create_table (mysql_conn=mysql_conn@entry=0x415468, table_name=0xf7c60020 "convert_version_table", fields=, fields@entry=0xf7c5f220, ending=) at ../../../src/database/mysql_common.c:1190 #9 0xf7c238f6 in _as_mysql_acct_check_tables (mysql_conn=0x0) at ../../../../../src/plugins/accounting_storage/mysql/accounting_storage_mysql.c:887 #10 init () at ../../../../../src/plugins/accounting_storage/mysql/accounting_storage_mysql.c:2892 #11 0xf7eebcae in plugin_load_from_file (p=0xfffeef80, p@entry=0xfffeefb0, fq_path=) at ../../../src/common/plugin.c:173 #12 0xf7eebec6 in plugin_load_and_link (type_name=, n_syms=0, n_syms@entry=80, names=0x0, names@entry=0xf7fca01c , ptrs=0x1, ptrs@entry=0xf7fccf44 ) at ../../../src/common/plugin.c:233 #13 0xf7eec038 in plugin_context_create (plugin_type=plugin_type@entry=0xf7fb392c "accounting_storage", uler_type=, ptrs=ptrs@entry=0xf7fccf44 , names=0xf7fca01c , names_size=names_size@entry=320) at ../../../src/common/plugin.c:364 #14 0xf7f64114 in acct_storage_g_init () at ../../../src/interfaces/accounting_storage.c:345 #15 0x00404460 in
[Bug 2058031] Re: [SRU] Backport 0.107.1-3 to Ubuntu 22.04
Autopkgtests from Jammy. See the description above for an explanation about why there are test failures. ** Attachment added: "jammy-autopkgtest-logs.tar" https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058031/+attachment/5758414/+files/jammy-autopkgtest-logs.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058031 Title: [SRU] Backport 0.107.1-3 to Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058051] Re: [SRU] Backport 0.107.1-3 to Ubuntu 23.10
** Changed in: netplan.io (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058051 Title: [SRU] Backport 0.107.1-3 to Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058031] Re: [SRU] Backport 0.107.1-3 to Ubuntu 22.04
** Changed in: netplan.io (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058031 Title: [SRU] Backport 0.107.1-3 to Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058051] Re: [SRU] Backport 0.107.1-3 to Ubuntu 23.10
** Description changed: + Stable Release Update for netplan.io 0.107.1-3 to Mantic. This version + has many bug fixes and new features we want to make available to users + of Ubuntu 23.10. netplan.io has an SRU exception for backporting new + versions with new features https://wiki.ubuntu.com/NetplanUpdates + Another SRU, for Jammy, was prepared in a separate LP bug: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058031. As the package is slightly different (due to backwards compatibility patches) and on Mantic we have the integration with Network Manager (which can cause different problems and requires more tests) I thought it would be more appropriate to work on the Mantic SRU in a different LP bug. [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: In terms of new features there were not big changes. The changes below though will cause backwards compatibility issues if the user upgrades to the new version of netplan.io, starts to use the new features and then decides to downgrade for some reason: * wifi: add support for WPA3-Enterprise - https://github.com/canonical/netplan/pull/402 - https://bugs.launchpad.net/netplan/+bug/2029876 + https://github.com/canonical/netplan/pull/402 + https://bugs.launchpad.net/netplan/+bug/2029876 * wifi: make it possible to have a psk and an eap password simultaneously - https://github.com/canonical/netplan/pull/416 + https://github.com/canonical/netplan/pull/416 * parse: allow COMMON_LINK_HANDLERS for VRFs - https://github.com/canonical/netplan/pull/401 + https://github.com/canonical/netplan/pull/401 The change below generates a different backend configuration for wpa-supplicant. Although is will not cause major backwards compatibility problems: * wifi: support WPA2 and WPA3 Personal simultaneously https://github.com/canonical/netplan/pull/404 In addition to all the changes from netplan.io 0.107.1-3, a couple of bug fixes were imported from netplan.io 1.0-1: * debian/patches/lp2041727: Check if ovsdb-server.service is active before displaying warning - https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041727 - https://github.com/canonical/netplan/pull/421 - - This fixes an annoying warning message that many users were seeing + https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041727 + https://github.com/canonical/netplan/pull/421 + + This fixes an annoying warning message that many users were seeing when they call "netplan apply". * d/p/0004-tests-assert-generated-.service-files-in-assert_srio.patch, d/p/0005-tests-sriov-test-if-the-generated-netplan-rebind-ser.patch, d/p/0006-sriov-don-t-generate-duplicate-entries-in-the-rebind.patch: Don't generate duplicate entries in the netplan-sriov-rebind.service - https://github.com/canonical/netplan/pull/437 - - This fixes a duplication problem where "netplan rebind" could process + https://github.com/canonical/netplan/pull/437 + + This fixes a duplication problem where "netplan rebind" could process the same SR-IOV interface multiple times. See the changelog entry below for a full list of changes and bugs. [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. Testing netplan upgrade 1) Launch a Mantic LXD VM lxc launch ubuntu:mantic mantic-vm --vm lxc shell mantic-vm 2) Check Netplan works netplan get netplan apply 3) Install Network Manager so we can test the netplan-everywhere integration apt update apt install network-manager 4) Change the default renderer to NetworkManager in /etc/netplan/50-cloud-init.yaml network: renderer: NetworkManager version: 2 ethernets: enp5s0: dhcp4: true 5) Apply the configuration netplan apply nmcli con show 6) Add a new connection with nmcli nmcli con add type dummy ifname dummy0 7) Check that a new 'dummy-device' is present in Netplan netplan get 8) Add the PPA with the new package add-apt-repository ppa:danilogondolfo/netplan-sru apt update ; apt -y upgrade 9) Restart Network Manager so it will load the new libnetplan systemctl restart NetworkManager 10) Add a new interface using nmcli
[Bug 2058051] Re: [SRU] Backport 0.107.1-3 to Ubuntu 23.10
** Description changed: Another SRU, for Jammy, was prepared in a separate LP bug: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058031. As the package is slightly different (due to backwards compatibility patches) and on Mantic we have the integration with Network Manager (which can cause different problems and requires more tests) I thought it would be more appropriate to work on the Mantic SRU in a different LP bug. [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: - * + In terms of new features there were not big changes. + The changes below though will cause backwards compatibility issues if the + user upgrades to the new version of netplan.io, starts to use the new features and + then decides to downgrade for some reason: + + * wifi: add support for WPA3-Enterprise + https://github.com/canonical/netplan/pull/402 + https://bugs.launchpad.net/netplan/+bug/2029876 + + * wifi: make it possible to have a psk and an eap password simultaneously + https://github.com/canonical/netplan/pull/416 + + * parse: allow COMMON_LINK_HANDLERS for VRFs + https://github.com/canonical/netplan/pull/401 + + The change below generates a different backend configuration for + wpa-supplicant. Although is will not cause major backwards compatibility + problems: + + * wifi: support WPA2 and WPA3 Personal simultaneously + https://github.com/canonical/netplan/pull/404 + + In addition to all the changes from netplan.io 0.107.1-3, a couple of + bug fixes were imported from netplan.io 1.0-1: + + * debian/patches/lp2041727: Check if ovsdb-server.service is active before displaying warning + https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041727 + https://github.com/canonical/netplan/pull/421 + + This fixes an annoying warning message that many users were seeing + when they call "netplan apply". + + * d/p/0004-tests-assert-generated-.service-files-in-assert_srio.patch, d/p/0005-tests-sriov-test-if-the-generated-netplan-rebind-ser.patch, d/p/0006-sriov-don-t-generate-duplicate-entries-in-the-rebind.patch: Don't generate duplicate entries in the netplan-sriov-rebind.service + https://github.com/canonical/netplan/pull/437 + + This fixes a duplication problem where "netplan rebind" could process + the same SR-IOV interface multiple times. See the changelog entry below for a full list of changes and bugs. [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. Testing netplan upgrade 1) Launch a Mantic LXD VM lxc launch ubuntu:mantic mantic-vm --vm lxc shell mantic-vm 2) Check Netplan works netplan get netplan apply 3) Install Network Manager so we can test the netplan-everywhere integration apt update apt install network-manager 4) Change the default renderer to NetworkManager in /etc/netplan/50-cloud-init.yaml network: renderer: NetworkManager version: 2 ethernets: enp5s0: dhcp4: true 5) Apply the configuration netplan apply nmcli con show 6) Add a new connection with nmcli nmcli con add type dummy ifname dummy0 7) Check that a new 'dummy-device' is present in Netplan netplan get 8) Add the PPA with the new package add-apt-repository ppa:danilogondolfo/netplan-sru apt update ; apt -y upgrade 9) Restart Network Manager so it will load the new libnetplan systemctl restart NetworkManager 10) Add a new interface using nmcli nmcli con add type dummy ifname dummy1 11) Check it will show up in the Netplan configuration netplan get 12) Delete both of the new connections nmcli con del dummy-dummy0 nmcli con del dummy-dummy1 13) Check they are gone netplan get [Where problems could occur] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. Regressions in this update could potentially impact the generation of networking configuration and also Network Manager. Note that all the autopkgtests for both netplan.io and network-manager don't show any regression. Also, this version of netplan.io was present in Noble for a few months now and no regressions were reported. [Other Info] -
[Bug 2058051] Re: [SRU] Backport 0.107.1-3 to Ubuntu 23.10
Attaching autopkgtest logs from netplan.io and network-manager tests. ** Attachment added: "mantic-autopkgtest-logs.tar" https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058051/+attachment/5758327/+files/mantic-autopkgtest-logs.tar ** Description changed: Another SRU, for Jammy, was prepared in a separate LP bug: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058031. As the package is slightly different (due to backwards compatibility patches) and on Mantic we have the integration with Network Manager (which can cause different problems and requires more tests) I thought it would be more appropriate to work on the Mantic SRU in a different LP bug. [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * See the changelog entry below for a full list of changes and bugs. [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. Testing netplan upgrade - 1) Launch a Mantic LXD VM lxc launch ubuntu:mantic mantic-vm --vm lxc shell mantic-vm - 2) Check Netplan works netplan get netplan apply 3) Install Network Manager so we can test the netplan-everywhere integration apt update apt install network-manager 4) Change the default renderer to NetworkManager in /etc/netplan/50-cloud-init.yaml network: - renderer: NetworkManager - version: 2 - ethernets: - enp5s0: - dhcp4: true - + renderer: NetworkManager + version: 2 + ethernets: + enp5s0: + dhcp4: true + 5) Apply the configuration netplan apply nmcli con show 6) Add a new connection with nmcli nmcli con add type dummy ifname dummy0 7) Check that a new 'dummy-device' is present in Netplan netplan get 8) Add the PPA with the new package add-apt-repository ppa:danilogondolfo/netplan-sru apt update ; apt -y upgrade 9) Restart Network Manager so it will load the new libnetplan systemctl restart NetworkManager 10) Add a new interface using nmcli nmcli con add type dummy ifname dummy1 11) Check it will show up in the Netplan configuration netplan get 12) Delete both of the new connections nmcli con del dummy-dummy0 nmcli con del dummy-dummy1 13) Check they are gone netplan get - [Where problems could occur] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. - + Regressions in this update could potentially impact the generation of + networking configuration and also Network Manager. Note that all the + autopkgtests for both netplan.io and network-manager don't show any + regression. Also, this version of netplan.io was present in Noble for a + few months now and no regressions were reported. [Other Info] - + [Changelog] * Backport netplan.io 0.107.1-3 to 23.10 (LP: #2058051): - wifi: add support for WPA3-Enterprise (LP: #2029876) (!402) - wifi: support WPA2 and WPA3 Personal simultaneously (!404) - added mii-monitor-interval example (!411) - docs: Add "Contribute Documentation" how-to - auth: add support for LEAP and EAP-PWD (!415) - tests: Add autopkgtest for (LP: #1959570) (!419) - wifi: make it possible to have a psk and an eap password simultaneously (!416) - doc: Set-up some basic Doxygen project (!423) - doc: Make Sphinx to handle autodoxygen project, using breathe (!423) - doc: create libnetplan apidoc structure (!423) - inc: Start documenting public API (!423) - doc: Update 'Netplan everywhere' for 23.10 (!418) Bug fixes: - test:ovs: Avoid NetworkManager taking contol, breaking a test - parse: allow COMMON_LINK_HANDLERS for VRFs (!401) - util: don't return a placeholder netdef in the iterator (!406) - tunnels/validation: do not error out if "local" is not defined (!407) - tests: add some integration tests without the local address (!407) - wireguard: ignore empty endpoints (LP: #2038811) (!414) - parse: improve the parsing of access-points (LP: #1809994) (!413) - wifi: replace the previously defined AP with the new one (!413) - doc: spelling check improvements (!417) - Fix
[Bug 2058051] Re: [SRU] Backport 0.107.1-3 to Ubuntu 23.10
** Description changed: Another SRU, for Jammy, was prepared in a separate LP bug: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058031. As the package is slightly different (due to backwards compatibility patches) and on Mantic we have the integration with Network Manager (which can cause different problems and requires more tests) I thought it would be more appropriate to work on the Mantic SRU in a different LP bug. [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * See the changelog entry below for a full list of changes and bugs. [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. + + Testing netplan upgrade + + + 1) Launch a Mantic LXD VM + + lxc launch ubuntu:mantic mantic-vm --vm + lxc shell mantic-vm + + + 2) Check Netplan works + netplan get + netplan apply + + 3) Install Network Manager so we can test the netplan-everywhere + integration + + apt update + apt install network-manager + + 4) Change the default renderer to NetworkManager in + /etc/netplan/50-cloud-init.yaml + + network: + renderer: NetworkManager + version: 2 + ethernets: + enp5s0: + dhcp4: true + + 5) Apply the configuration + + netplan apply + nmcli con show + + 6) Add a new connection with nmcli + + nmcli con add type dummy ifname dummy0 + + 7) Check that a new 'dummy-device' is present in Netplan + + netplan get + + 8) Add the PPA with the new package + + add-apt-repository ppa:danilogondolfo/netplan-sru + + apt update ; apt -y upgrade + + 9) Restart Network Manager so it will load the new libnetplan + + systemctl restart NetworkManager + + 10) Add a new interface using nmcli + + nmcli con add type dummy ifname dummy1 + + 11) Check it will show up in the Netplan configuration + + netplan get + + 12) Delete both of the new connections + + nmcli con del dummy-dummy0 + nmcli con del dummy-dummy1 + + 13) Check they are gone + + netplan get + [Where problems could occur] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. [Other Info] [Changelog] * Backport netplan.io 0.107.1-3 to 23.10 (LP: #2058051): - wifi: add support for WPA3-Enterprise (LP: #2029876) (!402) - wifi: support WPA2 and WPA3 Personal simultaneously (!404) - added mii-monitor-interval example (!411) - docs: Add "Contribute Documentation" how-to - auth: add support for LEAP and EAP-PWD (!415) - tests: Add autopkgtest for (LP: #1959570) (!419) - wifi: make it possible to have a psk and an eap password simultaneously (!416) - doc: Set-up some basic Doxygen project (!423) - doc: Make Sphinx to handle autodoxygen project, using breathe (!423) - doc: create libnetplan apidoc structure (!423) - inc: Start documenting public API (!423) - doc: Update 'Netplan everywhere' for 23.10 (!418) Bug fixes: - test:ovs: Avoid NetworkManager taking contol, breaking a test - parse: allow COMMON_LINK_HANDLERS for VRFs (!401) - util: don't return a placeholder netdef in the iterator (!406) - tunnels/validation: do not error out if "local" is not defined (!407) - tests: add some integration tests without the local address (!407) - wireguard: ignore empty endpoints (LP: #2038811) (!414) - parse: improve the parsing of access-points (LP: #1809994) (!413) - wifi: replace the previously defined AP with the new one (!413) - doc: spelling check improvements (!417) - Fix permissions on folder '/run/NetworkManager/' (!422) - cli:try: avoid linting error for type hints (Closes: #1058524) (!422) - nm-parse: always read the PSK into the new psk variable (!416) - networkd: fix formatting (!424) - networkd: replace deprecated CriticalConnection= by KeepConfiguration= (!424) - networkd: move KeepConfiguration= into [Network] section - apply: bring "lo" back up if it's managed by NM (!408) - apply: don't assume the NM loopback connection is called "lo" (!408) * Drop patches merged upstream: - lp1809994/0010-parse-improve-the-parsing-of-access-points-LP-180999.patch -
[Bug 2058031] Re: [SRU] Backport 0.107.1-3 to Ubuntu 22.04
** Description changed: Stable Release Update for netplan.io 0.107.1-3 to Jammy. This version has many bug fixes and new features we want to make available to users of Ubuntu 22.04. netplan.io has an SRU exception for backporting new versions with new features https://wiki.ubuntu.com/NetplanUpdates Another SRU, for Mantic, was prepared in a separate LP bug: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058051. As the package is slightly different (due to backwards compatibility patches) and on Mantic we have the integration with Network Manager (which can cause different problems and requires more tests) I thought it would be more appropriate to work on the Mantic SRU in a different LP bug. [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * The netplan.io package was split up into netplan.io, which contains the CLI tool, netplan-generator, which contains the systemd generator and python3-netplan which contains the libnetplan Python bindings. netplan.io was changed to depend on the new packages so they will be automatically installed during upgrades https://salsa.debian.org/debian/netplan.io/-/commit/08311bc76adda512c9a0d353734d06231520a82e https://salsa.debian.org/debian/netplan.io/-/commit/8ed803b320a52ec6364f02959cd67332a6553b87 * Support for dummy interfaces (dummy-devices) https://github.com/canonical/netplan/pull/361 https://bugs.launchpad.net/netplan/+bug/1774203 * Support for veth interfaces (virtual-ethernets) https://github.com/canonical/netplan/pull/368 * The libnetplan Python bindings implementation was refactored to use python3-cffi and was moved to its own package, python3-netplan. https://github.com/canonical/netplan/pull/385 In addition to all the changes from netplan.io 0.107.1-3, a couple of bug fixes were imported from netplan.io 1.0-1: * debian/patches/lp2041727: Check if ovsdb-server.service is active before displaying warning https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041727 https://github.com/canonical/netplan/pull/421 This fixes an annoying warning message that many users were seeing when they call "netplan apply". * d/p/0004-tests-assert-generated-.service-files-in-assert_srio.patch, d/p/0005-tests-sriov-test-if-the-generated-netplan-rebind-ser.patch, d/p/0006-sriov-don-t-generate-duplicate-entries-in-the-rebind.patch: Don't generate duplicate entries in the netplan-sriov-rebind.service https://github.com/canonical/netplan/pull/437 This fixes a duplication problem where "netplan rebind" could process the same SR-IOV interface multiple times. See the changelog entry below for a full list of changes and bugs. [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. NOTE: there are a few autopkgtests failing on Jammy, but they are not regressions: * ip6gre and vti6 tunnel types: after a kernel update on Ubuntu, systemd started to fail to setup these types of tunnels. The problem was narrowed down to systemd and there is a fix for that which is pending SRU: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037667 * veth activation with Network Manager: the Network Manager available in Jammy has a bug that prevents it to correctly activate veth interfaces. There is a fix for that pending analysis for a future SRU: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2032824 We have been using patched packages for systemd and network-manager on Netplan's CI on Github and all the tests pass with the fixes. A PPA is available here https://launchpad.net/~slyon/+archive/ubuntu/netplan-ci + + Testing netplan upgrade + + 1) Launch a LXD VM with Jammy + + lxc launch ubuntu:jammy jammy-vm --vm + lxc shell jammy-vm + + 2) Check netplan is working + + netplan apply + + Note the annoying warning below: + + WARNING:root:Cannot call Open vSwitch: ovsdb-server.service is not + running. + + + The warnings about file permission can be suppressed with `chmod 600 /etc/netplan/*`. + + netplan get + + 3) Add the PPA with the new package and upgrade your packages + + add-apt-repository ppa:danilogondolfo/netplan-sru + + apt update ; apt -y upgrade + + 4) Check netplan
[Bug 2058051] Re: [SRU] Backport 0.107.1-3 to Ubuntu 23.10
** Description changed: - Stable Release Update for netplan.io 0.107.1-3 to Mantic. This version - has many bug fixes and new features we want to make available to users - of Ubuntu 23.10. + Another SRU, for Jammy, was prepared in a separate LP bug: + https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058031. As + the package is slightly different (due to backwards compatibility + patches) and on Mantic we have the integration with Network Manager + (which can cause different problems and requires more tests) I thought + it would be more appropriate to work on the Mantic SRU in a different LP + bug. + + [Impact] + This release contains both bug-fixes and new features and we would like to + make sure all of our supported customers have access to these improvements. + The notable ones are: + +* + + See the changelog entry below for a full list of changes and bugs. + + [Test Plan] + The following development and SRU process was followed: + https://wiki.ubuntu.com/NetplanUpdates + + Netplan contains an extensive integration test suite that is ran using + the SRU package for each releases. This test suite's results are available here: + http://autopkgtest.ubuntu.com/packages/n/netplan.io + + A successful run is required before the proposed netplan package + can be let into -updates. + + The netplan team will be in charge of attaching the artifacts and console + output of the appropriate run to the bug. Netplan team members will not + mark ‘verification-done’ until this has happened. + + [Where problems could occur] + In order to mitigate the regression potential, the results of the + aforementioned integration tests are attached to this bug. + + + + [Other Info] + + + [Changelog] * Backport netplan.io 0.107.1-3 to 23.10 (LP: #2058051): - wifi: add support for WPA3-Enterprise (LP: #2029876) (!402) - wifi: support WPA2 and WPA3 Personal simultaneously (!404) - added mii-monitor-interval example (!411) - docs: Add "Contribute Documentation" how-to - auth: add support for LEAP and EAP-PWD (!415) - tests: Add autopkgtest for (LP: #1959570) (!419) - wifi: make it possible to have a psk and an eap password simultaneously (!416) - doc: Set-up some basic Doxygen project (!423) - doc: Make Sphinx to handle autodoxygen project, using breathe (!423) - doc: create libnetplan apidoc structure (!423) - inc: Start documenting public API (!423) - doc: Update 'Netplan everywhere' for 23.10 (!418) Bug fixes: - test:ovs: Avoid NetworkManager taking contol, breaking a test - parse: allow COMMON_LINK_HANDLERS for VRFs (!401) - util: don't return a placeholder netdef in the iterator (!406) - tunnels/validation: do not error out if "local" is not defined (!407) - tests: add some integration tests without the local address (!407) - wireguard: ignore empty endpoints (LP: #2038811) (!414) - parse: improve the parsing of access-points (LP: #1809994) (!413) - wifi: replace the previously defined AP with the new one (!413) - doc: spelling check improvements (!417) - Fix permissions on folder '/run/NetworkManager/' (!422) - cli:try: avoid linting error for type hints (Closes: #1058524) (!422) - nm-parse: always read the PSK into the new psk variable (!416) - networkd: fix formatting (!424) - networkd: replace deprecated CriticalConnection= by KeepConfiguration= (!424) - networkd: move KeepConfiguration= into [Network] section - apply: bring "lo" back up if it's managed by NM (!408) - apply: don't assume the NM loopback connection is called "lo" (!408) + * Drop patches merged upstream: + - lp1809994/0010-parse-improve-the-parsing-of-access-points-LP-180999.patch + - lp1809994/0011-wifi-replace-the-previously-defined-AP-with-the-new-.patch + - lp2039821/0008-wireguard-ignore-empty-endpoints.patch + - lp2039825/0009-auth-add-support-for-LEAP-and-EAP-PWD.patch * Add patches for bug fixes from netplan.io 1.0-1: - - d/p/0004-cli-utils-introduce-systemctl_is_installed-helper.patch + - lp2041727/0004-cli-utils-introduce-systemctl_is_installed-helper.patch cli:utils: introduce systemctl_is_installed helper (LP: #2041727) (!421) - - d/p/0005-Update-ovs.py-to-check-if-ovsdb-server.service-is-in.patch + - lp2041727/0005-Update-ovs.py-to-check-if-ovsdb-server.service-is-in.patch Check if ovsdb-server.service is active before displaying warning (LP: #2041727) (!421) - - d/p/0006-cli-sriov-remove-unused-code.patch: - Remove unused code to avoid unnecessary parsing (!435) - d/p/0007-tests-assert-generated-.service-files-in-assert_srio.patch, d/p/0008-tests-sriov-test-if-the-generated-netplan-rebind-ser.patch, d/p/0009-sriov-don-t-generate-duplicate-entries-in-the-rebind.patch: Don't generate duplicate entries in the
[Bug 2058031] Re: [SRU] Backport 0.107.1-3 to Ubuntu 22.04
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/netplan/+git/ubuntu/+merge/462714 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058031 Title: [SRU] Backport 0.107.1-3 to Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058051] Re: [SRU] Backport 0.107.1-3 to Ubuntu 23.10
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/netplan/+git/ubuntu/+merge/462773 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058051 Title: [SRU] Backport 0.107.1-3 to Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058031] Re: [SRU] Backport 0.107.1-3 to Ubuntu 22.04
** Description changed: Stable Release Update for netplan.io 0.107.1-3 to Jammy. This version has many bug fixes and new features we want to make available to users of Ubuntu 22.04. netplan.io has an SRU exception for backporting new versions with new features https://wiki.ubuntu.com/NetplanUpdates [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * The netplan.io package was split up into netplan.io, which contains the CLI tool, netplan-generator, which contains the systemd generator and python3-netplan which contains the libnetplan Python bindings. netplan.io was changed to depend on the new packages so they will be automatically installed during upgrades https://salsa.debian.org/debian/netplan.io/-/commit/08311bc76adda512c9a0d353734d06231520a82e https://salsa.debian.org/debian/netplan.io/-/commit/8ed803b320a52ec6364f02959cd67332a6553b87 * Support for dummy interfaces (dummy-devices) https://github.com/canonical/netplan/pull/361 https://bugs.launchpad.net/netplan/+bug/1774203 * Support for veth interfaces (virtual-ethernets) https://github.com/canonical/netplan/pull/368 * The libnetplan Python bindings implementation was refactored to use python3-cffi and was moved to its own package, python3-netplan. https://github.com/canonical/netplan/pull/385 In addition to all the changes from netplan.io 0.107.1-3, a couple of bug fixes were imported from netplan.io 1.0-1: * debian/patches/lp2041727: Check if ovsdb-server.service is active before displaying warning https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041727 https://github.com/canonical/netplan/pull/421 This fixes an annoying warning message that many users were seeing when they call "netplan apply". * d/p/0004-tests-assert-generated-.service-files-in-assert_srio.patch, d/p/0005-tests-sriov-test-if-the-generated-netplan-rebind-ser.patch, d/p/0006-sriov-don-t-generate-duplicate-entries-in-the-rebind.patch: Don't generate duplicate entries in the netplan-sriov-rebind.service https://github.com/canonical/netplan/pull/437 This fixes a duplication problem where "netplan rebind" could process the same SR-IOV interface multiple times. See the changelog entry below for a full list of changes and bugs. [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. NOTE: there are a few autopkgtests failing on Jammy, but they are not regressions: * ip6gre and vti6 tunnel types: after a kernel update on Ubuntu, systemd started to fail to setup these types of tunnels. The problem was narrowed down to systemd and there is a fix for that which is pending SRU: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037667 * veth activation with Network Manager: the Network Manager available in Jammy has a bug that prevents it to correctly activate veth interfaces. There is a fix for that pending analysis for a future SRU: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2032824 We have been using patched packages for systemd and network-manager on Netplan's CI on Github and all the tests pass with the fixes. A PPA is available here https://launchpad.net/~slyon/+archive/ubuntu/netplan-ci + [Where problems could occur] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. As this is a big update, there are changes across most of the code base. In addition to the existing distro patches to ensure backwards compatibility with Jammy, a new one was added: debian/patches/sru- compat/0014-Demote-lacp-rate-validation-error-to-warning-for-bac.patch. This patch converts a new validation error (for an option we were not validating correctly) to a simple warning so configuration files that have the option improperly set will not start to fail to validate after update. + But as usual, any backwards compatibility issue that prevents the new + netplan to parse existing YAML files would leave the system without + networking configuration after a reboot. + [Other Info] - + With the python3-netplan package, the directory /usr/share/netplan/netplan will not be used anymore. Although, due to .pyc
[Bug 2058031] Re: [SRU] Backport 0.107.1-3 to Ubuntu 22.04
** Description changed: Stable Release Update for netplan.io 0.107.1-3 to Jammy. This version has many bug fixes and new features we want to make available to users of Ubuntu 22.04. netplan.io has an SRU exception for backporting new versions with new features https://wiki.ubuntu.com/NetplanUpdates [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * The netplan.io package was split up into netplan.io, which contains the CLI tool, netplan-generator, which contains the systemd generator and python3-netplan which contains the libnetplan Python bindings. netplan.io was changed to depend on the new packages so they will be automatically installed during upgrades + https://salsa.debian.org/debian/netplan.io/-/commit/08311bc76adda512c9a0d353734d06231520a82e + https://salsa.debian.org/debian/netplan.io/-/commit/8ed803b320a52ec6364f02959cd67332a6553b87 * Support for dummy interfaces (dummy-devices) - https://github.com/canonical/netplan/pull/361 - https://bugs.launchpad.net/netplan/+bug/1774203 + https://github.com/canonical/netplan/pull/361 + https://bugs.launchpad.net/netplan/+bug/1774203 * Support for veth interfaces (virtual-ethernets) - https://github.com/canonical/netplan/pull/368 + https://github.com/canonical/netplan/pull/368 * The libnetplan Python bindings implementation was refactored to use python3-cffi and was moved to its own package, python3-netplan. - https://github.com/canonical/netplan/pull/385 + https://github.com/canonical/netplan/pull/385 In addition to all the changes from netplan.io 0.107.1-3, a couple of bug fixes were imported from netplan.io 1.0-1: * debian/patches/lp2041727: Check if ovsdb-server.service is active before displaying warning - https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041727 - https://github.com/canonical/netplan/pull/421 + https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041727 + https://github.com/canonical/netplan/pull/421 This fixes an annoying warning message that many users were seeing when they call "netplan apply". * d/p/0004-tests-assert-generated-.service-files-in-assert_srio.patch, d/p/0005-tests-sriov-test-if-the-generated-netplan-rebind-ser.patch, d/p/0006-sriov-don-t-generate-duplicate-entries-in-the-rebind.patch: Don't generate duplicate entries in the netplan-sriov-rebind.service - https://github.com/canonical/netplan/pull/437 + https://github.com/canonical/netplan/pull/437 This fixes a duplication problem where "netplan rebind" could process the same SR-IOV interface multiple times. See the changelog entry below for a full list of changes and bugs. [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. NOTE: there are a few autopkgtests failing on Jammy, but they are not regressions: * ip6gre and vti6 tunnel types: after a kernel update on Ubuntu, systemd started to fail to setup these types of tunnels. The problem was narrowed down to systemd and there is a fix for that which is pending SRU: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037667 * veth activation with Network Manager: the Network Manager available in Jammy has a bug that prevents it to correctly activate veth interfaces. There is a fix for that pending analysis for a future SRU: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2032824 We have been using patched packages for systemd and network-manager on Netplan's CI on Github and all the tests pass with the fixes. A PPA is available here https://launchpad.net/~slyon/+archive/ubuntu/netplan-ci [Where problems could occur] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. As this is a big update, there are changes across most of the code base. In addition to the existing distro patches to ensure backwards compatibility with Jammy, a new one was added: debian/patches/sru- compat/0014-Demote-lacp-rate-validation-error-to-warning-for-bac.patch. This patch converts a new validation error (for an option we were not validating correctly) to a simple warning so configuration files that have the option improperly set will not start
[Bug 2058031] Re: [SRU] Backport 0.107.1-3 to Ubuntu 22.04
** Description changed: Stable Release Update for netplan.io 0.107.1-3 to Jammy. This version has many bug fixes and new features we want to make available to users of Ubuntu 22.04. netplan.io has an SRU exception for backporting new versions with new features https://wiki.ubuntu.com/NetplanUpdates [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * The netplan.io package was split up into netplan.io, which contains the CLI tool, netplan-generator, which contains the systemd generator and python3-netplan which contains the libnetplan Python bindings. netplan.io was changed to depend on the new packages so they will be automatically installed during upgrades * Support for dummy interfaces (dummy-devices) + https://github.com/canonical/netplan/pull/361 + https://bugs.launchpad.net/netplan/+bug/1774203 * Support for veth interfaces (virtual-ethernets) - - * The libnetplan Python bindings implementation was refactored to use - python3-cffi and was moved to its own package, python3-netplan. + https://github.com/canonical/netplan/pull/368 + + * The libnetplan Python bindings implementation was refactored to use python3-cffi and was moved to its own package, python3-netplan. + https://github.com/canonical/netplan/pull/385 In addition to all the changes from netplan.io 0.107.1-3, a couple of bug fixes were imported from netplan.io 1.0-1: - * debian/patches/lp2041727: Check if ovsdb-server.service is active - before displaying warning (LP: #2041727) (!421) + * debian/patches/lp2041727: Check if ovsdb-server.service is active before displaying warning + https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041727 + https://github.com/canonical/netplan/pull/421 This fixes an annoying warning message that many users were seeing when they call "netplan apply". - * d/p/0004-tests-assert-generated-.service-files-in-assert_srio.patch, - d/p/0005-tests-sriov-test-if-the-generated-netplan-rebind-ser.patch, - d/p/0006-sriov-don-t-generate-duplicate-entries-in-the-rebind.patch: - Don't generate duplicate entries in the netplan-sriov-rebind.service - (!437) - - This change fixes a duplication problem where "netplan rebind" could - process the same SR-IOV interface multiple times. + * d/p/0004-tests-assert-generated-.service-files-in-assert_srio.patch, d/p/0005-tests-sriov-test-if-the-generated-netplan-rebind-ser.patch, d/p/0006-sriov-don-t-generate-duplicate-entries-in-the-rebind.patch: Don't generate duplicate entries in the netplan-sriov-rebind.service + https://github.com/canonical/netplan/pull/437 + + This fixes a duplication problem where "netplan rebind" could process + the same SR-IOV interface multiple times. See the changelog entry below for a full list of changes and bugs. [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. NOTE: there are a few autopkgtests failing on Jammy, but they are not regressions: - * ip6gre and vti6 tunnel types: after a kernel update on Ubuntu, + * ip6gre and vti6 tunnel types: after a kernel update on Ubuntu, systemd started to fail to setup these types of tunnels. The problem was narrowed down to systemd and there is a fix for that which is pending SRU: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037667 - * veth activation with Network Manager: the Network Manager available + * veth activation with Network Manager: the Network Manager available in Jammy has a bug that prevents it to correctly activate veth interfaces. There is a fix for that pending analysis for a future SRU: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2032824 We have been using patched packages for systemd and network-manager on Netplan's CI on Github and all the tests pass with the fixes. A PPA is available here https://launchpad.net/~slyon/+archive/ubuntu/netplan-ci [Where problems could occur] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. As this is a big update, there are changes across most of the code base. In addition to the existing distro patches to ensure backwards compatibility with Jammy, a new one was added: debian/patches/sru-
[Bug 2058031] Re: [SRU] Backport 0.107.1-3 to Ubuntu 22.04
** Description changed: Stable Release Update for netplan.io 0.107.1-3 to Jammy. This version has many bug fixes and new features we want to make available to users of Ubuntu 22.04. netplan.io has an SRU exception for backporting new versions with new features https://wiki.ubuntu.com/NetplanUpdates [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: * The netplan.io package was split up into netplan.io, which contains the CLI tool, netplan-generator, which contains the systemd generator and python3-netplan which contains the libnetplan Python bindings. - netplan.io was changed to depend on the new packages so they will be automatically installed during upgrades + netplan.io was changed to depend on the new packages so they will be automatically installed during upgrades * Support for dummy interfaces (dummy-devices) * Support for veth interfaces (virtual-ethernets) * The libnetplan Python bindings implementation was refactored to use python3-cffi and was moved to its own package, python3-netplan. In addition to all the changes from netplan.io 0.107.1-3, a couple of bug fixes were imported from netplan.io 1.0-1: * debian/patches/lp2041727: Check if ovsdb-server.service is active before displaying warning (LP: #2041727) (!421) - This fixes an annoying warning message that many users were seeing + This fixes an annoying warning message that many users were seeing when they call "netplan apply". * d/p/0004-tests-assert-generated-.service-files-in-assert_srio.patch, d/p/0005-tests-sriov-test-if-the-generated-netplan-rebind-ser.patch, d/p/0006-sriov-don-t-generate-duplicate-entries-in-the-rebind.patch: Don't generate duplicate entries in the netplan-sriov-rebind.service (!437) - This change fixes a duplication problem where "netplan rebind" could + This change fixes a duplication problem where "netplan rebind" could process the same SR-IOV interface multiple times. See the changelog entry below for a full list of changes and bugs. [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. + + NOTE: there are a few autopkgtests failing on Jammy, but they are not + regressions: + + * ip6gre and vti6 tunnel types: after a kernel update on Ubuntu, + systemd started to fail to setup these types of tunnels. The problem was + narrowed down to systemd and there is a fix for that which is pending + SRU: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037667 + + * veth activation with Network Manager: the Network Manager available + in Jammy has a bug that prevents it to correctly activate veth + interfaces. There is a fix for that pending analysis for a future SRU: + https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2032824 + + We have been using patched packages for systemd and network-manager on + Netplan's CI on Github and all the tests pass with the fixes. A PPA is + available here https://launchpad.net/~slyon/+archive/ubuntu/netplan-ci [Where problems could occur] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. As this is a big update, there are changes across most of the code base. In addition to the existing distro patches to ensure backwards compatibility with Jammy, a new one was added: debian/patches/sru- compat/0014-Demote-lacp-rate-validation-error-to-warning-for-bac.patch. This patch converts a new validation error (for an option we were not validating correctly) to a simple warning so configuration files that have the option improperly set will not start to fail to validate after update. [Other Info] [Changelog] * Backport netplan.io 0.107.1-3 to 22.04 (LP: #2058031): - Support for "dummy" (`dummy-devices`) interfaces (LP: #1774203) (!361) - Support for "veth" (`virtual-ethernets`) interfaces (!368) - Add Python bindings for libnetplan (!385) - netplan: Handle command exceptions (!334) - WPA3 (personal) support (LP: #2023238) (!369) - Add all the commands to the bash completion file (LP: #1749869) (!326) - New submodule for state manipulation (!379) - commands/status: show routes from all routing tables (!390)
[Bug 2058031] Re: [SRU] Backport 0.107.1-3 to Ubuntu 22.04
** Description changed: Stable Release Update for netplan.io 0.107.1-3 to Jammy. This version has many bug fixes and new features we want to make available to users of Ubuntu 22.04. netplan.io has an SRU exception for backporting new versions with new features https://wiki.ubuntu.com/NetplanUpdates [Impact] This release contains both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: - One big change with this updated is the split of netplan.io in different - packages. netplan.io now contains the CLI code, netplan-generator - contains the systemd generator used to emit the configuration and - python3-netplan contains the netplan python module used by the CLI and - external consumers of libnetplan. + * The netplan.io package was split up into netplan.io, which contains the CLI tool, netplan-generator, which contains the systemd generator and python3-netplan which contains the libnetplan Python bindings. + netplan.io was changed to depend on the new packages so they will be automatically installed during upgrades + + * Support for dummy interfaces (dummy-devices) + + * Support for veth interfaces (virtual-ethernets) + + * The libnetplan Python bindings implementation was refactored to use + python3-cffi and was moved to its own package, python3-netplan. + + In addition to all the changes from netplan.io 0.107.1-3, a couple of + bug fixes were imported from netplan.io 1.0-1: + + * debian/patches/lp2041727: Check if ovsdb-server.service is active + before displaying warning (LP: #2041727) (!421) + + This fixes an annoying warning message that many users were seeing + when they call "netplan apply". + + * d/p/0004-tests-assert-generated-.service-files-in-assert_srio.patch, + d/p/0005-tests-sriov-test-if-the-generated-netplan-rebind-ser.patch, + d/p/0006-sriov-don-t-generate-duplicate-entries-in-the-rebind.patch: + Don't generate duplicate entries in the netplan-sriov-rebind.service + (!437) + + This change fixes a duplication problem where "netplan rebind" could + process the same SR-IOV interface multiple times. See the changelog entry below for a full list of changes and bugs. [Test Plan] The following development and SRU process was followed: https://wiki.ubuntu.com/NetplanUpdates Netplan contains an extensive integration test suite that is ran using the SRU package for each releases. This test suite's results are available here: http://autopkgtest.ubuntu.com/packages/n/netplan.io A successful run is required before the proposed netplan package can be let into -updates. The netplan team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. Netplan team members will not mark ‘verification-done’ until this has happened. [Where problems could occur] In order to mitigate the regression potential, the results of the aforementioned integration tests are attached to this bug. + As this is a big update, there are changes across most of the code base. + In addition to the existing distro patches to ensure backwards + compatibility with Jammy, a new one was added: debian/patches/sru- + compat/0014-Demote-lacp-rate-validation-error-to-warning-for-bac.patch. + This patch converts a new validation error (for an option we were not + validating correctly) to a simple warning so configuration files that + have the option improperly set will not start to fail to validate after + update. + [Other Info] [Changelog] - * Backport netplan.io 0.107.1-3 to 22.04 (LP: #2058031): - - Support for "dummy" (`dummy-devices`) interfaces (LP: #1774203) (!361) - - Support for "veth" (`virtual-ethernets`) interfaces (!368) - - Add Python bindings for libnetplan (!385) - - netplan: Handle command exceptions (!334) - - WPA3 (personal) support (LP: #2023238) (!369) - - Add all the commands to the bash completion file (LP: #1749869) (!326) - - New submodule for state manipulation (!379) - - commands/status: show routes from all routing tables (!390) - - cli:status: Make rich pretty printing optional (!388) - - libnetplan: expose dhcp4 and dhcp6 properties (!394) - - Expose macaddress and DNS configuration from the netdef (!395) - - libnetplan: expose the routes list in the netdef (!397) - - NetworkManager: Wireguard private key flag support (!371) - - Add a netplan_parser_load_keyfile() Python binding (!351) - - keyfile parser: add support for all tunnel types (LP: #2016473) (!360) - - parse-nm:wg: add support for reading the listen-port property (!372) - - parse-nm: add support for VRF devices (!398) - - Vlan keyfile parser support (!370) - - Netplan docs rework (!333 & !337) - - docs: Add a short netplan-everywhere howto (!325) - - doc: make us of sphinx copybutton plugin (!354) - - doc: Add Ubuntu Code
[Bug 2058031] Re: [SRU] Backport 0.107.1-3 to Ubuntu 22.04
** Description changed: Stable Release Update for netplan.io 0.107.1-3 to Jammy. This version has many bug fixes and new features we want to make available to users - of Ubuntu 22.04. + of Ubuntu 22.04. netplan.io has an SRU exception for backporting new + versions with new features https://wiki.ubuntu.com/NetplanUpdates + + [Impact] + + This release contains both bug-fixes and new features and we would like to + make sure all of our supported customers have access to these improvements. + The notable ones are: One big change with this updated is the split of netplan.io in different packages. netplan.io now contains the CLI code, netplan-generator contains the systemd generator used to emit the configuration and python3-netplan contains the netplan python module used by the CLI and external consumers of libnetplan. - Changelog: + See the changelog entry below for a full list of changes and bugs. + + [Test Plan] + The following development and SRU process was followed: + https://wiki.ubuntu.com/NetplanUpdates + + Netplan contains an extensive integration test suite that is ran using + the SRU package for each releases. This test suite's results are available here: + http://autopkgtest.ubuntu.com/packages/n/netplan.io + + A successful run is required before the proposed netplan package + can be let into -updates. + + The netplan team will be in charge of attaching the artifacts and console + output of the appropriate run to the bug. Netplan team members will not + mark ‘verification-done’ until this has happened. + + [Where problems could occur] + In order to mitigate the regression potential, the results of the + aforementioned integration tests are attached to this bug. + + + + [Other Info] + + + [Changelog] * Backport netplan.io 0.107.1-3 to 22.04 (LP: #2058031): - Support for "dummy" (`dummy-devices`) interfaces (LP: #1774203) (!361) - Support for "veth" (`virtual-ethernets`) interfaces (!368) - Add Python bindings for libnetplan (!385) - netplan: Handle command exceptions (!334) - WPA3 (personal) support (LP: #2023238) (!369) - Add all the commands to the bash completion file (LP: #1749869) (!326) - New submodule for state manipulation (!379) - commands/status: show routes from all routing tables (!390) - cli:status: Make rich pretty printing optional (!388) - libnetplan: expose dhcp4 and dhcp6 properties (!394) - Expose macaddress and DNS configuration from the netdef (!395) - libnetplan: expose the routes list in the netdef (!397) - NetworkManager: Wireguard private key flag support (!371) - Add a netplan_parser_load_keyfile() Python binding (!351) - keyfile parser: add support for all tunnel types (LP: #2016473) (!360) - parse-nm:wg: add support for reading the listen-port property (!372) - parse-nm: add support for VRF devices (!398) - Vlan keyfile parser support (!370) - Netplan docs rework (!333 & !337) - docs: Add a short netplan-everywhere howto (!325) - doc: make us of sphinx copybutton plugin (!354) - doc: Add Ubuntu Code of Conduct 2.0 (!355) - doc: Explanation about 00-network-manager-all.yaml (!378) - wifi: add support for WPA3-Enterprise (LP: #2029876) (!402) - wifi: support WPA2 and WPA3 Personal simultaneously (!404) - added mii-monitor-interval example (!411) - docs: Add "Contribute Documentation" how-to - auth: add support for LEAP and EAP-PWD (!415) - tests: Add autopkgtest for (LP: #1959570) (!419) - wifi: make it possible to have a psk and an eap password simultaneously (!416) - doc: Set-up some basic Doxygen project (!423) - doc: Make Sphinx to handle autodoxygen project, using breathe (!423) - doc: create libnetplan apidoc structure (!423) - inc: Start documenting public API (!423) - doc: Update 'Netplan everywhere' for 23.10 (!418) Bug fixes: - Fix FTBFS on Fedora and refresh RPM packaging (!323) - parser: validate lacp-rate properly (LP: #1745648) (!324) - use meson-make-symlink.sh helper instead of install_symlink() (!327) - netplan: cli: fix typo from 'unkown' to 'unknown' (!328) - Handle duplication during parser second pass (LP: #2007682) (!329) - parse:ovs: Ignore deprecated OpenFlow1.6 protocol (LP: #1963735) (!332) - dbus: Build the copy path correctly (!331) - tests: add new spread based snapd integration test (!330) - Use controlled execution environment, to avoid failure if PATH is unset (LP: #1959570) (!336) - Some refactoring (!338) - netplan: adjust the maximum buffer size to 1MB (!340) - parse: use "--" with systemd-escape (!347) - docs: fix bridge parameters types and add examples (!346) - vrfs: skip policies parsing if list is NULL (LP: #2016427) (!341) - networkd: plug a memory leak (!344) -
[Bug 2058179] Re: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported
I ran into the same issue here. It's the same symptom. I'm running Noble with ZFS on root and kernel 6.8. Setting up tomcat10-common (10.1.16-1) ... Setting up tomcat10 (10.1.16-1) ... Creating group 'tomcat' with GID 994. Creating user 'tomcat' (Apache Tomcat) with UID 994 and GID 994. Failed to backup /etc/group: Operation not supported dpkg: error processing package tomcat10 (--configure): installed tomcat10 package post-installation script subprocess returned error exit status 1 Processing triggers for rsyslog (8.2312.0-3ubuntu3) ... Processing triggers for libc-bin (2.39-0ubuntu2) ... Errors were encountered while processing: tomcat10 E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058179 Title: Kernel 6.8 + zfs-2.2.2: copy_file_range Operation Not Supported To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/2058179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058031] Re: [SRU] Backport 0.107.1-3 to Ubuntu 22.04
** Description changed: - [tbd] + Stable Release Update for netplan.io 0.107.1-3 to Jammy. This version + has many bug fixes and new features we want to make available to users + of Ubuntu 22.04. + + One big change with this updated is the split of netplan.io in different + packages. netplan.io now contains the CLI code, netplan-generator + contains the systemd generator used to emit the configuration and + python3-netplan contains the netplan python module used by the CLI and + external consumers of libnetplan. + + Changelog: + + * Backport netplan.io 0.107.1-3 to 22.04 (LP: #2058031): + - Support for "dummy" (`dummy-devices`) interfaces (LP: #1774203) (!361) + - Support for "veth" (`virtual-ethernets`) interfaces (!368) + - Add Python bindings for libnetplan (!385) + - netplan: Handle command exceptions (!334) + - WPA3 (personal) support (LP: #2023238) (!369) + - Add all the commands to the bash completion file (LP: #1749869) (!326) + - New submodule for state manipulation (!379) + - commands/status: show routes from all routing tables (!390) + - cli:status: Make rich pretty printing optional (!388) + - libnetplan: expose dhcp4 and dhcp6 properties (!394) + - Expose macaddress and DNS configuration from the netdef (!395) + - libnetplan: expose the routes list in the netdef (!397) + - NetworkManager: Wireguard private key flag support (!371) + - Add a netplan_parser_load_keyfile() Python binding (!351) + - keyfile parser: add support for all tunnel types (LP: #2016473) (!360) + - parse-nm:wg: add support for reading the listen-port property (!372) + - parse-nm: add support for VRF devices (!398) + - Vlan keyfile parser support (!370) + - Netplan docs rework (!333 & !337) + - docs: Add a short netplan-everywhere howto (!325) + - doc: make us of sphinx copybutton plugin (!354) + - doc: Add Ubuntu Code of Conduct 2.0 (!355) + - doc: Explanation about 00-network-manager-all.yaml (!378) + - wifi: add support for WPA3-Enterprise (LP: #2029876) (!402) + - wifi: support WPA2 and WPA3 Personal simultaneously (!404) + - added mii-monitor-interval example (!411) + - docs: Add "Contribute Documentation" how-to + - auth: add support for LEAP and EAP-PWD (!415) + - tests: Add autopkgtest for (LP: #1959570) (!419) + - wifi: make it possible to have a psk and an eap password simultaneously + (!416) + - doc: Set-up some basic Doxygen project (!423) + - doc: Make Sphinx to handle autodoxygen project, using breathe (!423) + - doc: create libnetplan apidoc structure (!423) + - inc: Start documenting public API (!423) + - doc: Update 'Netplan everywhere' for 23.10 (!418) + Bug fixes: + - Fix FTBFS on Fedora and refresh RPM packaging (!323) + - parser: validate lacp-rate properly (LP: #1745648) (!324) + - use meson-make-symlink.sh helper instead of install_symlink() (!327) + - netplan: cli: fix typo from 'unkown' to 'unknown' (!328) + - Handle duplication during parser second pass (LP: #2007682) (!329) + - parse:ovs: Ignore deprecated OpenFlow1.6 protocol (LP: #1963735) (!332) + - dbus: Build the copy path correctly (!331) + - tests: add new spread based snapd integration test (!330) + - Use controlled execution environment, to avoid failure if PATH is unset + (LP: #1959570) (!336) + - Some refactoring (!338) + - netplan: adjust the maximum buffer size to 1MB (!340) + - parse: use "--" with systemd-escape (!347) + - docs: fix bridge parameters types and add examples (!346) + - vrfs: skip policies parsing if list is NULL (LP: #2016427) (!341) + - networkd: plug a memory leak (!344) + - libnetplan: don't try to read from a NULL file (!342) + - nm: return if write_routes() fails (!345) + - parse: plug a memory leak (!348) + - parse: set the backend on nm-devices to NM (!349) + - parse: don't point to the wrong node on validation (!343) + - rtd: set the OS and Python versions explicitly (!357) + - Fix 8021x eap method parsing (LP: #2016625) (!358) + - CI: update canonical/setup-lxd to v0.1.1 (!359) + - CI: fix dch after adding the new 0.106.1 tag (!364) + - Provide frequency to wpa_supplicant in adhoc mode (LP: #2020754) (!363) + - Improve the coverage of the memory leak tests (!365) + - Fix keyfile parsing of wireguard config (!366) + - routes: fix metric rendering (LP: #2023681) (!367) + - CI: add DebCI integration test (!362) + - CI: initial NetworkManager autopkgtests (!374) + - parse-nm: handle cloned-mac-address special cases (LP: #2026230) (!376) + - Improve autopkgtest stability with systemd 253 & iproute 6.4 (!377) + - Fixes for minor issues (!380) + - tests:integration: Adopt for systemd v254 (Closes: #1041310) (!381) + - parse: Downgrade NM passthrough warning to debug (!384) + - Don't drop files with just global
[Bug 2058051] Re: [SRU] Backport 0.107.1-3 to Ubuntu 23.10
** Description changed: - [tbd] + Stable Release Update for netplan.io 0.107.1-3 to Mantic. This version + has many bug fixes and new features we want to make available to users + of Ubuntu 23.10. + + * Backport netplan.io 0.107.1-3 to 23.10 (LP: #2058051): + - wifi: add support for WPA3-Enterprise (LP: #2029876) (!402) + - wifi: support WPA2 and WPA3 Personal simultaneously (!404) + - added mii-monitor-interval example (!411) + - docs: Add "Contribute Documentation" how-to + - auth: add support for LEAP and EAP-PWD (!415) + - tests: Add autopkgtest for (LP: #1959570) (!419) + - wifi: make it possible to have a psk and an eap password simultaneously + (!416) + - doc: Set-up some basic Doxygen project (!423) + - doc: Make Sphinx to handle autodoxygen project, using breathe (!423) + - doc: create libnetplan apidoc structure (!423) + - inc: Start documenting public API (!423) + - doc: Update 'Netplan everywhere' for 23.10 (!418) + Bug fixes: + - test:ovs: Avoid NetworkManager taking contol, breaking a test + - parse: allow COMMON_LINK_HANDLERS for VRFs (!401) + - util: don't return a placeholder netdef in the iterator (!406) + - tunnels/validation: do not error out if "local" is not defined (!407) + - tests: add some integration tests without the local address (!407) + - wireguard: ignore empty endpoints (LP: #2038811) (!414) + - parse: improve the parsing of access-points (LP: #1809994) (!413) + - wifi: replace the previously defined AP with the new one (!413) + - doc: spelling check improvements (!417) + - Fix permissions on folder '/run/NetworkManager/' (!422) + - cli:try: avoid linting error for type hints (Closes: #1058524) (!422) + - nm-parse: always read the PSK into the new psk variable (!416) + - networkd: fix formatting (!424) + - networkd: replace deprecated CriticalConnection= by KeepConfiguration= + (!424) + - networkd: move KeepConfiguration= into [Network] section + - apply: bring "lo" back up if it's managed by NM (!408) + - apply: don't assume the NM loopback connection is called "lo" (!408) + * Add patches for bug fixes from netplan.io 1.0-1: + - d/p/0004-cli-utils-introduce-systemctl_is_installed-helper.patch + cli:utils: introduce systemctl_is_installed helper (LP: #2041727) (!421) + - d/p/0005-Update-ovs.py-to-check-if-ovsdb-server.service-is-in.patch + Check if ovsdb-server.service is active before displaying warning + (LP: #2041727) (!421) + - d/p/0006-cli-sriov-remove-unused-code.patch: + Remove unused code to avoid unnecessary parsing (!435) + - d/p/0007-tests-assert-generated-.service-files-in-assert_srio.patch, + d/p/0008-tests-sriov-test-if-the-generated-netplan-rebind-ser.patch, + d/p/0009-sriov-don-t-generate-duplicate-entries-in-the-rebind.patch: + Don't generate duplicate entries in the netplan-sriov-rebind.service + (!437) + * Drop patches not required for 23.10: + - debian/patches/python-limited-stable-api.patch + * debian/netplan.io.preinst: + - This preinst script is intended to cleanup the .pyc files from + share/netplan/netplan. This directory is supposed to be removed after + the upgrade from netplan.io 0.106.1 to 0.107, as the Python code + was moved to it's own python3-netplan package, but it's left behind + due to Python cached files. + * Drop changes related to usr-merge and not required for 23.10: + - debian/netplan-generator.install + - debian/netplan-generator.postinst + - debian/netplan-generator.preinst + * debian/netplan-generator.lintian-overrides: + - Drop overrides file. It wasn't really silencing any lintian warnings. + + + [Test Plan] + tbd + + [Where problems could occur] + tbd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058051 Title: [SRU] Backport 0.107.1-3 to Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058051] [NEW] [SRU] Backport 0.107.1-3 to Ubuntu 23.10
Public bug reported: [tbd] ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058051 Title: [SRU] Backport 0.107.1-3 to Ubuntu 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058031] [NEW] [SRU] Backport 0.107.1-3 to Ubuntu 22.04
Public bug reported: [tbd] ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058031 Title: [SRU] Backport 0.107.1-3 to Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2058031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055148 Title: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2055148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055148 Title: NetworkManager connections with an explicit DoT (DNS over TLS) are not supported with Netplan To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2055148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056633] [NEW] Gnome-shell crashing
Public bug reported: Gnome shell always crashing for no apparent reason ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 14:33:52 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-09-14 (177 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056633 Title: Gnome-shell crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2056633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056213] [NEW] Unable to open Software & Updates
Public bug reported:
I receive the error below when trying to open, after update
software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, in
__init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42 [modified:
usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py]
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 5 20:42:48 2024
InstallationDate: Installed on 2023-09-14 (173 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056213
Title:
Unable to open Software & Updates
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2056213/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052457] Re: libreoffice latest version not detecting my java installation
It seems no JRE was packed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052457 Title: libreoffice latest version not detecting my java installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2052457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
+1 maintenance
Hello, I had some Netplan related tasks to finish before FF so my +1 maintenance shift wasn't super efficient. For awareness, I'm seeing lots of similar FTBFS issues: 1) FTBFS due to missing symbols in symbol files. Some of them are due to only two symbols, strlcpy and strlcat. Those functions were added in glibc 2.38 and started to show up now during rebuilds. 2) FTBFS due to custom implementations of strlcpy and strlcat and the new glibc. I suppose Debian is not seeing it yet because glibc 2.38 is still in experimental there. 3) FTBFS due to unsatisfiable dependencies. Probably caused by the ongoing time_t work. 4) FTBFS due to _FORTIFY_SOURCE redefinition. It started to happen probably because we bumped it up to 3 in Ubuntu and it's still 2 in Debian. Things I worked on: fetchmail: FTBFS due to OpenSSL version (LP: #2052964). fetchmail is compatible with the OpenSSL available in Noble so I dropped the dependency from >= 3.1.x to >= 3.0.x. OpenSSL 3.0 is the version we are going to ship with Noble. libhtp2: FTBFS on Noble on all archs (LP: #2055051). The symbols file was missing some new symbols and the build is failing on Ubuntu. It's blocking suricata. btas: btas is causing a FTBFS in tiledarray. I submitted a no change rebuild (LP: #2055063) due to the new libboost1.83. btas installs a cmake file with the full path of BoostConfig.cmake and it's pointing to the old file from libboost1.74. android-platform-art: FTBFS due to new glibc strlcpy symbol (LP: #2055399). I've created a little patch to only compile the package’s own implementation of strlcpy if glibc is older than 2.38. beep: FTBFS due to _FORTIFY_SOURCE redefinition (LP: #2055689) intel-graphics-compiler: FTBFS due to _FORTIFY_SOURCE redefinition. I prepared a patch but the maintainer was quicker and fixed it in Debian. Although, the solution seems to not be ideal for Ubuntu. The change basically undefines _FORTIFY_SOURCE so when it shows up again it doesn't fail with a redefinition error. Although, on Ubuntu, this is what happens effectively: gcc -D_FORTIFY_SOURCE=3 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 so the default value of 3 from Ubuntu is overwritten back to 2. libdumbnet: FTBFS due to the symbols file and strlcpy/strlcat symbols with the new glibc (LP: #2055693). libwww-mechanize-perl: merged from debian (LP: #2055713) -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 2055693] Re: FTBFS on Noble
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/libdumbnet/+git/libdumbnet/+merge/461632 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055693 Title: FTBFS on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdumbnet/+bug/2055693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055713] Re: Please merge 2.18-1 into noble
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/libwww-mechanize-perl/+git/libwww-mechanize-perl/+merge/461653 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055713 Title: Please merge 2.18-1 into noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwww-mechanize-perl/+bug/2055713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055713] [NEW] Please merge 2.18-1 into noble
Public bug reported: tracking bug ** Affects: libwww-mechanize-perl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055713 Title: Please merge 2.18-1 into noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwww-mechanize-perl/+bug/2055713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055689] Re: FTBFS on Noble
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/beep/+git/beep/+merge/461630 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055689 Title: FTBFS on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beep/+bug/2055689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055693] [NEW] FTBFS on Noble
Public bug reported: +++ dpkg-gensymbolsZpo_vY 2024-02-29 10:00:05.746752747 + @@ -93,8 +93,8 @@ route_get@Base 1.8 route_loop@Base 1.8 route_open@Base 1.8 - strlcat@Base 1.8 - strlcpy@Base 1.8 +#MISSING: 1.17.0-1# strlcat@Base 1.8 +#MISSING: 1.17.0-1# strlcpy@Base 1.8 tun_close@Base 1.11 tun_fileno@Base 1.11 tun_name@Base 1.11 mv debian/.debhelper/generated/libdumbnet1/triggers.new debian/.debhelper/generated/libdumbnet1/triggers rm -f debian/libdumbnet-dev/DEBIAN/shlibs dh_makeshlibs: error: failing due to earlier errors ** Affects: libdumbnet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055693 Title: FTBFS on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdumbnet/+bug/2055693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055689] [NEW] FTBFS on Noble
Public bug reported: It's failing with : error: "_FORTIFY_SOURCE" redefined [-Werror] : note: this is the location of the previous definition cc1: all warnings being treated as errors ** Affects: beep (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055689 Title: FTBFS on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beep/+bug/2055689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055399] Re: FTBFS due new glibc and strlcpy
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/android-platform-art/+git/android-platform-art/+merge/461525 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055399 Title: FTBFS due new glibc and strlcpy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-art/+bug/2055399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055399] Re: FTBFS due new glibc and strlcpy
** Description changed:
This package had it's own implementation of strlcpy. glibc added it in
2.38 and now it's failing to build.
In file included from runtime/debugger.cc:37:
libartbase/base/strlcpy.h:31:22: error: static declaration of 'strlcpy'
follows non-static declaration
static inline size_t strlcpy(char* dst, const char* src, size_t size) {
- ^
+ ^
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:150:8: note: previous
definition is here
__NTH (strlcpy (char *__restrict __dest, const char *__restrict __src,
-^
+ ^
+
+ Related to https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2035195
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055399
Title:
FTBFS due new glibc and strlcpy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-platform-art/+bug/2055399/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055399] [NEW] FTBFS due new glibc and strlcpy
Public bug reported:
This package had it's own implementation of strlcpy. glibc added it in
2.38 and now it's failing to build.
In file included from runtime/debugger.cc:37:
libartbase/base/strlcpy.h:31:22: error: static declaration of 'strlcpy' follows
non-static declaration
static inline size_t strlcpy(char* dst, const char* src, size_t size) {
^
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:150:8: note: previous
definition is here
__NTH (strlcpy (char *__restrict __dest, const char *__restrict __src,
^
** Affects: android-platform-art (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055399
Title:
FTBFS due new glibc and strlcpy
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-platform-art/+bug/2055399/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055063] [NEW] No change rebuild needed due to new libboost1.83
Public bug reported: libbtas-dev installs a cmake file with the full path of the file BoostConfig.cmake, like this /usr/lib/cmake/BTAS/btas-config.cmake:set(Boost_CONFIG /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake) It's causing tiledarray to FTBFS with the following error: CMake Error at /usr/lib/cmake/BTAS/btas-config.cmake:72 (message): Expected Boost config file at /usr/lib/x86_64-linux-gnu/cmake/Boost-1.74.0/BoostConfig.cmake; directory moved since BTAS configuration? Call Stack (most recent call first): cmake/modules/FindOrFetchBTAS.cmake:1 (find_package) CMakeLists.txt:279 (include) A no change rebuild should be enough to fix the problem. ** Affects: btas (Ubuntu) Importance: Undecided Status: New ** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/btas/+git/btas/+merge/461276 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055063 Title: No change rebuild needed due to new libboost1.83 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btas/+bug/2055063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055051] Re: FTBFS on Noble
** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/libhtp/+git/libhtp/+merge/461263 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055051 Title: FTBFS on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhtp/+bug/2055051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055051] [NEW] FTBFS on Noble
Public bug reported: It's blocking Suricata. dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libhtp2/DEBIAN/symbols doesn't match completely debian/libhtp2.symbols --- debian/libhtp2.symbols (libhtp2_1:0.5.46-1_amd64) +++ dpkg-gensymbolsl4zGci 2024-02-21 02:58:05.888502114 + @@ -146,6 +146,7 @@ htp_config_set_log_level@Base 0.5.16 htp_config_set_lzma_layers@Base 0.5.34 htp_config_set_lzma_memlimit@Base 0.5.31 + htp_config_set_max_tx@Base 1:0.5.46-1 htp_config_set_nul_encoded_terminates@Base 0.5.16 htp_config_set_nul_encoded_unwanted@Base 0.5.16 htp_config_set_nul_raw_terminates@Base 0.5.16 @@ -229,6 +230,7 @@ htp_connp_res_receiver_finalize_clear@Base 0.5.16 htp_connp_set_user_data@Base 0.5.16 htp_connp_tx_create@Base 0.5.16 + htp_connp_tx_freed@Base 1:0.5.46-1 htp_connp_tx_remove@Base 0.5.16 htp_convert_method_to_number@Base 0.5.16 htp_decode_path_inplace@Base 0.5.16 @@ -237,6 +239,7 @@ htp_gzip_decompressor_create@Base 0.5.16 htp_gzip_decompressor_decompress@Base 0.5.41 htp_gzip_decompressor_destroy@Base 0.5.41 + htp_header_has_token@Base 1:0.5.46-1 htp_hook_copy@Base 0.5.16 htp_hook_create@Base 0.5.16 htp_hook_destroy@Base 0.5.16 @@ -388,5 +391,5 @@ htp_utf8_validate_path@Base 0.5.16 htp_validate_hostname@Base 0.5.16 lzma_Alloc@Base 0.5.31 - strlcat@Base 0.5.24+1git0439eed - strlcpy@Base 0.5.24+1git0439eed +#MISSING: 1:0.5.46-1# strlcat@Base 0.5.24+1git0439eed +#MISSING: 1:0.5.46-1# strlcpy@Base 0.5.24+1git0439eed dh_makeshlibs: error: failing due to earlier errors mv debian/.debhelper/generated/libhtp2/triggers.new debian/.debhelper/generated/libhtp2/triggers make: *** [debian/rules:12: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 ** Affects: libhtp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055051 Title: FTBFS on Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhtp/+bug/2055051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2052964] Re: Migration prevented due to "missing dep libssl-dev (>= 3.1.4)"
As we are not going to update OpenSSL on Noble (https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2044795) I created a merge request dropping the requirements to OpenSSL 3.0. According to the README.SSL file, fetchmail will work just fine. ** Merge proposal linked: https://code.launchpad.net/~danilogondolfo/ubuntu/+source/fetchmail/+git/fetchmail/+merge/461242 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2052964 Title: Migration prevented due to "missing dep libssl-dev (>= 3.1.4)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/2052964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
+1 maintenance report
I had a shorter week with some Netplan distractions but here we go: 1. delve FTBFS due to the installed bpftool not matching the running kernel version. I tried to workaround this by calling bpftool directly from /usr/lib/linux-tools-. It kinda worked but the build still fails for a different reason. It needs more work. See LP: #2021481 2. bpftrace FTBFS on armhf. The problem apparently is a gcc bug. I created a patch with a workaround and asked the upstream project about the issue. See: LP: #2023173 Also submitted to Debian #1037185 Github discussion https://github.com/iovisor/bpftrace/pull/2360#discussion_r1223534659 3. cbmc FTBFS on all architectures. The compiler is catching some errors I believe are false positives. There are some optional variables that it says are MAYBE uninitialized. I added -Wno-error=maybe-uninitialized to the CXX FLAGS and it fixed the build on amd64. It's now failing for a different reason on the other archs. LP: #2023276 4. pistache FTBFS on all architectures except riscv One of the unit tests tries to resolve an address via DNS and fails because the builder doesn't have access to the internet I suppose. It's not failing on Debian's CI. A patch was submitted to the upstream project https://github.com/pistacheio/pistache/pull/1134 LP: #2023274 5. ctffind FTBFS on non-x86 architectures It uses x86 assembly inline. I implemented an alternative code calling sinf() and cosf() from the libc instead on non-x86 systems. LP: #2023288 Debian bug: #1037227 The patch was accepted by Debian and is already synced to Ubuntu. 6. elinks: FTBFS on s390x A tool used during tests, sgml-parser, is crashing. There is a use-after-free issue in the code that is not making it crash on other architectures. One can see it by using valgrind or compiling elinks with address sanitizer. See: LP: 2023305 I also reported the problem upstream: https://github.com/rkd77/elinks/issues/235 7. libopenmpt Autopkgtests failing The test will build a C file that emits some deprecation warnings. This is causing the test to fail. LP: #2023406 It was already reported to Debian: #1037007 Danilo. -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
+1 maintenance report
I was on +1 last week (my first week :) ) and worked on the following items: pycodestyle vs update-notifier: update-notifier was failing a style check with the new pycodestyle and blocking its migration. I submitted a trivial fix upstream which was merged and pycodestyle migrated when a new release of update-notifier was uploaded. flake8-import-order vs python-flake8 vs pycodestyle: flake8-import-order was failing with the new pycodestyle. It required a retry triggered with python-flake8 from -proposed and migrated after that. python-pytest-flake8 vs python-flake8: python-pytest-flake8 was also failing with the new pycodestyle. It required a retry triggered with python-flake8 from -proposed. python-flake8 vs icdiff: the new version of icdiff was failing due to a weird test that used process substitution and was expecting a specific file descriptor number to succeed. I reached out to the upstream project on Github and they came up with a fix. I also submitted a PR to integrate another patch present in the package which is already merged so hopefully we can drop all the patches on the next release. fio vs tgt: tgt's tests were failing due to a missing test dependency (fio-examples). It was fixed on Ubuntu and submitted to Debian as well. These packages were migrated during my shift: pycodestyle python-flake8 python-pytest-flake8 icdiff fio tgt -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[Bug 1947624] [NEW] package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: il sottoprocesso installato pacchetto phpmyadmin script post-installation ha restituito lo stato di errore 1
Public bug reported: Linux Ubuntu 20.04.3 LTS OS just noticed: "package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: il sottoprocesso installato pacchetto phpmyadmin script post-installation ha restituito lo stato di errore 1" as a system error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: phpmyadmin 4:4.9.5+dfsg1-2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 15 02:27:58 2021 ErrorMessage: il sottoprocesso installato pacchetto phpmyadmin script post-installation ha restituito lo stato di errore 1 InstallationDate: Installed on 2021-10-14 (3 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: phpmyadmin Title: package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: il sottoprocesso installato pacchetto phpmyadmin script post-installation ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: phpmyadmin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947624 Title: package phpmyadmin 4:4.9.5+dfsg1-2 failed to install/upgrade: il sottoprocesso installato pacchetto phpmyadmin script post-installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1947624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942902] Re: Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split corruption"
** Description changed:
In order to address https://bugs.launchpad.net/bugs/1933074 the following
SAUCE patch was introduced.
Colin Ian King (1):
- UBUNTU: SAUCE: ext4: fix directory index node split corruption
+ UBUNTU: SAUCE: ext4: fix directory index node split corruption
- fs/ext4/namei.c | 12 +++-
- 1 file changed, 7 insertions(+), 5 deletions(-)
+ fs/ext4/namei.c | 12 +++-
+ 1 file changed, 7 insertions(+), 5 deletions(-)
Meanwhile the issue addressed by this patch was fixed upstream with
commit 877ba3f729fd ("ext4: fix potential htree corruption when growing
large_dir directories").
The upstream patch was already cherry-picked to hirsute with "upstream
stable patchset 2021-08-30" [1] commit ffcc845ec245) and focal with
"v5.4.140 upstream stable release" [2] (commit 93ad4c3f59c6).
[1] BugLink: https://bugs.launchpad.net/bugs/1942123
[2] BugLink: https://bugs.launchpad.net/bugs/1941798
- Therefore the SAUCE patch can be either dropped or reverted.
+ Therefore the SAUCE patch is obsolete and can be either dropped or
+ reverted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942902
Title:
Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split
corruption"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942902/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942902] [NEW] Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split corruption"
Public bug reported:
In order to address https://bugs.launchpad.net/bugs/1933074 the following
SAUCE patch was introduced.
Colin Ian King (1):
UBUNTU: SAUCE: ext4: fix directory index node split corruption
fs/ext4/namei.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
Meanwhile the issue addressed by this patch was fixed upstream with
commit 877ba3f729fd ("ext4: fix potential htree corruption when growing
large_dir directories").
The upstream patch was already cherry-picked to hirsute with "upstream
stable patchset 2021-08-30" [1] commit ffcc845ec245) and focal with
"v5.4.140 upstream stable release" [2] (commit 93ad4c3f59c6).
[1] BugLink: https://bugs.launchpad.net/bugs/1942123
[2] BugLink: https://bugs.launchpad.net/bugs/1941798
Therefore the SAUCE patch is obsolete and can be either dropped or
reverted.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942902
Title:
Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split
corruption"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942902/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924627] [NEW] Crash while installing Ubuntu 21.04
Public bug reported: Installer crashed while doing a fresh install of Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.14 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 20:08:24 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) ProcEnviron: LANGUAGE=pt_BR.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.11.0-14-generic linux-base linux-base SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubiquity-21.04.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924627 Title: Crash while installing Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1924627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922418] Re: Can't read files on /tmp
I ran the command, if need I can open a new one with ubuntu-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922418 Title: Can't read files on /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1922418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922418] Re: Can't read files on /tmp
Please note that this is on snap version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922418 Title: Can't read files on /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1922418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922418] [NEW] Can't read files on /tmp
Public bug reported: I have a .emc files that uses striata to decrypt to a /tmp folder and evince to read it. When trying to open the files I receive the message that the path is not accessible. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922418 Title: Can't read files on /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1922418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915562] Re: Libreoffice not loading installed fonts
I've downloaded new fonts from dafont.com to be used on a document. The extension for these fonts is ttf. These newly installed fonts are not showing on Libreoffice. You can try installing any font from the website. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915562 Title: Libreoffice not loading installed fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1915562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915562] [NEW] Libreoffice not loading installed fonts
Public bug reported: I've downloaded news fonts to be used on LibreOffice when I try to use them, the fonts are not loading ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 12 22:58:17 2021 InstallationDate: Installed on 2020-10-15 (120 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Snap: libreoffice 7.0.4.2 (latest/stable) SnapSource: ubuntu/+source/libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915562 Title: Libreoffice not loading installed fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1915562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911037] [NEW] nvidia-kernel-source-460 460.32.03-0ubuntu0.20.04.1: nvidia kernel module failed to build
Public bug reported: installation crashed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-460 460.32.03-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-36-generic Date: Mon Jan 11 15:16:08 2021 Dependencies: InstallationDate: Installed on 2020-12-29 (13 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 460.32.03-0ubuntu0.20.04.1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-460 Title: nvidia-kernel-source-460 460.32.03-0ubuntu0.20.04.1: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911037 Title: nvidia-kernel-source-460 460.32.03-0ubuntu0.20.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1911037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906998] Re: no headphone sound after update 18.04.5 kernel 5.4.0-56-generic
Follow the print from the screen running the pavucontrol ** Attachment added: "ubuntu-pavucontrol-sound-issue1.png" https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-osp1/+bug/1906998/+attachment/5444330/+files/ubuntu-pavucontrol-sound-issue1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906998 Title: no headphone sound after update 18.04.5 kernel 5.4.0-56-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-osp1/+bug/1906998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906998] Re: no headphone sound after update 18.04.5 kernel 5.4.0-56-generic
The headphone sound issue was temporarily resolved. I launched pavucontrol > input devices > and in the "sof-hda-dsp Headphone Microphone + Headset Microphone" I selected "Headphone Microphone" in the "Port" field. As default, the "Headset Microphone" is set. I have no idea why this worked. But every time I connect my headphone, I need to change the settings as mentioned above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906998 Title: no headphone sound after update 18.04.5 kernel 5.4.0-56-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-osp1/+bug/1906998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876879] Re: gnome-software cannot install classic snaps if a channel is selected
I have the same bug ** Attachment added: "snap-store.png" https://bugs.launchpad.net/snap-store-desktop/+bug/1876879/+attachment/5443882/+files/snap-store.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876879 Title: gnome-software cannot install classic snaps if a channel is selected To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1876879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
