Verified with upgrade of a Pi 4 on an SD card as described in the test
plan, only variant being to grab the noble tar-ball manually (as do-
release-upgrade won't allow --proposed with --devel). Worked happily,
KMS was present in the config.txt after the upgrade, and the HDMI audio
outputs appeared
** Changed in: deepin-log-viewer (Ubuntu Noble)
Assignee: Shengjing Zhu (zhsj) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058970
Title:
deepin-log-viewer 5.9.7+
I've re-sponsored updated debdiffs as requested
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921914
Title:
[SRU] package quickml 0.7-5.1 failed to install/upgrade: installed
quickml package
Confirmed; fix looks minimal and reasonable, sponsoring, thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060882
Title:
[SRU] usrpctl fails to run
To manage notifications about this bug
** Changed in: graphviz (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: graphviz (Ubuntu Jammy)
Status: Confirmed => In Progress
** Changed in: graphviz (Ubuntu Mantic)
Status: Confirmed => In Progress
** Changed in: graphviz (Ubuntu Noble)
Status:
** Description changed:
+ [ Impact ]
+
+ graphivz output is incorrect for SVG output when the "size" attribute is
+ set, as it implicitly is in several circumstances.
+
+ [ Test Plan ]
+
+ * sudo apt install imagemagick graphviz
+ * Grab fst.dot attached to this bug
+ * dot -Tpng fst.dot |
Brilliant, thanks very much for that -- I've upload the ocular version
to proposed, and I'll get the SRU uploads done later this morning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2015017
Title:
For SRU purposes, is there any chance I could ask you for a simple
reproducer case? It's okay if it uses jupyter, but I'm struggling to
come up with one without it and I've run out of time this evening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I quite understand the frustration with something that appears to be
abandoned. However, in this case it seems it was actually down to some
confusion over the versioning scheme which changed upstream from Debian
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980900 has the gory
details). It
Public bug reported:
New upstream version fixes future re-numbering of the gpiochip device on
Pi 5.
** Affects: rpi-lgpio (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, I'm afraid so. In fact I'm occasionally seeing it on boot as well
which seems to result in wayland crashing and the session falling back
to X11. Here's the backtrace from a crash on startup which resulted in
me starting an X11 session (and then wondering why the cursor
[ 47.898381] spl:
@viraniac well, you're absolutely right! Same SD card with a fresh noble
install, running on a Pi 4, first stock and second with a downgraded
dracut from mantic:
Pi 4B, stock -- 03:05
Pi 4B, downgrade -- 01:10
That is a pretty substantial regression, and diff'ing the initrds once
more showed
Importance: Undecided
Assignee: Dave Jones (waveform)
Status: Confirmed
** Changed in: ubuntu-raspi-settings (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: ubuntu-raspi-settings (Ubuntu)
Milestone: None => ubuntu-24.10
** Changed in: ubunt
Some results from some local testing. These tests were all performed on
the same SD card (a Samsung EVO Select 64GB) with fresh installs of the
jammy and noble server images, after running full upgrades and
rebooting:
Pi 5, noble -- 01:23
Pi 4B, noble -- 03:05
Pi 3B+, noble -- 05:19
Pi 5,
** Patch added: "initramfs.diff"
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2065180/+attachment/5776701/+files/initramfs.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065180
I've added some notes to the upstream bug, including an observation
about the regulatory-domain. My thoughts earlier that it doesn't affect
anything may be partially wrong (the issue still occurs, but
*potentially* only when the interface has no regdom prior to
authentication? We'll see what
Aha! I can reproduce this on RaspiOS bookworm too, but while the
messages appear in dmesg, they *don't* appear on the console, but that's
just due to different printk default (level 3 instead of 4 on Ubuntu).
So, this is an upstream issue.
--
You received this bug notification because you are a
I can reproduce this fairly reliably on the Ubuntu 24.04 Server for Pi
image. Strangely, it doesn't seem to occur on the initial use of the
wifi on boot, but running "netplan apply" (causing the interface to re-
connect to the AP), reliably causes several "set chanspec" messages to
appear in
This merge is no longer needed. Our only delta with Debian is adding
libraspberrypi-dev as a build-dependency which used to be required to
enable raspi compatibility. However, since switching everything over to
full KMS (in noble), we no longer need the raspi-specific bits.
--
You received this
Oh, many thanks to @marius.quabeck as well -- all the confirmations are
extremely helpful!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064208
Title:
Installer crashes when booting from USB on
@phrogger Brilliant, thanks for the confirmations; I've also tested a
Sabrent NVMe drive here (successfully) and an ancient Intel SSD over USB
(again successful). I think I'm happy to call this "good" at this point,
so I'll push ahead with trying to get LP: #2037015 SRU'd back to noble,
and then
** Description changed:
+ [ Impact ]
+
In switching Pi Server users over to the KMS overlay (as resolution to
LP: #2038924) we need an additional quirk for upgraders to migrate
config.txt (this will be similar, but not identical, to the one for LP:
#1923673).
+
+ If we do not migrate
** Summary changed:
- Migrate Pi users to KMS
+ [SRU] Migrate Pi users to KMS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065051
Title:
[SRU] Migrate Pi users to KMS
To manage notifications
** Also affects: ubuntu-release-upgrader (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
)
Importance: High
Assignee: Dave Jones (waveform)
Status: Confirmed
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Confirmed
** Changed in: ubuntu-release-up
It was a little tricky to confirm this one, given that the missing
dependency (libterm-readkey-perl) is seeded by server and cloud-image
(so the problem didn't immediately manifest in my test containers!), but
yes, confirmed. Targetting to affected releases.
One question about the proposed fix:
Hmm, one thing that a test build in oracular shows is that lintian
complains about the package depending on lsb-base, which is now an empty
transitional package. It appears the only reason it depends on it is for
the init-script in debian/quickml.init and there's no equivalent systemd
package.
Confirmed on all noted series; targetting accordingly. I was a little
nervous about rm'ing /etc/mailname in the postrm, but an apt-file search
confirms nothing else seems to own it (if something else owned it, it
might be better to create things like this in postinst, and just leave
them there in
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubuntu-manual-tests/+git/ubuntu-manual-tests/+merge/465423
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064208
Title:
Installer
** Changed in: network-manager (Ubuntu Lunar)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951586
Title:
Need option to specify wifi regulatory domain
To
I now have a test image that, using the patch from LP: #2037015, appears
to fix the installer issue when booting from USB. If volunteers are
interested in testing the image, I've made it available at:
https://zoidberg.waveform.org.uk/images/ubuntu-24.04-preinstalled-
desktop-arm64+raspi.img.xz
> So that means that with different monitors I could potentially not
need this vc4.force_hotplug option, right?
That is certainly my suspicion; it doesn't much surprise me that an LCD
controller isn't *quite* obeying the HDMI spec (or perhaps that it
expects to be part of something else which
> If I switch to the KMS overlay, the message is exactly the same, so it
means the EDID is accessible from the monitor in either case.
Not quite the case I'm afraid. The output you're quoting there is from
the pi's bootloader running on the GPU. So, what you've established
there is that the GPU
You are correct it was introduced for noble as, without the KMS driver,
there's no audio output over HDMI on the server image under the Pi 5
(LP: #2038924). KMS is also the only supported stack on the Pi 5
upstream, and rather than trying to support different stacks on
different models I opted to
** Changed in: ubiquity (Ubuntu)
Status: New => Triaged
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064208
Title:
** Description changed:
After writing the Ubuntu 24.04 Desktop for Raspberry Pi image to an SSD
drive with a USB3 interface (specifically; this issue does not occur
when booting from an SD card), booting the drive on a Pi 4 or Pi 5, and
running through the installer to the point where the
Public bug reported:
After writing the Ubuntu 24.04 Desktop for Raspberry Pi image to an SSD
drive with a USB3 interface (specifically; this issue does not occur
when booting from an SD card), booting the drive on a Pi 4 or Pi 5, and
running through the installer to the point where the
That's a different issue, LP: #2063365, which only started occurring
after the recent wifi firmware bump
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861338
Title:
RPI4 wifi unreliable when usb3
** Changed in: ubuntu-raspi-settings (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-raspi-settings (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Re-uploaded with bug ref
--
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 go to:
Public bug reported:
On the Ubuntu Desktop for Raspberry Pi (arm64) under noble, GIMP is
reliably crashing when closing the application with unsaved changes, and
selecting "Discard Changes".
Steps to reproduce:
* sudo apt install gimp
* Open GIMP with an image (right click image in Files, Open
I finally got around to testing this on noble: it's broken. Even more
than it was in mantic where at least it'd *list* the camera modules. Now
it can't even do that (but it works fine on RaspiOS with the same camera
modules). Sigh.
I'll release note this for now, and try and find time to dig into
** Also affects: ubuntu-meta (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/2062667
Title:
Fails on (and should be removed from) raspi desktop
I *think* you may have run into the issue with the installer crashing on
the timezone selection screen (which is directly after network selection
and which had a fatal issue with an out of date library; LP: #1987454).
That issue is now corrected on the current daily (from 4/22 which I'm
ISO
** Summary changed:
- Cannot play audio from server on older models
+ Cannot play audio via HDMI on server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063255
Title:
Cannot play audio via HDMI
Another interesting data-point: apparently mpg321 *isn't* broken on
noble. It works, but only with the headphone output (on those models
that have it, i.e. everything prior to the Pi 5). Same goes with ffmpeg;
no buffer xruns when outputting to the headphone socket.
Which leans me back towards
Hmm, I may have to revise this. It seems mpg321 (with ALSA, which is how
I've always tested the audio output) just doesn't work at all on any
model; just complains about libao driver everywhere.
Meanwhile, ffmpeg (my backup) works happily on the 4 and 5, but just
complains about buffer xrun
** 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
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
1 - 100 of 934 matches
Mail list logo
