mesa GLX change leads to wine showing GLXBadFBConfig
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mesa (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
A mesa GLX change (somewhere between the 20.0.4 and 21.0.3) causes both wine and Proton (on an older system that does not have Vulkan.. SandyBridge, OpenGL 3.3..) to exit with GLXBadFBConf when it tries to fire up OpenGL.
Wine, for Direct3D support it tries to fire up (in order) Vulkan then progressively older OpenGL versions fro 4.5 down to 2.1 or maybe even 1.4 (of course the older the OpenGL the lower supported Direct3D version). Wine does not like getting an error back with the same transaction serial number as it sent out.
See https:/
Mesa issue 3969,
The patch there throws in an "XNoOp()" to increment the transaction serial number.
But the patch there caused issues in other apps, per
https:/
Mes issue 4763,
They found XNoOp() increments the serial number, but xcb keeps a "shadow copy" of the serial number which is not incremented, causing problems. XFlush() increments the serial number, keeps xcb in sync and happy, with no real side effects (running XFlush() frequently would slow things down, but this code only runs when a GLX context is being created anyway which just doesn't happen all that frequently.)
Please find attached a patch implementing the updated patch suggested in issue 4763.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libglx-mesa0 21.0.3-
ProcVersionSign
Uname: Linux 5.13.0-22-generic x86_64
ApportVersion: 2.20.11-
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckR
CompositorRunning: None
CurrentDesktop: GNOME-Flashback
Date: Wed Dec 1 18:59:43 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingI
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller])
Subsystem: Dell Picasso [1028:0a12]
InstallationDate: Installed on 2020-05-05 (575 days ago)
InstallationMedia:
MachineType: Dell Inc. Inspiron 3505
ProcEnviron:
TERM=screen.
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2021
dmi.bios.release: 5.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.7
dmi.board.
dmi.board.name: 0RV9WY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3505
dmi.product.sku: 0A12
dmi.product.
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.
version.
version.
version.
version.
version.
version.
Suggested patch.
For now, I've been running mesa 20.0.x on the affected system from (21.0.x is in ubuntu-updates, 20.0.x in base ubuntu repo, so I downgraded to that and thank goodness for apt-mark hold...) But I can update it straight away to test any update that comes out.
Thanks!
--Henry