just needs some time to figure things out, maybe it could be done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2114151
Title:
Vulkan broken on Pi @ Ubuntu Core 24 with Mesa 24.2.8
To manage notifi
FWIW I'm OK if this becomes a Won't Fix. Mostly just want a record of
that decision being taken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2114151
Title:
Vulkan broken on Pi @ Ubuntu Core 24 wit
https://lists.freedesktop.org/archives/dri-
devel/2021-September/325477.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2114151
Title:
Vulkan broken on Pi @ Ubuntu Core 24 with Mesa 24.2.8
To ma
turns out this is not a trivial backport even though it's from 5.16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2114151
Title:
Vulkan broken on Pi @ Ubuntu Core 24 with Mesa 24.2.8
To manage noti
** Changed in: mesa (Ubuntu Jammy)
Status: New => Invalid
** Changed in: mesa (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2114151
Title:
Vulka
Seems that the new mesa requires multisync support in drm/v3d, which got
added upstream in v5.16.
I don't think snaps for jammy should use mesa from noble+, as in here.
We'll have 25.0.7 soon in noble, and another set of similar issues might
crop up. But if it's unavoidable, then we'll have to man
Looks like the problem (and the solution) belong to the kernel. I
hopefully updated the bug tasks to better reflect this.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
You received this bug notificati
