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"
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).
This may be a duplicate of LP: #2037015 -- we saw this on mantic first,
then noble, in the oem-config process (the first-time setup wizard).
Previously it *didn't* affect jammy, but I'm currently running through
the ISO tests for the jammy .4 release and it's cropped up there now as
well.
--
You
** Changed in: ubuntu-release-notes
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037642
Title:
[FFe] Raspberry Pi 5 support
To manage
Added text to the release notes [1] detailing Pi 5 support, including
the planned SRU of libcamera support. Can others double-check the
raspberry pi sections look reasonable, and let me know if we want to
mention anything else specific?
I've also updated the "known issues" section, removing a
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/452468
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037642
Title:
** Changed in: rpi-eeprom (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: ubuntu-settings (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
The rpiboot package can be skipped for now; according to upstream the
updated package won't be ready at release. The separate bug LP: #2032178
will track updates if/when I can get the uploaded.
** No longer affects: rpiboot (Ubuntu)
--
You received this bug notification because you are a member
** Changed in: xwayland (Ubuntu Hirsute)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/1909678
Title:
Ubuntu 20.10 Desktop on Pi4B - screen-freeze after
I can replicate the issue on a freshly flashed groovy image. However,
once the image is fully upgraded (via a typical apt update+upgrade
followed by a reboot), I'm unable to replicate the issue any more.
Would be interested to hear if any one else can replicate the issue
either on hirsute (fresh
Unable to replicate the problem on hirsute (either a fresh install from
the image, or post all upgrades); currently flashing a groovy image for
testing, but it looks like whatever's causing this in groovy *might*
have been fixed by hirsute.
If I can replicate the issue on the groovy image, I'll
Looks like the armhf version of the package builds two (identical)
copies of various GL-related libs (EGL, GLESv2, etc): one with "mesa-
like" names (e.g. libEGL.so) and one with broadcom-specific names (e.g.
libbrcmEGL.so).
In either case, the produced libraries are for use with the "legacy"
12 matches
Mail list logo
