"No suitable EGL configs found" on desktop-next
Bug #1457458 reported by
Chris Coulson
This bug affects 13 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Oxide |
Fix Released
|
Medium
|
Chris Coulson | ||
1.8 |
Won't Fix
|
Medium
|
Chris Coulson |
Bug Description
The Mir backend for Mesa doesn't support pbuffer surfaces, so we have a hack in Oxide to modify the attributes passed to eglChooseConfig to exclude EGL_PBUFFER_BIT from EGL_SURFACE_TYPE on Mir. It's a hack because it uses the EGL_PLATFORM environment override, which desktop-next sessions used to set. However, they no longer do that and mesa auto-detects the platform instead, breaking Oxide.
Related branches
Changed in oxide: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in oxide: | |
milestone: | none → branch-1.9 |
Changed in oxide: | |
assignee: | nobody → Chris Coulson (chrisccoulson) |
status: | Triaged → In Progress |
Changed in oxide: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
>>Fix Released
Recently upgraded. The browser crashes as before.