** Description changed:
While attempting to play music as part of the ISO tests for the release,
while the vc4hdmi sound card appears in /proc/asound/cards, the mpg321
player used by the tests (which has never worked *well* on the older
models, but at least worked) failed with:
-
Public bug reported:
While attempting to play music as part of the ISO tests for the release,
while the vc4hdmi sound card appears in /proc/asound/cards, the mpg321
player used by the tests (which has never worked *well* on the older
models, but at least worked) failed with:
[0.029s]
** Bug watch added: Busybox Bugzilla #16042
https://bugs.busybox.net/show_bug.cgi?id=16042
** Also affects: busybox via
https://bugs.busybox.net/show_bug.cgi?id=16042
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Ah, so the code in ubuntu-settings postinst is taking care of deleting
the file on existing systems (i.e. upgraders) but that doesn't matter
for the fresh image where livecd-rootfs is presumably injecting the file
after the package is installed as part of the image build.
I ... thought I had a
Have now also observed this on the Zero 2W with the current noble daily
server image. Interestingly, it *didn't* occur directly on the image at
first. This booted happily on the Zero 2W. However, this same card was
then used to test a 3A+. On the 3A+ I regenerated the initramfs (testing
a reported
I'm sponsoring this under the assumption that the FFe from LP: #2054477
still applies (it covered the original upload that failed to pass
autopkgtests; this upload is intended to correct that failure).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for preparing these packages. I've successfully upgraded a
test Ceph cluster using them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057713
Title:
[SRU] ceph 16.2.15
To manage
Public bug reported:
The protection-domain-mapper package (and qrtr-tools) are both installed
by default on the Ubuntu Desktop for Raspberry Pi images, thanks to
their inclusion in the desktop-minimal seed for arm64. However, there's
no hardware that they target on these platforms, and the result
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/463674
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062564
Title:
[FFe] Seed pemmican
To
Public bug reported:
[ Impact ]
Add pemmican to raspi server and desktop images in order that Pi 5 users
can be notified if/when overcurrent or undervolt events occur
(potentially resulting in brownout, data-corruption, and all manner of
other symptoms typically caused as a result of undervolt).
We now have some better confidence that the failure is purely test-suite
based, and shouldn't affect the operation of the binary itself. Marking
won't fix and leaving the armhf tests disabled until such time as they
can be fixed properly (or removed).
** Changed in: mtd-utils (Ubuntu)
Revised patch with upstream bug links
** Patch added: "2-2062414.debdiff"
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+attachment/5767659/+files/2-2062414.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Build reference:
https://launchpad.net/ubuntu/+source/busybox/1:1.36.1-6ubuntu2/+build/28036868
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062414
Title:
busybox 1.36.1 FTBFS with current kernel
** Patch added: "1-2062414.debdiff"
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+attachment/5767655/+files/1-2062414.debdiff
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The networking/tc.c unit in busybox relies upon the CBQ (class based
queue) UAPI in the kernel. Unfortunately this was removed in [1]. At
present, there is no upstream patch (or even bug report that I can
find), and this close to the release patching the kernel to resolve
** Changed in: linux-raspi (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/2038924
Title:
No alsa sound cards on Pi 5
To manage notifications
Public bug reported:
Under the current noble daily server image for Raspberry Pi (arm64
architecture) I cannot launch an armhf container image using lxd from
the channel 5.21/stable/ubuntu-24.04 (build 28284). It *appears* to
launch successfully, and lxd reports no error yet afterward the
Potentially affected images:
As noted above this potentially affects *any* armhf image with boot
artifacts that require flashing (that are deb based). This potentially
affects our older Pi server armhf images (which, although they don't use
mtd-utils, do use flash-kernel). However, we're not
$ reverse-depends src:mtd-utils
Reverse-Recommends
==
* 0x [armhf](for mtd-utils)
* python3-binwalk (for mtd-utils)
Reverse-Depends
===
* flash-kernel [arm64 armhf](for mtd-utils)
Packages without architectures listed are
Additional context:
flash-kernel has several methods of "flashing" boot artifacts
(bootloaders, kernel, initrd, etc.) on various boards. Flashing may
actually mean flashing EEPROM (typically done via some other utility, in
many cases mtd-utils -- mtd incidentally is "Memory Technology Device",
I'll leave the flash-kernel portion of this open though, as it should
not be attempting to flash stuff when the destination is going to run
out of space.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, I'm wrong -- looks like 0.142ubuntu23 fixed it. I'll pull this hack
back out, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060032
Title:
Mitigate lack of space from new initramfs
To
Fixed with empty transitional package (kernel setup handles this
correctly)
** Changed in: pi-bluetooth (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
LP: #2060214 (FTBFS) was eventually resolved by disabling failing tests
on armhf to enable migration. Unfortunately, mtd-utils is the facility
used by flash-kernel (on several boards, as it's used in the "generic"
method) to flash boot artifacts to their destination.
Given
Attaching new debdiff based on the current noble version.
** Patch added: "1097467-3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5766422/+files/1097467-3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
chibi-scheme 0.9.1-3ubuntu1 (uploaded as fix for LP: #2009694) fails to
build on armhf:
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
Already done
** Changed in: matchbox-panel (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061552
Title:
0.9.3+git20100816-1build2 fails to build on armhf
To
Noble version sponsored; mantic and jammy versions may need adjustment
as they build with the following lintian error:
E: not-binnmuable-all-depends-any
N:
N: The package is not safely binNMUable because an arch:all package depends
on an arch:any package
N: with a strict (=
Looks good; adding targets for jammy and mantic, and sponsoring.
** Also affects: chibi-scheme (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: chibi-scheme (Ubuntu Mantic)
Importance: Undecided
Status: New
--
You received this bug notification because you
Updating test case to make clear that both the release and hwe kernels
require testing for this patch, but otherwise looks good -- sponsoring.
** Description changed:
[Impact]
libvpoll-eventfd is completely unusable as it will fail to install for a
Jammy user with the following error:
This looks good to me, and libelf1t64 is now built in armhf. Sponsoring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060212
Title:
U-Boot misses to invoke the UEFI boot manager
To manage
Patch looks mostly good. Needed a couple of trivial changes (run update-
maintainer to deal with maintainer address in d/control, and add bug-ref
in d/changelog), but I've sponsored with those changes, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
matchbox-panel 0.9.3+git20100816-1build2 fails to build on armhf:
panel.c: In function ‘panel_main’:
panel.c:1026:7: error: implicit declaration of function ‘msg_set_timeout’
[-Werror=implicit-function-declaration]
1026 | msg_set_timeout (panel, , );
|
Looks good to me; sponsoring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970521
Title:
[SRU] boinc-client crashes when started with core dump on Xubuntu
22.04
To manage notifications about
Looks good to me! Sponsoring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976312
Title:
[SRU] Pathological wont accept any input
To manage notifications about this bug go to:
Now builds happily on noble; sponsoring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058917
Title:
cvise 2.10.0-1 still depends on python-pytest-flake8 although upstream
dropped it
To manage
I've removed ubuntu-sponsors for now, but please feel free to re-
subscribe when it's clear ignition-cmake is also ack'd for FFe.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054477
Title:
[FFe]
Okay, ogre-next looks good for sponsoring, so I'm going ahead with that
one. I'm not clear from the above if FFe acceptance was given for
ignition-cmake so I'm leaving that for now.
One thing to bear in mind: the ogre-next build was pretty clean but did
throw up some lintian warnings about
Okay, this looks good, sponsoring packages from PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052575
Title:
[SRU] Update firmware to support autofocus
To manage notifications about this bug
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubiquity/+git/ubiquity/+merge/464248
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1987454
Title:
Port ubiquity to libsoup3 -
Patched in pi-gadget classic branch with commit
https://github.com/snapcore/pi-
gadget/commit/cebff92bd4b67d1bfffab5d98cdcefa38809b62e
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Sorry, I should give a bit more context on this issue to clarify things.
The test for this issue comes from the ISO tests for the Ubuntu Desktop
for Raspberry Pi images. The test intends to check whether a fresh
install can play a video "out of the box". The video used in the test is
Bah, looks like this upload got accidentally dropped by the subsequent
merge for noble. I'll rebase and re-proposed it when I've got some
time...
** Changed in: bash (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: bash (Ubuntu)
Assignee: Dan Bungert (dbungert) =>
I haven't managed to reproduce this on several systems (pi4 booting from
USB, pi5 booting from NVMe, etc). Setting to incomplete until anyone can
come up with a firm reproduction case.
** Changed in: pi-bluetooth (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
Fixed in linux-firmware-raspi 10
** Changed in: linux-firmware-raspi2 (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/1961907
Title:
Missing firmware link
This was fixed in linux-firmware-raspi 10 (finally :)
** Changed in: linux-firmware-raspi2 (Ubuntu Bionic)
Status: New => Won't Fix
** Changed in: linux-firmware-raspi2 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Looks like this was fixed with a sync from Debian.
** Changed in: veusz (Ubuntu Jammy)
Status: Confirmed => Fix Released
** Changed in: veusz (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: xilinx-bootgen (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/1998732
Title:
[SRU] Backport xilinx-bootgen 2022.2-2ubuntu1 to kinetic and
** Changed in: u-boot-xlnx (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/2006448
Title:
[SRU] Backport 2022.01-2022.1-update3+repack-0ubuntu1 to kinetic
** Changed in: 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/2056234
Title:
[needs-packaging] nobodd
To manage notifications about this bug go to:
Failed to reproduce on noble beta images; marking invalid as that's two
failures now.
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- No login sound on Ubuntu desktop
+ No welcome/login sound on Ubuntu desktop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060693
Title:
No welcome/login sound on Ubuntu
** Description changed:
Whoops! Removed one of the bluetooth firmwares too soon; need to add
brcm/BCM43430A1.raspberrypi,3-model-b.hcd back in (until we can get
- bluez-firmware into main next cycle and then remove it again; see LP:
- #2058234 for context)
+ bluez-firmware into restricted
Public bug reported:
The Pi Zero 2W, 2B, and 3B all fail to light their power LED once the
kernel starts booting under noble (I hope this is only on noble; I only
just noticed this during ISO testing and it's quite possible I missed it
on earlier revisions...).
Specifically, on the 2W (which
** Description changed:
- It's looking for bcm2710-rpi-2-b.dtb instead of bcm2709-rpi-2-b.dtb. The
- latter is correct for armhf, but not arm64. The 2B is only compatible
- with arm64 in revision 1.2 of the board, but given we only support arm64
- images from noble, it's reasonable to replace the
Public bug reported:
Reports AA:AA:AA:AA:AA:AA instead of the serial derived MAC it should
have
** Affects: pi-bluetooth (Ubuntu)
Importance: Undecided
Assignee: Dave Jones (waveform)
Status: Confirmed
** Changed in: pi-bluetooth (Ubuntu)
Status: New => Confir
Public bug reported:
Appears this was added in 1.20; we should merge that.
** Affects: pi-bluetooth (Ubuntu)
Importance: Undecided
Assignee: Dave Jones (waveform)
Status: Confirmed
** Changed in: pi-bluetooth (Ubuntu)
Status: New => Confirmed
** Changed in:
berry Pi 2 rev
1.2" entry in the db on noble onwards (but this change should *not* be
backported).
** Affects: flash-kernel (Ubuntu)
Importance: High
Assignee: Dave Jones (waveform)
Status: Confirmed
** Changed in: flash-kernel (Ubuntu)
Status: New => Confirme
This was fixed in 11-0ubuntu1 of linux-firmware-raspi.
** Changed in: linux-firmware-raspi (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/2017132
Title:
)
Importance: High
Assignee: Dave Jones (waveform)
Status: Confirmed
** Changed in: linux-firmware-raspi (Ubuntu)
Status: New => Confirmed
** Changed in: linux-firmware-raspi (Ubuntu)
Importance: Undecided => High
** Changed in: linux-firmware-raspi (Ubuntu)
As
This was fixed with version 11 of linux-firmware-raspi in noble; I don't
see a great deal of point in expending the effort to backport this to
mantic, however, so I'll set that to invalid.
** Changed in: linux-firmware-raspi (Ubuntu)
Status: Confirmed => Fix Released
** Changed in:
Similar results on the 3A+ under the KMS overlay (with cma-128 to ensure
it boots, re LP: #2060300); except here ffmpeg results in:
[alsa @ 0xd948a930] ALSA buffer xrun
[alsa @ 0xd948a930] ALSA write error: Cannot allocate memory
[aost#0:0/pcm_s16le @ 0xd94c5a30] Error
Argh, another wrinkle in this story: during ISO testing of the server
images, I also tried the audio output tests with both the current setup
(framebuffer driver) and the intended setup (KMS driver). The KMS driver
works happily for audio output on the Pi 4 and 5. But on the 3B+, it
throws the
Public bug reported:
See PR#8 in https://github.com/waveform80/rpi-lgpio/pull/8
** Affects: rpi-lgpio (Ubuntu)
Importance: High
Assignee: Dave Jones (waveform)
Status: Confirmed
** Affects: rpi-lgpio (Ubuntu Mantic)
Importance: High
Assignee: Dave Jones (waveform
Setting to "high" because this affects the usability of several seeded,
and quite basic applications (settings and the file manager to name but
two).
** Changed in: gtk4 (Ubuntu)
Status: New => Confirmed
** Changed in: gtk4 (Ubuntu)
Importance: Undecided => High
** Tags added:
Adding affects packagekit as I've no idea if this is totem's fault or
packagekit's.
** Also affects: packagekit (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And is occurring on the noble images again...
** Changed in: pipewire (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1993347
Title:
Wrong audio
Public bug reported:
While attempting to play a video on Ubuntu noble desktop for raspberry
pi, totem attempts to locate a package for the H.264 codec but cannot
find a service providing org.freedesktop.PackageKit. This is strange
given that packagekit is installed, provides packagekit.service,
There's an intriguingly different style of corruption in the noble
images on the Pi 5. It's still just on the installer's slides, but it's
more ... "chunky"? I'll attach a photo...
** Attachment added: "slide-corruption-2.jpg"
*** This bug is a duplicate of bug 1874927 ***
https://bugs.launchpad.net/bugs/1874927
Duplicate of LP: #1874927 ?
** This bug has been marked a duplicate of bug 1874927
do-release-upgrade's upgradeable package check doesn't consider kept back
packages
--
You received this bug
*** This bug is a duplicate of bug 1874927 ***
https://bugs.launchpad.net/bugs/1874927
Duplicate of LP: #1874927 ?
** This bug has been marked a duplicate of bug 1874927
do-release-upgrade's upgradeable package check doesn't consider kept back
packages
--
You received this bug
Hmm, I see that was released on 21st of March; I'm *fairly* sure the
excess size of the initramfs was still occurring after that but I'll
double check this evening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Under the Ubuntu desktop for Raspberry Pi, for several recent releases,
the startup sound from the Yaru sound theme has failed to play both at
the initial setup (from oem-config, where it used to play just before
language selection), and at the greeter.
This worked in Jammy
Screenshot of the greeter showing lack of icons on radio buttons for
selecting Ubuntu Pro
** Attachment added: "greeter1.png"
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+attachment/5762735/+files/greeter1.png
--
You received this bug notification because you are a member of
Screenshot of gnome maps showing lack of controls in router planner and
title bar
** Attachment added: "gnome-maps1.png"
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+attachment/5762734/+files/gnome-maps1.png
--
You received this bug notification because you are a member of
Public bug reported:
While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta, I
noticed that all GTK4 applications appear to be missing various icons.
All lack the minimize / maximize / close icons (which are left as three
empty circles on the window), and others lack icons within
Screenshot of nautilus showing lack of icons on left bar and title bar
** Attachment added: "nautilus1.png"
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+attachment/5762733/+files/nautilus1.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Screenshot of gnome-control-center showing lack of icons on left menu,
and title bar
** Attachment added: "gnome-control-center1.png"
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+attachment/5762732/+files/gnome-control-center1.png
--
You received this bug notification
Public bug reported:
When shutting down Ubuntu noble desktop on my Pi 5, I consistently see
the following kernel errors briefly flash by before the machine shuts
down:
kernel: spl: loading out-of-tree module taints kernel.
kernel: zfs: module license 'CDDL' taints kernel.
kernel: Disabling
I believe this is also "fixed" (or rather wasn't an issue) with the
noble kernel; at least testing the current noble desktop beta image from
an SD card shows an NVMe drive attached to a pimoroni base. I'll mark
this as Fix Released; please feel free to re-open if this re-appears on
the noble
Team subscription added
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055434
Title:
[MIR] pemmican
To manage notifications about this bug go to:
Incidentally, this is the product in question:
https://www.raspberrypi.com/products/dac-plus/
I've been using one of the older IQaudIO DAC+ boards, but I'm told
they're electrically equivalent; they were just rebranded when Raspberry
Pi started producing them directly.
--
You received this bug
Public bug reported:
Came across something bizarre when investigating the audio situation
with server on the Pi 5 (LP: #2038924). Moving the server images to use
the KMS overlay solves the situation, and would be preferable as it
would eliminate another difference between server and desktop
Public bug reported:
First reported on the Raspberry Pi forums
(https://forums.raspberrypi.com/viewtopic.php?p=2162847), I've since
confirmed that the Raspberry Pi DAC+ HAT (formerly the IQaudIO DAC+ HAT,
which is basically the same board) works happily under RaspiOS on the Pi
5, but not Ubuntu
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubuntu-seeds/+git/ubuntu-seeds/+merge/463674
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055434
Title:
[MIR] pemmican
To
I'm currently investigating switching the server images to load the kms
overlay by default (they don't currently). This does appear to fix the
issue, in that the vc4-hdmi ports show up in /proc/asound/cards once the
overlay is loaded. Unfortunately, it also appears to break boot on the
512MB 3A+
I'm fairly sure we can just ditch that file entirely in ubuntu-raspi-
settings now, as ubuntu-desktop-settings should provide an equivalent
under /lib.
** Changed in: ubuntu-raspi-settings (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: ubuntu-raspi-settings (Ubu
Public bug reported:
Discovered on an image upgraded from jammy to noble:
jammy's boot partition is a mere 256MB. This was fine when the initrd
was relatively minimal, as was the case with the split linux-modules-
extra, which resulted in initrd's with a size around ~30MB. However,
with noble,
I'll have a look at this next week; there's a bunch of things I need to
shove in ubuntu-raspi-settings anyway this cycle and something like this
is already present in there but I'll see if it needs enhancing (it won't
be able to rely on raspi-config though, so I'll have to change those
bits out).
I see a basically identical message (and dmesg apparmor output) with
"lxc profile edit default":
unshare: write failed /proc/self/uid_map: Operation not permitted
And the dmesg entry:
[ 194.625507] audit: type=1400 audit(1711709095.424:293):
apparmor="DENIED" operation="capable"
Yes, this is indeed the issue that 0.7.0-3 fixed, which it would seem
would be reasonable to backport (same upstream version as is currently
in jammy, with addition of one patch from Debian to fix the issue). I'll
prepare an upload.
** Bug watch added: Debian Bug tracker #1009916
** Description changed:
+ [ Impact ]
+
+ The version in Ubuntu 22.04 of python3-build cannot create a virtual
+ environment, which severely hampers the use of the package. While this
+ can be worked around to some extent by installing python3-virtualenv,
+ this still fails with the use of
Tested locally in a focal container with the quick test plan and it does
indeed fix the issue. The patch looks good too, sponsoring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876597
Title:
Patch looks good, and the test case is well written; sponsoring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056361
Title:
[SRU] python3-qrencode fails with SystemError about PY_SSIZE_T_CLEAN
> If you have a bunch of unmanaged interfaces, then you should use a
> drop-in configuration to pass the --any flag to
> systemd-networkd-wait-online:
>
> cat > /etc/systemd/system/systemd-networkd-wait-online.service.d/any.conf <<
> EOF
> [Service]
> ExecStart=
>
** 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/2059123
Title:
Build failure due to t64 on armhf
To manage notifications about this bug go to:
Public bug reported:
There is an assumption in src/client/protocol.c that tv_sec is the same
size as "long", which is no longer the case on armhf, causing a build
failure in 1.15.4-1build1.
** Affects: cowsql (Ubuntu)
Importance: Undecided
Assignee: Dave Jones
Patch from upstream: https://github.com/cowsql/cowsql/pull/19
** Tags added: time-t
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059123
Title:
Build failure due to t64 on armhf
To manage
Argh, that upload was rejected because there's a deleted 9.5-6ubuntu0.2
in noble-proposed as a no-change rebuild, which therefore has different
content (https://launchpad.net/ubuntu/+source/sagemath/9.5-6ubuntu0.2)!
I'll re-upload with some suitably weird version like 9.5-6ubuntu0.1.1
--
You
** Bug watch added: Debian Bug tracker #1067687
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067687
** Also affects: lcov (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067687
Importance: Unknown
Status: Unknown
--
You received this bug notification
101 - 200 of 23322 matches
Mail list logo
