Well there are two options here, backport the changes from xserver master that fix this instead of using the 114 patch, or dropping the 2 glx 1.4 enablement patches and 114 completely. Just dropping 114 is not an option because it will regress things horribly to the point where closing clutter apps crashes the server.
but the patches need some *serious* review and it is only compile tested at the moment. This only affects people using the glx 1.4 enablement backports to xserver 1.7.x so it's not really upstream material.
The slightly more sane option I see at the moment is to revert the 2 glx 1.4 enablement patches as well as the 114 patch that only mattered for things using that. I have uploaded that combination to x-updates here -
Well there are two options here, backport the changes from xserver master that fix this instead of using the 114 patch, or dropping the 2 glx 1.4 enablement patches and 114 completely. Just dropping 114 is not an option because it will regress things horribly to the point where closing clutter apps crashes the server.
I tried my hand at backporting the 2 commits here (xorg-server - 2:1.7.6-2ubuntu7.5) - /edge.launchpad .net/~sarvatt/ +archive/ bugs/+packages
https:/
but the patches need some *serious* review and it is only compile tested at the moment. This only affects people using the glx 1.4 enablement backports to xserver 1.7.x so it's not really upstream material.
The two patches: sarvatt. com/downloads/ patches/ 119_dri2_ drawables. patch sarvatt. com/downloads/ patches/ 120_glx_ drop_destroywin dow.patch
http://
http://
The slightly more sane option I see at the moment is to revert the 2 glx 1.4 enablement patches as well as the 114 patch that only mattered for things using that. I have uploaded that combination to x-updates here -
https:/ /edge.launchpad .net/~ubuntu- x-swat/ +archive/ x-updates