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
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
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
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
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
** 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
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
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
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
*** 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
** 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
*** 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:
*** 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
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
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
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
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
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
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
** 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
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)
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.
as-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
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:
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,
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
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
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
** 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.
*** 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
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
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
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
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
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
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
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
** 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:
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:
```
39 matches
Mail list logo
