https://bugs.winehq.org/show_bug.cgi?id=52500
--- Comment #40 from Bernhard Übelacker bernhardu@mailbox.org --- Created attachment 75889 --> https://bugs.winehq.org/attachment.cgi?id=75889 DEBUG-make-winex11.drv-DllMain-visible.patch
(In reply to O. Nykyforchyn from comment #38)
Created attachment 75888 [details] xz'ed log of a failed attempt to run winecfg
0048:trace:module:build_module loaded L"\??\C:\windows\system32\explorer.exe" 00007FFFFE223620 0000000140000000 0048:Call KERNEL32.LoadLibraryW(7ffffe1ff290 L"winex11.drv") ret=14000220f 0048:warn:module:process_attach Initialization of L"winex11.drv" failed 0048:Ret KERNEL32.LoadLibraryW() retval=00000000 ret=14000220f
I guess this failing LoadLibraryW is the first visible sign of the issue.
Unfortunately by default winex11.drv is excluded from +relay. If you want to see calls done by winex11.drv you could remove it from the exclusion list (I assume command line is working?):
$ wine reg query 'HKCU\Software\Wine\Debug' /v RelayFromExclude HKEY_CURRENT_USER\Software\Wine\Debug RelayFromExclude REG_SZ winex11.drv;winemac.drv;user32;gdi32;advapi32;kernel32
$ wine reg add 'HKCU\Software\Wine\Debug' /v RelayFromExclude /t REG_SZ /d "winemac.drv;user32;gdi32;advapi32;kernel32"
$ wineserver -k
Afterwards a +relay should include calls done from winex11.drv.
If you want to add some debug logging I guess in dlls/winex11.drv/dllmain.c the function DllMain might be therefore the starting point.
Unfortunately output of explorer.exe at this stage is kind of hidden. Attached patch should make it better visible, if you want to give it a try?