https://bugs.winehq.org/show_bug.cgi?id=41240
Bug ID: 41240 Summary: Upon upgrading Wine and associated dependencies to 1.9.17, Wine is no longer able to run programs with a graphical interface Product: Wine Version: 1.9.17 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: andrewsuicune@gmail.com
Created attachment 55533 --> https://bugs.winehq.org/attachment.cgi?id=55533 1.9.17 winecfg log
On August 27, 2016, I upgraded from 1.9.13 to 1.9.17 using MacPorts. Upon upgrade, trying to run programs resulted in the following:
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
Thinking it was a regression, I activated 1.9.13, but 1.9.13 now had the same problem, leading me to believe that it may not necessarily be Wine itself.
I posted in the forums: https://forum.winehq.org/viewtopic.php?f=9&t=27305
Note that 1.9.13 worked as expected before the update.
winecfg suffers from the same fate as all other applications with a graphical interface.
Applications that normally crash with Wine continue to crash and produce appropriate crash logs.
Creating a clean .wine did NOT rectify the problem.
Assuming the other forum posts are referring to the same problem, this issue also exists on some Linux distros.
Attached is a sample when running winecfg on 1.9.17