After having updated mesa and wine, I'm now having issues when trying to launch the wine configuration or one of my wine applications. However it will run when downgrading to wine-8.4-1.fc38 from wine-8.11-1.fc38. Not sure if related to rhbz#2219130 or not, but I've got an AMD Radeon RX 580 and not dependent on Radeon 3000 (r600 driver). gnome-shell-44.2-1.fc38 kernel-6.3.11-200.fc38 mesa-23.1.3-1.fc38 mutter-44.2-2.fc38 wine-8.11-1.fc38 How reproducible: always! 002c:fixme:winediag:LdrInitializeThunk wine-staging 8.11 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0090:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 Programmet kunde inte startas, eller så var inget program associerat med den angivna filen.* 'ShellExecuteEx' misslyckades: Filen hittades inte.** * application was unable to run, or no application associated with the file ** 'ShellExecuteEx' failed: file could not be found
KDE Plasma, RX550 (AMD) video card, and I have a similar issue. For me it is easiest to trigger using the "Emulate a virtual desktop" option. If you run 'winecfg' without it selected, wine config loads without issue; select "Emulate a virtual desktop", set a size, close wine config and then run 'winecfg' again- fails to load with the following err message: > 015c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded. If I downgrade to wine-8.4-1.fc38.x86_64, this error does not show up, and winecfg loads without issue with "Emulate a virtual desktop" enabled. As an aside in my case, wine applications which do not require a virtual desktop work fine on wine-8.11-1.fc38, while on wine-8.4-1.fc38.x86_64 they work fine regardless of virtual desktop or not. I am unsure as to whether I should file this under its own bug report, whether this is a mesa or wine issue, etc- please do advise if anyone thinks I should file a new report.
The bug with err:winediag:nodrv_CreateWindow seems to have been introduced in wine-staging (which Fedora packages) version 8.10. Going back to wine-8.6-1.fc38 (the latest non-broken version packaged for F38) indeed solves it. Upstream bug for this: https://bugs.winehq.org/show_bug.cgi?id=55085
Tried patch listed there. And it works. https://copr.fedorainfracloud.org/coprs/moceap/wine-vd-fix/