https://bugs.winehq.org/show_bug.cgi?id=41235
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com, | |austinenglish@gmail.com, | |winetest@luukku.com
--- Comment #3 from winetest@luukku.com --- (In reply to Tobias (:Tobbi) Markus from comment #2)
(In reply to Martin Fuhrer from comment #1)
This appears to be a more general problem in the latest wine releases (I encountered it in 1.9.16). Running any executable that attempts to open a window (e.g. winemine, regedit) fails to do so, generating the "Application tried to create a window, but no driver could be loaded" console error.
Another forum thread about the problem is here: https://forum.winehq.org/viewtopic.php?f=9&t=27305
Martin and others: I just re-installed wine via homebrew (as opposed to Macports, previously) and things have started to work again. I am not sure if this has something to do with one of the releases in the meantime or whether it's a bug with how Macports installs wine.
Can you re-test?
I think this is safe to close now.
The thread mentioned here has 2 last comments as following:
Solution has been found for this problem. It is related to fontconfig 2.12.1. To fix the issue, revert to 2.12.0
I can confirm that after reverting to fontconfig 2.12.0, wine is back to normal and will display windows just fine.
But does wine even support homebrew installs???