http://bugs.winehq.org/show_bug.cgi?id=30184
James Eder jimportal@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jimportal@gmail.com
--- Comment #8 from James Eder jimportal@gmail.com 2012-07-05 13:15:17 CDT --- (In reply to comment #7)
Is something blocking this patch from getting into wine, or can we hope for a fix soon?
I think the big question is whether xrandr 1.3 supported well enough for this kind of change or should there be some kind of fallback mechanism to use the older protocol?
I suspect (wild guessing really) most systems have a recent enough version of the xrandr library and Wine will be able to load the library fine. However, some drivers (NVIDIA BLOB) only recently started advertising support for >= 1.3 in their release notes. So I guess my question boils down to is if 1.3 xrandr libraries gracefully handle the case where they're matched up with older, less capable, drivers.
We could just do it, call it an upstream problem, and be done with it but it would be nice to cover all the bases if we can. Please forgive my ignorance if this really is a non issue.
I suspect at a minimum there should be a configure check for >= 1.3 headers.