** Changed in: mesa (Ubuntu)
Milestone: None => ubuntu-24.04.2
--
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/2082072
Title:
No support for Pi 2712D0 stepping
To manage notifications about
Verified jammy back-port with a manually rebuilt gnome content snap. On
Pi 4, current and proposed variants worked. On Pi 5 C1 (earlier
stepping), the same. On Pi 5 D0 stepping (2GB model only), current
version fails (crashes the entire desktop in fact), and proposed version
worked successfully.
O
Ah, oracular upload rejected because 3.8.12 already exists in the
archive ... but in plucky where it's been removed (still, the version
technically "exists" and with differing content). Re-uploading oracular
version with adjustment of version to 3.8.12~24.10.1
--
You received this bug notificatio
Sponsoring patches from comment 15 for oracular and noble with a couple
of minor changes. The noble upload needs a different version to ensure
it's earlier (using 3.8.12~24.04.1). The oracular upload I'll also tweak
to remove the .git garbage I accidentally introduced in the upload for
the py3-fix
*** This bug is a duplicate of bug 2083754 ***
https://bugs.launchpad.net/bugs/2083754
Appears to be another duplicate of LP: #2083754
** This bug has been marked a duplicate of bug 2083754
[SRU] Failed to upgrade xdiagnose (3.8.10ubuntu1) over (3.8.10)
--
You received this bug notificat
Thanks very much, Timo! Looks like ppc64el is having some issues in
autopkgtest, but they all look like tmpfails so I've just submitted
retries for all of those. The i386 regression looks more serious
(there's an actual fail involving a missing header there). I'll try and
have a look this evening.
Ohhh -- I hadn't realized the jammy backport had already been uploaded!
(the PPA linked earlier only had the noble build, hence my assumption)
Unfortunately, this is going to start becoming rather urgent in the next
couple of weeks as the D0 stepping starts appearing in the Pi 5 supply
chain, and
** Tags added: fr-9631
--
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/2082072
Title:
No support for Pi 2712D0 stepping
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
As all the seeded snaps on recent releases are still Core 22 based, it
appears the jammy fix is indeed now needed. I'll prepare a debdiff for
sponsorship.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/
Verification performed according to test plan on D0 and C1 stepping of
Pi 5, and older 8GB model of Pi 4. Proposed version operated correctly
on all boards.
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a m
@racb yes, that's correct -- I forgot to update the title!
--
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/2082072
Title:
No support for Pi 2712D0 stepping
To manage notifications about this bug
@tjaalton -- I think I put this on MM already, but just adding a
confirmation here that the staging build in your PPA does indeed fix the
mesa issue on the D0. Is there any possibility this is going to make it
into noble (and the mesa content snap) before oracular's release?
The reason I ask is th
** Description changed:
+ [ Impact ]
+
+ Pi 5 owners with the D0 stepping will find the noble (24.04) desktop
+ doesn't work at all, including login. While oracular desktop users have
+ a sufficiently up to date mesa, all snaps relying on noble's mesa
+ (firefox, thunderbird, and the snap-store -
** Summary changed:
- Mesa bump to 24.2 required for Pi 2712D0 stepping
+ [SRU] Mesa bump to 24.2 required for Pi 2712D0 stepping
--
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/2082072
Title:
[
I'm informed the three commits that require backporting for D0 support
are:
b545e78f12b v3dv: support 2712D0
1fc846dce39 v3d: support 2712D0
7b807c3e
My uneducated guess is that this is the source of the incompatibility:
/* 2712D0 (V3D 7.1.10) has included draw index and base vertex,
* shuffling all the fields in the packet. Since the versioning
* framework doesn't handle revision numbers, the XML has a
* diff
Related mesa bug:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29189
--
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/2082072
Title:
Mesa bump to 24.2 required for Pi 2712D0 stepping
Public bug reported:
The Raspberry Pi 5 2GB model now uses the D0 stepping of the 2712 SoC.
Unfortunately, this is only supported from Mesa 24.2.0 (see
https://docs.mesa3d.org/relnotes/24.2.0.html -- search for 2712D0). The
result is corrupted or blank output for the current Ubuntu 24.04.1 Pi
desk
Well, not exactly duplicate given that's targetting the snap-store-
desktop package specifically, but the symptom sounds identical, and I
wonder if it's the mesa package underlying both these things (given that
snap-store-desktop is packaged as a snap and is thus using the snap
version of mesa whic
Possible duplicate of LP: #2076919 ?
--
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/2081238
Title:
colors inverted on qxl graphics on lubuntu installer only with qxl
graphics on vm.
To manage
@mfo re: comment 91 on nordugrid: I've re-uploaded with the (horrible :)
spacing restored. The Breaks being against nordugrid-arc-arex and
nothing else is indeed deliberate and correct. The bug only affects
those binary packages which 1) contain python modules (which this
package does) and 2) are a
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"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2037015/+at
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 notifications
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 coup
** 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 o
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 tr
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"
grap
33 matches
Mail list logo
