Looks good, sponsoring for oracular
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072500
Title:
[SRU] Add Microchip PIC64GX Curiosity Kit support
To manage notifications about this bug go to:
Sponsoring for oracular; this will need an ack from an AA to enter the
archive. The question then is whether to MIR this package, given the
intent is obviously to include it in images. I guess that'll come down
to how "official" we want those images to be (and that may come down to
a question of
Re: the armhf and arm64 build failures, this is already tracked in LP:
#2039967 but given they also failed in noble's release pocket these
shouldn't matter for migration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@nathan-openid-1 That's a separate issue to this one -- I would suggest
opening a separate issue against the linux-raspi package
(https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+filebug),
providing steps to reproduce if possible, and a link to the upstream bug
--
You received this bug
I included mantic as well since it's technically affected, but I suspect
it may go EOL before the fix lands there. Sponsoring for oracular in the
meantime, and I'll paste Doug's SRU template in shortly (thanks very
much for preparing that!)
** Summary changed:
- gdebi-gtk calls pkexec
Targetting to jammy, noble, and oracular.
** Also affects: gdebi (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: gdebi (Ubuntu Oracular)
Importance: Medium
Assignee: Utkarsh Gupta (utkarsh)
Status: Confirmed
** Also affects: gdebi (Ubuntu Mantic)
** Changed in: cqrlog (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: cqrlog (Ubuntu)
Assignee: (unassigned) => Dave Hibberd (hibby)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
I haven't had the time to try it myself, but I'm guessing the installer
*may* well work, provided the lowlatency kernel option is deselected.
There may be some amd64-only packages it attempts to pull in though, I'm
not sure.
That said a while back I did succeed in hammering together something
@kevinyeh Oh, then I'm wondering if it is a boot firmware issue at all;
the current Core 20 images were generated in January 2023, after the
current point release of focal from August 2022, so they should have
firmware at least as recent as the focal images.
How far does the boot process get on
The lowlatency kernel isn't supported on the Pi, and flash-kernel won't
permit it to be flashed (because you'd be left with an unbootable
system).
Ideally the studio installer should detect this and not select the
option by default (or better still, disable it), but I'm not sure
there's a simple
** Merge proposal linked:
https://code.launchpad.net/~waveform/pollinate/+git/pollinate/+merge/468065
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070268
Title:
pollen man-page in wrong
Public bug reported:
The pollinate(1) man-page specifies pollen(8) references in several
places, which are turned into links on manpages.ubuntu.com [1].
Unfortunately, pollen is documented in section 1 [2], so these links are
all dead.
[1]:
** Merge proposal linked:
https://code.launchpad.net/~tobhe/ubuntu-seeds/+git/ubuntu-seeds/+merge/467849
--
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
If the bump enables the new boards to boot we will have to look at a
potential point release for focal on the Pi images.
Note to self: because this bump involves a rename of the package (from
linux-firmware-raspi2 to linux-firmware-raspi) this will also involve
adjusting the seed ... argh, which
Test firmware is available in
https://launchpad.net/~waveform/+archive/ubuntu/firmware. Please run
through these steps for testing:
* Flash current focal server images (armhf and arm64) from
http://cdimage.ubuntu.com/releases/20.04.5/release/ to boot media (SD
card) for testing
* Boot the media
Some quick clarifications to Loic's excellent notes:
> ... it should probably also run when f-k gets updated but I think it
doesn't right now ...
It should indeed be running when f-k is updated. That's something I
fixed a while ago (LP: #1667742), and then fixed the fix (LP: #2007827).
As you
Hi all,
It turns out I agreed after some more thinking on the subject, so have
committed a fix for this as 2.5.2-5 in Debian:
https://tracker.debian.org/news/1538653/accepted-cqrlog-252-5-source-
into-unstable/
Code's on salsa if you want to try a build and install - I ran it
through my build
** Tags removed: indeed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977919
Title:
Docker container creation causes kernel oops on linux-aws
5.13.0.1028.31~20.04.22
To manage notifications
** Changed in: ubuntu-raspi-settings (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: ubuntu-raspi-settings (Ubuntu)
Milestone: None => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
The Ubuntu Desktop for Raspberry Pi images include cloud-init since
noble. The cloud-init seed is redirected to the (FAT formatted) boot
partition on the Ubuntu Server for Raspberry Pi images, and for
consistency and ease of use, this should be replicated for the desktop
Triggered autopkgtests via requested link, and added targetting for
affected series (and package).
** Also affects: mariadb-10.6 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mariadb (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: mariadb-10.6
> - This package does not yield massive lintian Warnings, Errors
Building locally against oracular presents the following:
E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/]
E: lenovo-cfgservice: dir-or-file-in-opt [opt/fcc_lenovo/configservice_lenovo]
E: lenovo-cfgservice:
Hi Aleksandr -- thanks for the patch. There's a few things I'd like to
rectify, and a couple of questions which should probably be answered
before this can be sponsored. If we're going to introduce a delta on
Debian, we should ensure things are forwarded so the delta can be
resolved in time. To
Hi Dave,
The computer I had been using when I reported the problem physically
broke. I was without a personal computer for a long time. However, I
recently got a new one, put Manjaro Linux on it, and am pleased to
report that downloading malware definitions was a lot easier compared to
when I
Oh, one other thing to check -- I did note that for some reason the
boards aren't auto-detected under Ubuntu. I did need to add
"dtoverlay=iqaudio-dacplus" to /boot/firmware/config.txt on my board.
I'm not sure why the auto-detection isn't operating for us (the overlays
are present and in the
I was testing with a black IQaudIO Pi-DAC+ board (I don't have one of
the newer ones) -- and that was working for me. Are you seeing the same
symptoms, i.e. the particular lines of output in dmesg quoted in the
original report?
--
You received this bug notification because you are a member of
As requested, results from running stock noble on the same Pi 4B with
the same SD card as before. First, stock noble (with all available
upgrades):
$ sudo hyperfine --warmup 1 -r 5 "update-initramfs -u"
Benchmark 1: update-initramfs -u
Time (mean ± σ): 193.558 s ± 2.334 s[User: 77.577
I think the consensus at this point is that, while this manifests in LXD
(and chroot), it's ultimately a kernel configuration issue. Marking lxd
invalid.
Just to fill in a bit of background, there's been some discussion
between kernel team and foundations what the correct course of action
here is
> Was it it more than a red line in systemctl status output? Does it
have annoying logging behaviour or break some other service if it isn't
running?
A red line in systemctl status output is sufficient, to my
understanding? I was under the impression that, absent any hardware
issues, a freshly
Verified on a Pi 5 8GB running the current release of noble with an
IQaudio DAC+ HAT. Played some Rolling Stones, and some Tangerine Dream
very nicely! Also verified SPI still appeared operable (at least with a
low-speed ADC), and that the DAC+ still operated on a 3B+ board.
** Tags removed:
Public bug reported:
An unresolvable problem occurred while initializing the package
information.
Please report this bug against the 'update-manager' package and include the
following error message:
E:can not open
/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_jammy-backports_InRelease
This is likely to be a linux-raspi issue since armhf containers are
apparently working happily in the autopkgtest cloud. Further, armhf
chroots are also failing under linux-raspi with a Futex error from the
kernel (will attempt to add some detail on this in due course).
** Also affects:
Results on a Pi 4B booting from SD card. Stock noble:
$ sudo hyperfine -r 5 "update-initramfs -u"
Benchmark 1: update-initramfs -u
Time (mean ± σ): 189.984 s ± 1.618 s[User: 75.720
Sponsored linked branch after patching for oracular. Once this lands for
oracular, this should be converted to SRU for noble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062948
Title:
@teward -- yes, I'm aware of the requirement that each release needs a
higher version, and the versions proposed in the patches do conform to
this requirement. It just seems a bit odd that the mantic patch proposes
a 0.1 suffix while the noble patch proposes a 0.24.04.1 suffix.
Could/should the
Leaving ubuntu-sponsors subscribed for the SRU uploads
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957168
Title:
[SRU] fwbuilder crashes in Noble when trying to create almost any type
of new
** Merge proposal linked:
https://code.launchpad.net/~liushuyu-011/ubuntu/+source/intel-mediasdk/+git/intel-mediasdk/+merge/464771
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062948
Title:
The branch in the linked merge proposal is for noble, but the issue is
still present in the oracular package (by the looks of the version
numbers it's presumably present in at least noble, mantic and possibly
earlier too).
I've sponsored this for oracular for now; if that lands successfully (I
** Merge proposal linked:
https://code.launchpad.net/~liushuyu-011/ubuntu/+source/chmlib/+git/chmlib/+merge/464769
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062947
Title:
chmlib: FTBFS:
Reviewing the patches, they mostly look fine but I'm a bit confused as
to why the version numbering goes from a ubuntu0.24.04.1 suffix in the
noble patch, to a ubuntu0.1 suffix in the mantic patch (noting that both
have the same base version, 1:5.1+git20220924+dfsg-1). Obviously that'll
still work
Sync to oracular is now done so I'll mark this Fix Released, and target
to the affected series
** Also affects: xxdiff (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: xxdiff (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: xxdiff (Ubuntu
Confirmed on oracular; targetting for affected series and sponsoring for
oracular, thanks!
** Also affects: python-evtx (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: python-evtx (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: python-evtx
Confirmed on an oracular desktop VM with the current release (5.3.7-8).
Patch needed a quick rebase against that current version (and update-
maintainer running, but that may be because the current release has no
Ubuntu changes). Anyway, sponsoring for oracular, and adding noble to
the targetting.
I do like the addition of the compare test; it's a bit "magic" but the
fact it's comparing against an image from the actual installation
(/usr/share/xrdp/xrdp_logo.bmp) does demonstrate the operation of the
package very nicely.
I did try and run the tests locally under autopkgtest but
* straight-forward and care must be taken to ensure that all
relevant files end up in their correct locations with the correct
diversions.
** Affects: linux-firmware-raspi2 (Ubuntu)
Importance: Undecided
Assignee: Dave Jones (waveform)
Status: New
** Affects: linux-firmware-raspi2
** Summary changed:
- Quassel opens "another" icon under Gnome
+ Some Qt-based applications open "another" icon under Gnome
** Description changed:
- I'm unsure if this is a bug in quassel, or in the gnome dock itself.
- Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the
-
Curiously, I've seen this issue with several Qt-based applications
(Quassel, Veusz, and OpenSCAD) under noble, as reported in LP: #2044382,
but I've not seen it with Firefox (which isn't Qt-based to the best of
my knowledge?).
--
You received this bug notification because you are a member of
Public bug reported:
After registering my Ubuntu 24.04 desktop for Raspberry Pi with
Landscape, the following warnings periodically appear in the system
journal (every few minutes):
May 23 12:30:33 kermit landscape-client[23891]: 2024-05-23 12:29:23,114 WARNING
[MainThread] Unable to get
Public bug reported:
On the Ubuntu noble desktop for Raspberry Pi, the system journal has
numerous of the following entries:
May 23 10:30:29 kermit tracker-miner-f[11130]: Could not get landlock supported
ABI: Operation not supported
May 23 10:30:29 kermit tracker-miner-f[11130]: Refusing to
** Changed in: pemmican (Ubuntu)
Status: Triaged => 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/2062564
Title:
[FFe] Seed pemmican
To manage notifications about this bug go
@vanvugt Indeed -- I'm confident that's the root cause at this point;
just waiting for that to land in devel, then I can convert the bug to
SRU, wait for that to land, then request an image re-spin from the
release team
--
You received this bug notification because you are a member of Ubuntu
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]
1 - 100 of 23320 matches
Mail list logo
