https://bugs.winehq.org/show_bug.cgi?id=49326
--- Comment #14 from Robert Walker bob.mt.wya@gmail.com --- Created attachment 67379 --> https://bugs.winehq.org/attachment.cgi?id=67379 wine-staging-044cb930662d61f401a5d1bdd7b8e75d59cea5ea_wineboot_log
(In reply to Paul Gofman from comment #11)
(In reply to Robert Walker from comment #10)
Could you please attach the full WINEDEBUG=+pid,+virtual,+module,+process log with the latest patch? And also the exact command line how do you run Wine (the way it would fail without the patch)?
The thing is, I could not ever reproduce the problem like described here without some very specific settings, and it was the same for some other people. And while there was definitely a bug (which should be fixed now), maybe I could finally guess the reason why it fails specifically for some people and maybe suggest some workaround with existing version.
Log attached.
My minimal trigger command, for this bug, was simply:
wineboot -u
Which is used to create a (clean) 64-bit WINEPREFIX.
Tested with 64-bit Gentoo, with gcc (Gentoo 10.1.0 p1) 10.1.0
CPU: 16-Core (2-Die) AMD Ryzen 9 3950X (-MT MCP MCM-) speed/min/max: 3155/2200/3500 MHz Kernel: 5.7.0-gentoo-x86_64 x86_64