http://bugs.winehq.org/show_bug.cgi?id=23235
Kenneth Robinette support@securenetterm.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |support@securenetterm.com
--- Comment #7 from Kenneth Robinette support@securenetterm.com 2011-01-30 09:53:47 CST --- (In reply to comment #6)
(In reply to comment #5)
Then, wine should not query for it over and over - it will not appear after it was missing the first time :)
It's ridiculous to print loud warnings in the first place when someone just queries for a feature.
Ah, the dictators at WINE speaks again. A user reports a problem, and they are ignored. Case closed, not a WINE problem. Really? Why not look at the problem report and help resolve it.
I see the same thing, and if you take a few nanoseconds and do a web search, you will find that this has been around for years.
The only way you can get rid of the thousands of messages flooding the network regarding the MIT_XSHM not supported message is to configure WINE with:
configure --without-xshm
Who cares whether is ridiculous for X-11 to keep printing the message. The point is, it does. Every program/system involved in this reports back to WINE that the option MIT-XSHM is NOT SUPPORTED, yet the messages continue to flow.