Windows no longer display (1.9.13 -> 1.9.17)

[Sparen]

Today I upgraded from 1.9.13 to 1.9.17 via MacPorts. Once I did so, I was no longer able to use Wine - no windows could load. I was getting the following repeated a few times.

Code: Select all

err:winediag:nulldrv_CreateWindow Application tried to create a window, but no driver could be loaded.
err:winediag:nulldrv_CreateWindow The explorer process failed to start.
err:ole:apartment_createwindowifneeded CreateWindow failed with error 0
err:ole:apartment_createwindowifneeded CreateWindow failed with error 0
err:ole:apartment_createwindowifneeded CreateWindow failed with error 0

I have no idea what caused this to break. Fearing it was a regression, I reverted back to 1.9.13, but the same problem was present. Therefore, it is most likely not an issue with Wine - I tried a new .wine directory with 1.9.13 and still had the issue.

If anyone else has this problem or can cast light onto the situation (as well as potential solutions or enlightening me as to the cause), that would be greatly appreciated. Thank you very much.

EDIT:
Trying to run

Code: Select all

winecfg

via the Terminal also brings up the error. MacOSX El Capitan

[claunia]

I have experienced same regression updating from 1.9.16 to 1.9.17 on Arch Linux.
1.9.17-staging shows winecfg window.

[mfuhrer]

I am encountering this problem after a fresh install of wine-devel 1.9.16 via MacPorts on El Capitan last week (the last time I had a MacPorts wine installation was over a year ago on Yosemite). Upgraded to 1.9.17 yesterday and the same problem continues - whether I try to launch a binary distributed with wine (e.g. winemine, regedit) or a third party Windows app.

Initially I thought the problem was related to SIP/rootless, but disabling SIP had no effect. Interesting to see the problem is present on the linux side as well (as per the previous post)...

[Sparen]

The problem seems to be with the upgrade itself and not with the version of Wine, though I guess it's a 1.9.17 thing? Since going back to 1.9.13 still retained the issue.

My thoughts:
-One of the dependencies updated and broke Wine as a side effect
-The update changed something that is not reverted when going back to and activating 1.9.13 instead

[Arietis]

I have same issues.
viewtopic.php?f=9&t=27227
Anyone was able to make it work?

[Sparen]

Added as a bug

https://bugs.winehq.org/show_bug.cgi?id=41240

[Sparen]

Solution has been found for this problem. It is related to fontconfig 2.12.1. To fix the issue, revert to 2.12.0

[mfuhrer]

I can confirm that after reverting to fontconfig 2.12.0, wine is back to normal and will display windows just fine.