https://bugs.winehq.org/show_bug.cgi?id=34348
--- Comment #29 from Henri Verbeet hverbeet@gmail.com --- (In reply to Adam Bolte from comment #28)
So that's only a built-in command line application. Instead, maybe we could just complain about it the one time when Wine first needs to use RandR?
Yes, that's unfortunate, but not something we can easily fix. The message is actually only printed once when winex11.drv is loaded, but this happens for each process that loads winex11.drv.
Is there anything Wine needs to do that RandR 1.0 cannot? Searching for RandR on the Wine wiki returns 0 results.
The most significant things RandR 1.3 gets you are RRGetScreenResourcesCurrent to query the current configuration without polling the display connectors, and the ability to set the display mode independently on different displays of a multihead setup. (I.e., changing the display mode of one display without either the other displays going black or the contents getting stretched over all displays.) Note though that even the RandR 1.0 implementation in the proprietary NVIDIA drivers has its own issues.