[Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble
Now that upgrades from Jammy to Noble are re-enabled, the issue shows again on multiple flavors. I'm attaching the Jenkins artifacts for each jobs. Sometimes, it's when installing chromium, and sometimes firefox, but that doesn't change that the upgrade fails in the end. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043820 Title: Unable to contact snap store on Xubuntu from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble
** Attachment added: "lubuntu-jammy-noble.zip" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2043820/+attachment/5789081/+files/lubuntu-jammy-noble.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043820 Title: Unable to contact snap store on Xubuntu from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble
** Attachment added: "mate-jammy-noble.zip" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2043820/+attachment/5789079/+files/mate-jammy-noble.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043820 Title: Unable to contact snap store on Xubuntu from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble
** Attachment added: "xubuntu-jammy-noble.zip" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2043820/+attachment/5789080/+files/xubuntu-jammy-noble.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043820 Title: Unable to contact snap store on Xubuntu from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043820] Re: Unable to contact snap store on Xubuntu from Jammy to Noble
** Attachment added: "kubuntu-jammy-noble.zip" https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2043820/+attachment/5789078/+files/kubuntu-jammy-noble.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043820 Title: Unable to contact snap store on Xubuntu from Jammy to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2043820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067633] Re: `lxc` commands returning `Error: Failed to begin transaction: context deadline exceeded`
That seems to be the case, yes. Since the issue arises only now and then, I can't exactly be sure, but so far, I've absolutely never seen it on the HWE kernel. I've just encountered the following: ``` Jun 11 20:22:12 lxd-armhf-bos03-04 lxd.daemon[929146]: time="2024-06-11T20:22:12Z" level=warning msg="Transaction timed out. Retrying once" err="Failed to begin transaction: context deadline exceeded" member=1 ... Jun 11 21:49:08 lxd-armhf-bos03-04 kernel: Unable to handle kernel paging request at virtual address 37575eb49000 ... Jun 11 21:49:30 lxd-armhf-bos03-04 lxd.daemon[929146]: time="2024-06-11T21:49:30Z" level=warning msg="Transaction timed out. Retrying once" err="Failed to begin transaction: context deadline exceeded" member=1 Jun 11 21:49:35 lxd-armhf-bos03-04 lxd.daemon[929146]: time="2024-06-11T21:49:35Z" level=warning msg="Transaction timed out. Retrying once" err="Failed to begin transaction: context deadline exceeded" member=1 ``` It's the first time I see the `context deadline exceeded` before the kernel issue, but there was only one error, and it might be a legitimate one since the machine was probably under high load at that time, and there are also issues with the underlying arm64 hypervisor these days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067633 Title: `lxc` commands returning `Error: Failed to begin transaction: context deadline exceeded` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067633] Re: `lxc` commands returning `Error: Failed to begin transaction: context deadline exceeded`
This was hit again, as soon as the load rose with a big influx of jobs. Same situation, with the 5.15.0-107.117 kernel, and the same pattern in the logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067633 Title: `lxc` commands returning `Error: Failed to begin transaction: context deadline exceeded` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057490] Re: Crash during upgrade from Jammy/Mantic to Noble
No, I haven't seen that appear for a while now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057490 Title: Crash during upgrade from Jammy/Mantic to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067633] Re: `lxc` commands returning `Error: Failed to begin transaction: context deadline exceeded`
** Attachment added: "lxd-armhf-bos03-12.log" https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2067633/+attachment/5785825/+files/lxd-armhf-bos03-12.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067633 Title: `lxc` commands returning `Error: Failed to begin transaction: context deadline exceeded` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067633] Re: `lxc` commands returning `Error: Failed to begin transaction: context deadline exceeded`
** Attachment added: "lxd-armhf-bos03-16.log" https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2067633/+attachment/5785826/+files/lxd-armhf-bos03-16.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067633 Title: `lxc` commands returning `Error: Failed to begin transaction: context deadline exceeded` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067633] Re: `lxc` commands returning `Error: Failed to begin transaction: context deadline exceeded`
Upload the logs as attachment for longer lifespan. ** Attachment added: "lxd-armhf-bos03-09.log" https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2067633/+attachment/5785824/+files/lxd-armhf-bos03-09.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067633 Title: `lxc` commands returning `Error: Failed to begin transaction: context deadline exceeded` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067633] [NEW] `lxc` commands returning `Error: Failed to begin transaction: context deadline exceeded`
Public bug reported: Since around 2024-05-24, we've been experiencing an error in the autopkgtest.ubuntu.com infrastructure. The symptom is all `lxc` command invokation returning `Error: Failed to begin transaction: context deadline exceeded`, whether from the machine usually running the commands through an LXD remote (like `lxc list lxd-armhf-10.123.123.123:` to list containers on the given remote), or from the machine itself where the containers run on (`lxc list` on the machine `10.123.123.123`). This is happening quite randomly, sometime every few days, sometimes two times per day on the same machine. At one point, the 16 workers where in that same situation at the same time (around 2024-05-26, Sunday evening, when nobody took care of that). Those workers are all `arm64` Jammy machines, and the containers running on them are all `armhf` of all the supported Ubuntu releases. LXD version: 5.21.1 LTS, installed with snapd Kernel version: 5.15.0-107.117 Here are logs from around the issue on three machines: https://pastebin.ubuntu.com/p/ZMCbY2gHmX/ https://pastebin.ubuntu.com/p/kVBp7RQb2n/ https://pastebin.ubuntu.com/p/HyGsgdXkqb/ As we can see, the pattern is always the same, and has also been observed on other problematic machines: * First `kernel: physZlw57F: renamed from eth0` and following network related lines. These lines are common during normal operation, but also always happen before the kernel calltrace. That might still just be a coincidence. * Then `kernel: Unable to handle kernel paging request at virtual address` with the calltrace * Finally LXD starting to have issues with the `Failed to begin transaction: context deadline exceeded`. Sometimes these lines start to appear half an hour after the kernel issue, but we've never seen them before. One workaround we're experimenting right now is running the HWE kernel (version 6.5.0-35.35~22.04.1), and so far, the four machines running it haven't had the issue in two days, but it's still too early to conclude anything. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "`ubuntu-bug` report for one of those machines" https://bugs.launchpad.net/bugs/2067633/+attachment/5784269/+files/report-16 ** Also affects: lxd (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/2067633 Title: `lxc` commands returning `Error: Failed to begin transaction: context deadline exceeded` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036578] Re: ubuntu-unity-desktop debian not installed in automatic upgrade test
We are currently testing Ubuntu Unity just fine. Can we close this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036578 Title: ubuntu-unity-desktop debian not installed in automatic upgrade test To manage notifications about this bug go to: https://bugs.launchpad.net/auto-upgrade-testing/+bug/2036578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061918] Re: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1
A run of UbuntuStudio upgrade from Mantic to Noble did pass successfully. As I think this previously hit this bug, I'm marking it as Fix Released. ** Changed in: thunderbird (Ubuntu) Status: Confirmed => 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/2061918 Title: package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055044] Re: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x)
Same here, 2.10.36-3ubuntu0.24.04.1 fixed the crash on Noble running `sway`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055044 Title: GIMP crash at closure on systems with GLib 2.80.0 (and 2.79.x) To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/2055044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056461] Re: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
Latest findings: * The deepest loop that actually never exits is actually the `while not os.path.exists(fexit):` in the `eofcat` script. This is because the `block = os.read(0, 100)` always reads nothing. * From the guest: * `head`ing the `stdin` file doesn't help. * `tail`ing the `stdin` file does help, it unblocks the loop, just the same way as `stat`ing it. * From the host: * `stat`ing `stdin` doesn't change anything. * Appending more data to it doesn't change anything either. * This adds up with the fact that it's a kernel change in the guest that triggered the bug. * That `stdin` file is stored on a 9p shared FS. This might be a related change, but nothing confirmed yet: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c9b93cafb69cbbbe375de29c1ebf410dbc33ebfc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056461 Title: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056461] Re: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056461 Title: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056461] Re: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown
Okay, I've spend the last 24h digging into that issue, and here are my findings: * I confirm I can only reproduce the issue with 6.8 kernels, not with 6.5. Just to be sure, I've also tested 6.8.0-32.32 in kernel team's PPA, and it has the issue too. * Changing `--cpus` or `--ram-size` in `autopkgtest-virt-qemu` doesn't change anything. * The code responsible for this in autopkgtest is a wonderful piece of black magic: most lives in `virt/autopkgtest-virt-qemu`, and the main part is the `runcmd` script being crafted in the `make_auxverb` function. The hanging is the `# wait until command has exited` loop, that never exits. The most funny part is the new workaround that I found. Run the following from your host that runs `autopkgtest`. Obvious change the port number depending on which free port was available for `autopkgtest`. ``` ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 10022 ubuntu@localhost stat /run/autopkgtest/shared/job\*/stdin ``` For some reason, `stat`ing that file in the testbed makes the loop exit and everything continues as normal, meaning you can use the test results normally. I've seen this work at least 20 times on my machine, but I'd like someone else to confirm that this workaround indeed works. This bug is becoming more and more interesting, stay tuned for more adventures! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056461 Title: autopkgtest-virt-qemu on noble images sometimes hangs doing copydown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058227] Re: Crash during upgrade from Mantic to Noble due to Python 3.12
Yes, sorry, I got confused, upgrades from Mantic are still hidden behind the `-d` flag. That means you need `do-release-upgrade -d` to get it. Be advised though that if it's not enabled yet, there might be remaining issues that I'm not aware of, even if from my point of view, the jump from Mantic to Noble has been pretty much stabilized. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058227 Title: Crash during upgrade from Mantic to Noble due to Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/2058227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058227] Re: Crash during upgrade from Mantic to Noble due to Python 3.12
A quirk has been added to ubuntu-release-upgrader so this issue doesn't appear anymore, and upgrades from Mantic to Noble are already enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058227 Title: Crash during upgrade from Mantic to Noble due to Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/2058227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063361] [NEW] Selecting French at the beginning of installation doesn't change the language for the whole live desktop
*** This bug is a duplicate of bug 2013329 *** https://bugs.launchpad.net/bugs/2013329 Public bug reported: Steps to reproduce: * Use latest Noble Desktop release candidate: https://cdimage.ubuntu.com/daily-live/20240424/noble-desktop-amd64.iso * Boot it in a VM. * Select "Français" in the very first screen of the subiquity installer. * Now explore the various desktop menus and applications, they are not in french at all. * Clicking "Suivant" (Next) doesn't change anything, the desktop is still in English. * Going through to the keyboard layout selection and selecting a french keyboard does changes the layout for the whole desktop. * Typing `locale` in a terminal reports `LANG=C.UTF-8` and `LANGUAGE=`. Language is correctly set after installation+reboot. ** Affects: ubuntu-desktop-provision Importance: Undecided Status: New ** Affects: subiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: subiquity (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/2063361 Title: Selecting French at the beginning of installation doesn't change the language for the whole live desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2063361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058227] Re: Crash during upgrade from Mantic to Noble due to Python 3.12
** Changed in: apt-xapian-index (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058227 Title: Crash during upgrade from Mantic to Noble due to Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/2058227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063142] Re: Ubuntu Studio unable to upgrade from Mantic to Noble
*** This bug is a duplicate of bug 2061918 *** https://bugs.launchpad.net/bugs/2061918 This was confirmed as a duplicate of #2061918, which was resolved by archive surgery removing the libglib2.0-0 transitional package. Ubuntu Studio upgrades are now passing fine. ** Changed in: ubuntu-release-upgrader (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/2063142 Title: Ubuntu Studio unable to upgrade from Mantic to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063142] Re: Ubuntu Studio unable to upgrade from Mantic to Noble
*** This bug is a duplicate of bug 2061918 *** https://bugs.launchpad.net/bugs/2061918 ** This bug has been marked a duplicate of bug 2061918 package thunderbird 2:1snap1-0ubuntu1 failed to install/upgrade: new thunderbird package pre-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063142 Title: Ubuntu Studio unable to upgrade from Mantic to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063194] [NEW] Sync capnproto 1.0.1-4 (universe) from Debian unstable (main)
Public bug reported: Please sync capnproto 1.0.1-4 (universe) from Debian unstable (main) Changelog entries since current noble version 1.0.1-3build4: capnproto (1.0.1-4) unstable; urgency=medium * Add patch for FTBFS on 32-bit ARM after the time_t 64 transition. Thank you to Arnd Bergmann, Wookey, Tom Lee, and Andrey Rakhmatullin for their for help resolving this bug. (Closes: #1067916) -- tony mancill Mon, 15 Apr 2024 22:09:51 -0700 ** Affects: capnproto (Ubuntu) Importance: Undecided Assignee: Graham Inggs (ginggs) Status: 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/2063194 Title: Sync capnproto 1.0.1-4 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/2063194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063142] [NEW] Ubuntu Studio unable to upgrade from Mantic to Noble
Public bug reported: Jenkins catches this with `DEBIAN_FRONTEND=noninteractive`, but this also reproduces locally with a manual upgrade in a VM. Please find attached the artifacts from the Jenkins job, that contains all the logs of the operation. We can see a lot of removed libraries at the beginning of the upgrade, and then the first errors start to appear during the Thunderbird snap install. This may actually be the same bug as https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2061918, but nothing confirmed. I also noticed that it's removing a lot of packages that seemed quite important for Studio, like `blender`. ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Attachment added: "archive.zip" https://bugs.launchpad.net/bugs/2063142/+attachment/5769491/+files/archive.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063142 Title: Ubuntu Studio unable to upgrade from Mantic to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2063142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063128] [NEW] Upgrade from mantic to noble shows a debconf prompt
Public bug reported: Reproducer: * Run Ubuntu Studio Mantic in a VM * Run `do-release-upgrade -d` to upgrade it to Noble * After the package download phase, the packages upgrade starts, and you quickly get prompted by jackd2 asking `Enable realtime process priority?` This can be avoided with `export DEBIAN_FRONTEND=noninteractive`, that's why it didn't show up in the CI, but we can't expect users to rely on this. I've attached a screenshot of the prompt, that contains more details on what exactly is asked. ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "2024-04-22-16_31_14.png" https://bugs.launchpad.net/bugs/2063128/+attachment/5769449/+files/2024-04-22-16_31_14.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063128 Title: Upgrade from mantic to noble shows a debconf prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/2063128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062622] Re: autopkgtest broken on deb822 only testbeds
Here is a debdiff fixing the test by checking `/etc/passwd` instead of `/etc/apt/sources.list`. ** Patch added: "deb822.debdiff" https://bugs.launchpad.net/ubuntu/+source/apt-clone/+bug/2062622/+attachment/5768354/+files/deb822.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062622 Title: autopkgtest broken on deb822 only testbeds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-clone/+bug/2062622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062622] [NEW] autopkgtest broken on deb822 only testbeds
Public bug reported: Running apt-clone autopkgtest on a deb822-only such as a fresh Noble image breaks the tests, because they test for the presence of `/etc/apt/sources.list` on the system they run (not the embedded mocked test data). Checking for another file would fix this, or removing the "real system" test, since this is heavily dependent on the testbed, and thus quite brittle. Here is an example of broken run: https://autopkgtest.ubuntu.com/results/autopkgtest- noble/noble/arm64/a/apt-clone/20240419_132003_66310@/log.gz ** Affects: apt-clone (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/2062622 Title: autopkgtest broken on deb822 only testbeds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-clone/+bug/2062622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'
With the latest upload of mutter (46.0-1ubuntu7), we still have `gnome- shell` crashes during Jammy to Noble upgrades. Here is a recent oops: https://errors.ubuntu.com/oops/0ec860d4-fd60-11ee-9dae-fa163ec44ecd Let me know if you need anything else. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054761 Title: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland- allow-byte-swapped-clients' To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060117] Re: Merge autopkgtest 5.34 from Debian unstable
** Changed in: autopkgtest (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060117 Title: Merge autopkgtest 5.34 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2060117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058930] Re: Missing in i386 Packages index
Apparently this was linked to the extra `setup-commands` issue that made us loose the `proposed` pocket, and got "fixed" by updating the database with the `no-proposed` tag. TL;DR: fixed, and we didn't loose any cowboy specific to that issue, everything is fine. ** Changed in: libvpx (Ubuntu) Status: Fix Committed => 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/2058930 Title: Missing in i386 Packages index To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/2058930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058758] Re: FTBFS due to FORTIFY_SOURCE
Done here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067672 ** Bug watch added: Debian Bug tracker #1067672 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067672 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058758 Title: FTBFS due to FORTIFY_SOURCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvas-scanner/+bug/2058758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058758] Re: FTBFS due to FORTIFY_SOURCE
Second version with bug number in changelog and headers in patch. ** Patch added: "openvas-scanner_fortify-source.debdiff" https://bugs.launchpad.net/ubuntu/+source/openvas-scanner/+bug/2058758/+attachment/5758412/+files/openvas-scanner_fortify-source.debdiff ** Changed in: openvas-scanner (Ubuntu) Assignee: (unassigned) => Skia (hyask) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058758 Title: FTBFS due to FORTIFY_SOURCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvas-scanner/+bug/2058758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058758] [NEW] FTBFS due to FORTIFY_SOURCE
Public bug reported: Latest versions of `openvas-scanner` have stopped building due to `_FORTIFY_SOURCE` being redefined. Please find attached a debdiff fixing that. Current build on `noble-proposed`: https://launchpad.net/ubuntu/+source/openvas-scanner/22.7.9-1build1 ** Affects: openvas-scanner (Ubuntu) Importance: Undecided Status: New ** Attachment added: "openvas-scanner_fortify-source.debdiff" https://bugs.launchpad.net/bugs/2058758/+attachment/5758411/+files/openvas-scanner_fortify-source.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058758 Title: FTBFS due to FORTIFY_SOURCE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvas-scanner/+bug/2058758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058227] [NEW] Crash during upgrade from Mantic to Noble due to Python 3.12
Public bug reported: Upgrading from Mantic to Noble often triggers a crash related to Python 3.12 compatibility: ``` Traceback (most recent call last): File "/usr/sbin/update-apt-xapian-index", line 66, in import axi.indexer File "/usr/lib/python3/dist-packages/axi/indexer.py", line 27, in import imp ModuleNotFoundError: No module named 'imp' ``` I guess that the crash happens when the indexer code is called while still being in the Mantic version, but the default Python3 package has already been upgraded to 3.12. However, that situation doesn't happen all the time, and the upgrade is sometimes able to complete without crash. For some reasons, I mostly (only?) see this on Kubuntu upgrades. Maybe that situation could also happen while upgrading from Jammy, but as the upgrade is currently broken due to some other issues, I haven't seen it yet. ** Affects: apt-xapian-index (Ubuntu) Importance: Undecided Status: New ** Tags: rls-nn-incoming ** Attachment added: "_usr_sbin_update-apt-xapian-index.0.crash" https://bugs.launchpad.net/bugs/2058227/+attachment/5756751/+files/_usr_sbin_update-apt-xapian-index.0.crash ** Summary changed: - Crash during upgrade from Mantic to Noble + Crash during upgrade from Mantic to Noble due to Python 3.12 ** Tags added: rls-nn-incoming ** Description changed: Upgrading from Mantic to Noble often triggers a crash related to Python 3.12 compatibility: ``` Traceback (most recent call last): - File "/usr/sbin/update-apt-xapian-index", line 66, in - import axi.indexer - File "/usr/lib/python3/dist-packages/axi/indexer.py", line 27, in - import imp + File "/usr/sbin/update-apt-xapian-index", line 66, in + import axi.indexer + File "/usr/lib/python3/dist-packages/axi/indexer.py", line 27, in + import imp ModuleNotFoundError: No module named 'imp' ``` I guess that the crash happens when the indexer code is called while still being in the Mantic version, but the default Python3 package has already been upgraded to 3.12. However, that situation doesn't happen all the time, and the upgrade is sometimes able to complete without crash. + For some reasons, I mostly (only?) see this on Kubuntu upgrades. + Maybe that situation could also happen while upgrading from Jammy, but as the upgrade is currently broken due to some other issues, I haven't seen it yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058227 Title: Crash during upgrade from Mantic to Noble due to Python 3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/2058227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057490] Re: Crash during upgrade from Jammy/Mantic to Noble
There, I finally got an apport crash file. Is that enough for you to have a first look? ** Attachment added: "_usr_sbin_NetworkManager.0.crash" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+attachment/5756023/+files/_usr_sbin_NetworkManager.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057490 Title: Crash during upgrade from Jammy/Mantic to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057490] Re: Crash during upgrade from Jammy/Mantic to Noble
I'll see for reproducing that locally and provide you with a crash report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057490 Title: Crash during upgrade from Jammy/Mantic to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057490] [NEW] Crash during upgrade from Jammy/Mantic to Noble
Public bug reported: Our automatic upgrade testing reports crashes happening regularly, but not 100% time, during upgrades from Mantic to Noble. Here is the corresponding error tracker problem: https://errors.ubuntu.com/problem/0e53cd613cee458a7332d45bfb11c6daef4edeb3 Please also find attached an archive of Jenkins artifacts containing a lot of various additional logs from this morning's occurrence. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "mantic-noble-ubuntu-mate_network-manager_crash.zip" https://bugs.launchpad.net/bugs/2057490/+attachment/5755245/+files/mantic-noble-ubuntu-mate_network-manager_crash.zip ** Summary changed: - Crash during upgrade from Mantic to Noble + Crash during upgrade from Jammy/Mantic to Noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057490 Title: Crash during upgrade from Jammy/Mantic to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2057490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic
** Tags removed: verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051939 Title: [SRU exception] backport 5.32 to Jammy and Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056432] Re: Thunderbird profile not migrated to snap
*** This bug is a duplicate of bug 2056434 *** https://bugs.launchpad.net/bugs/2056434 ** This bug has been marked a duplicate of bug 2056434 Thunderbird profile not migrated to snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056432 Title: Thunderbird profile not migrated to snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056668] Re: Thunderbird Snap migration loses user profile
Here is how I worked around this: * close thunderbird, make sure it's not running in the background * `rsync -raxPHAX ~/.thunderbird/ ~/snap/thunderbird/common/.thunderbird/` * edit `~/snap/thunderbird/common/.thunderbird/profiles.ini` to make sure the only profile listed here is the one with the data (the biggest folder in `~/snap/thunderbird/common/.thunderbird/`) * run thunderbird So far, everything seems to be in order, including contacts, calendars on multiple accounts, sieve filter and message redirect plugins. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056668 Title: Thunderbird Snap migration loses user profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056562] Re: shim-signed 1.57+15.8-0ubuntu1 upgrade failing due to grub-common/2.12-1ubuntu3 still being present during installation
Solution worked here too. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056562 Title: shim-signed 1.57+15.8-0ubuntu1 upgrade failing due to grub- common/2.12-1ubuntu3 still being present during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/2056562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056334] Re: wrong version when building a package that's already part of the initial image
Thanks for the report. What version of autopkgtest are you using? I expect 5.32ubuntu3 from Noble? Is the same issue also happening using upstream's master branch? ``` git clone https://salsa.debian.org/ci-team/autopkgtest/ ./autopkgtest/runner/autopkgtest . -U -- lxd autopkgtest/ubuntu/noble/amd64 ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056334 Title: wrong version when building a package that's already part of the initial image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2056334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic
I've performed some manual verification on local podman containers and encountered no issue. Here are my tests in details, if someone wants to replicate them. I run the containers with the following command: ``` podman run -it --rm -v /srv/images/:/srv/images -v /dev/kvm:/dev/kvm ubuntu:jammy ``` This allows me both to have hardware acceleration for amd64 VM, and access to my existing VM images in `/srv/images`. Then in the container, I run this: ``` # Install right package apt update apt install -y lsb-release cat
[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200 here is a bug with a debdiff fixing the systemd tests-in-lxd issue. It will be block-proposed until a more important systemd SRU is done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051939 Title: [SRU exception] backport 5.32 to Jammy and Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055200] [NEW] tests-in-lxd is broken on Jammy with latest autopkgtest version
Public bug reported: With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "tests-in-lxd.debdiff" https://bugs.launchpad.net/bugs/2055200/+attachment/5749847/+files/tests-in-lxd.debdiff ** Description changed: - With autopkgtest 5.32 being SRU'd to Jammy, `tests-in-lxd` breaks + With autopkgtest 5.32 being SRU'd to Jammy[1], `tests-in-lxd` breaks because it can't patch `autopkgtest-build-lxd` anymore. Please find a debdiff attached to fix that issue. + + [1]: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055200 Title: tests-in-lxd is broken on Jammy with latest autopkgtest version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic
Regarding autopkgtest regressions: On Mantic: * the surf tests are very flaky[1], and have been so for a while[2]. With some retriggers, arm64 could pass, but with the current load on the infra, I couldn't make armhf to pass. Still the error reported in the log file[3] is `Too few characters detected (0)`, and is thrown by the surf test itself. Nothing in this test makes calls to autopkgtest provided commands, so I don't expect this regression to be actually caused by this current SRU. On Jammy: * gscan2pdf and sbuild were transient failures that retries fixed easily. * systemd, on the other hand, is directly related to this SRU: The systemd testsuite, for some reason, tries to patch the `autopkgtest-build-lxd` here[4], but the patch doesn't apply anymore. Given that this file is not present in more recent versions of systemd, I'm not sure if fixing this test is the right way to spend time. As for the `networkd-test.py` test, this one has been observed to be flaky in many other runs with different triggers [5] [1]: https://autopkgtest.ubuntu.com/packages/s/surf/mantic/armhf [2]: https://autopkgtest.ubuntu.com/packages/surf/jammy/armhf [3]: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-mantic/mantic/armhf/s/surf/20240227_144458_eb091@/log.gz [4]: https://git.launchpad.net/ubuntu/+source/systemd/tree/debian/tests/tests-in-lxd?h=ubuntu/jammy-updates#n12 [5]: See https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/systemd/20240227_140930_112c3@/log.gz and https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/systemd/20240227_132149_18a85@/log.gz and https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/s/systemd/20240227_051630_ed958@/log.gz for examples. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051939 Title: [SRU exception] backport 5.32 to Jammy and Mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/2051939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055146] Re: Upgrade from Jammy to Noble breaks
** Tags removed: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055146 Title: Upgrade from Jammy to Noble breaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2055146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055146] [NEW] Upgrade from Jammy to Noble breaks
Public bug reported: Hello there! Upgrading `dash` from Jammy to Noble is broken. Here is a quick reproducer: ``` podman pull ubuntu:jammy podman run -it --rm ubuntu:jammy sed -i 's/jammy/noble/' /etc/apt/sources.list apt update apt full-upgrade ``` This should end up with this error: ``` Setting up dash (0.5.12-6ubuntu3) ... Removing 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash' Removing 'diversion of /bin/sh to /bin/sh.distrib by dash' This should never be reached dpkg: error processing package dash (--configure): installed dash package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dash E: Sub-process /usr/bin/dpkg returned an error code (1) ``` As `dash` is pre-installed on almost every kind of Ubuntu, this breaks any upgrade from Jammy to Noble in practice. ** Affects: dash (Ubuntu) Importance: Undecided Status: New ** Tags: rls-nn-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055146 Title: Upgrade from Jammy to Noble breaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/2055146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
