Bug 1946118

full terminal output:
002c:fixme:winediag:LdrInitializeThunk wine-staging 6.3 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
002c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0034:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0050:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0064:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
006c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0024:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0024:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0104:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
0024:err:module:LdrInitializeThunk "comctl32.dll" failed to initialize, aborting
0024:err:module:LdrInitializeThunk Initializing dlls for L"C:\\windows\\system32\\winecfg.exe" failed, status c0000005

Could you please file a bug upstream and link to it here?

https://bugs.winehq.org/enter_bug.cgi?product=Wine-staging

I'm also now getting this after my last update, which included kernel 5.12.8-300.fc34.x86_64

Wine version wine-6.9 (Staging)

Confirmed that (for me anyway), this behaviour is related to the WINE virtual desktop. Turning that off allows applications to launch normally. 

Workaround:

Unfortunately, if you have the vd enabled by default, this bug prevents you from using any of the normal means to turn it off (winecfg, winetricks, regedit) because these also fail to start! 

Instead, look for a "[Software\\Wine\\Explorer]" key in the user.reg file in the WINE prefix you're using, and comment out the line

"Desktop"="Default"

(ie, change it to 

# "Desktop"="Default"

)

Applications now launch as normal except, of course, sans the vd.

Problem still exists in wine-6.10-1.fc34.x86_64

Still broken in wine-6.11-1.fc34.x86_64

Upstream bug says this is actually a bug in Mesa, and that "Upgrading mesa-vulkan-drivers from 20.3.4-1 to 20.3.5-1 ... fixes it."

But we're already newer than that: mesa-vulkan-drivers-21.1.3-1.fc34.x86_64

Still broken in wine-6.12-1.fc34.x86_64 -- I've opened Bug 1983839 against Mesa, based on upstream's finding

This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle.
Changing version to 35.

I've got this exact same problem. But I don't think it is a mesa problem since I've got a Nvidia GPU and I use the proprietary drivers.
I'm still under Fedora 34.
```
$ uname -a
Linux fixe 5.17.9-100.fc34.x86_64 #1 SMP PREEMPT Wed May 18 15:28:19 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

$ wine --version
wine-7.2 (Staging)

$ rpm -qa | grep nvidia
xorg-x11-drv-nvidia-cuda-libs-510.60.02-1.fc34.x86_64
xorg-x11-drv-nvidia-kmodsrc-510.60.02-1.fc34.x86_64
nvidia-persistenced-510.60.02-1.fc34.x86_64
xorg-x11-drv-nvidia-libs-510.60.02-1.fc34.i686
xorg-x11-drv-nvidia-libs-510.60.02-1.fc34.x86_64
nvidia-settings-510.60.02-1.fc34.x86_64
xorg-x11-drv-nvidia-power-510.60.02-1.fc34.x86_64
xorg-x11-drv-nvidia-510.60.02-1.fc34.x86_64
akmod-nvidia-510.60.02-1.fc34.x86_64
xorg-x11-drv-nvidia-cuda-libs-510.60.02-1.fc34.i686
xorg-x11-drv-nvidia-cuda-510.60.02-1.fc34.x86_64
kmod-nvidia-5.17.6-100.fc34.x86_64-510.60.02-1.fc34.x86_64
kmod-nvidia-5.17.8-100.fc34.x86_64-510.60.02-1.fc34.x86_64
kmod-nvidia-5.17.9-100.fc34.x86_64-510.60.02-1.fc34.x86_64
```

Fedora 34 has reached end of life and is no longer supported. Upgrade to Fedora 35 or 36 where Wine 7.9 is available.

This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.