[Bug 51081] New: wine fails to run any program with emulate a virtual desktop is enabled, showing: "comctl32.dll" failed to initialize, aborting
https://bugs.winehq.org/show_bug.cgi?id=51081 Bug ID: 51081 Summary: wine fails to run any program with emulate a virtual desktop is enabled, showing: "comctl32.dll" failed to initialize, aborting Product: Wine Version: 6.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dauerhaft(a)gustr.com Distribution: --- using winehq-devel 6.7 on Debian bullseye. Enabling the emulate a virtual desktop checkbox with winecfg results in every program executed after to fail to start with "00d0:err:module:LdrInitializeThunk "comctl32.dll" failed to initialize, aborting". Wine is working just fine when the virtual desktop is not enabled (, but some programs do not run without virtual desktop emulation.) This happens with any "wine myprogram.exe", and with programs included in wine such as "winecfg". full log reproduced below: ~> winecfg 0060:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete 00d8:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete 0034:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete 00d0:err:winediag:is_broken_driver Broken NVIDIA RandR detected, falling back to RandR 1.0. Please consider using the Nouveau driver instead. MESA-INTEL: warning: Ivy Bridge Vulkan support is incomplete 00d0:err:module:LdrInitializeThunk "comctl32.dll" failed to initialize, aborting 00d0:err:module:LdrInitializeThunk Initializing dlls for L"C:\\windows\\syswow64\\winecfg.exe" failed, status c0000005 I would gladly do more tests or provide more insightful logs if instructed to do so. Thanks! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 dauerhaft(a)gustr.com changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Debian -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 dauerhaft(a)gustr.com changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|wine fails to run any |wine fails to run any |program with emulate a |program with "emulate a |virtual desktop is enabled, |virtual desktop" enabled, |showing: "comctl32.dll" |showing: "comctl32.dll" |failed to initialize, |failed to initialize, |aborting |aborting -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zzhang(a)codeweavers.com --- Comment #1 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Please upload a "WINEDEBUG=+xrandr,+x11drv,+winediag,+x11settings wine winecfg" log -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 --- Comment #2 from dauerhaft(a)gustr.com --- Created attachment 69952 --> https://bugs.winehq.org/attachment.cgi?id=69952 WINEDEBUG=+xrandr,+x11drv,+winediag,+x11settings wine winecfg WINEDEBUG=+xrandr,+x11drv,+winediag,+x11settings wine winecfg log attached -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 --- Comment #3 from dauerhaft(a)gustr.com --- as this is still UNCONFIRMED: Is there any other information needed? I just tested this again and it ("comctl32.dll" failed to initialize, aborting) still happens as of 6.9 . Same results with wine staging 6.9 and with wine stable 6.0 . (For completeness' sake, I also tested this with open source intel graphics instead of proprietary nvidia graphics. same results) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 kolAflash <kolAflash(a)kolahilft.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kolAflash(a)kolahilft.de --- Comment #4 from kolAflash <kolAflash(a)kolahilft.de> --- I'm having the same problem on Bullseye! (Debian 11 Testing/Beta) I think the problem didn't appear with Wine-6.0 a few weeks before. So maybe not Wine itself, but a library recently updated by Debian may caused this. Please let me know if I can somehow help fixing this. Problem is existing on both my Bullseye systems: desktop computer CPU: Ryzen 7 5800X GPU: Radeon RX 590 notebook Model: HP EliteBook 735 G6 CPU & GPU: Ryzen 5 3500U with Vega 8 Problem also exists if I create a new Wine prefix and enable the virtual desktop either via winecfg or by using "/desktop=shell,1920x1080": env WINEPREFIX="${HOME}"/my_prefix wine explorer.exe /desktop=shell,1920x1080 winefile -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 --- Comment #5 from kolAflash <kolAflash(a)kolahilft.de> --- Reproduced with Bullseye (Debian-Testing) builds from: https://wiki.winehq.org/Debian Tested: - wine-stable-6.0.1 - wine-devel-6.10 - wine-staging-6.10 wine-stable-5.11 is the first broken version! Previous wine-stable-5.10 is fine. Wine-5.0.3 from the Debian-Bullseye sources is completely fine to. And interestingly the bug only seems to happen when calling bin/wine. But bin/wine64 seems to be not affected. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 --- Comment #6 from kolAflash <kolAflash(a)kolahilft.de> --- Identified the first bad commit. https://source.winehq.org/git/wine.git/commitdiff/145cfce1135a7e59cc4c89cd05... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #7 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Confirmed with wine 6.10. Working on this. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NOTOURBUG --- Comment #8 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- This is caused by bugs in Mesa. Upgrading mesa-vulkan-drivers from 20.3.4-1 to 20.3.5-1 in sid fixes it. The related commits are https://gitlab.freedesktop.org/mesa/mesa/-/commit/14033ab6dc97e84227377d1713... and https://gitlab.freedesktop.org/mesa/mesa/-/commit/9a467b33bfb03683ce2f8256cb... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 --- Comment #9 from kolAflash <kolAflash(a)kolahilft.de> --- (In reply to Zhiyi Zhang from comment #8)
This is caused by bugs in Mesa. Upgrading mesa-vulkan-drivers from 20.3.4-1 to 20.3.5-1 in sid fixes it. [...]
Thank you very much! Looks like there's already a similar bug related to Wine and asking for Mesa-20.3.5-1 in Bullseye. (Bullseye = currently Debian-11 Testing and may become Stable in June 2021) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983390#17 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 googlemail(a)email-postfach.info changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |googlemail(a)email-postfach.i | |nfo -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 zelea2 <ez(a)vajn.icu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ez(a)vajn.icu --- Comment #10 from zelea2 <ez(a)vajn.icu> --- Created attachment 75154 --> https://bugs.winehq.org/attachment.cgi?id=75154 trace of the winecfg crash -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51081 --- Comment #11 from zelea2 <ez(a)vajn.icu> --- This bug is still present in wine v8.0.2 winecfg (and any .exe program) crashes once the emulate virtual desktop is set wine starts to work again only after removing the \\Wine\\Explorer\\Desktops key from user.reg -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla