Bug 1897215 - PicaSim.exe does not start on F33 Wine (regression from F32)
Summary: PicaSim.exe does not start on F33 Wine (regression from F32)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: wine-dxvk
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: František Zatloukal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-12 15:12 UTC by Jan "Yenya" Kasprzak
Modified: 2020-12-08 01:47 UTC (History)
4 users (show)

Fixed In Version: wine-dxvk-1.7.2-3.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-08 01:47:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Wine HQ 45277 0 None None None 2020-11-13 12:54:50 UTC

Description Jan "Yenya" Kasprzak 2020-11-12 15:12:47 UTC
Description of problem:
After upgrading to Fedora 33, an RC plane simulator PicaSim no longer works under Wine, even though it used to work in Fedora 32 on the same computer.

Version-Release number of selected component (if applicable):
wine-5.20-1.fc33.x86_64

How reproducible:
100 %

Steps to Reproduce:
1. Download PicaSim for Windows from http://rowlhouse.co.uk/PicaSim/download.html
2. Install it and launch it from the last page of the installer.

Actual results:
The PicaSim window gets created, but it is stuck in the splash screen, and never goes any further.

Expected results:
The simulator should start up as it did in F32.

Additional info:
I tried to manually dowgrade to wine-5.20-1.fc32.x86_64, but it did not fix the problem. I also tried to disable SElinux. So the problem might be somewhere deeper than the Wine itself.

When started as

$ cd .wine/drive_c/Program\ Files\ \(x86\)/PicaSim
$ wine ./PicaSim.exe

the stderr ends with this:

[...]
info:  DXVK: Read 0 valid state cache entries
info:  DXVK: Using 10 compiler threads
info:  D3D9DeviceEx: Using extended constant set for software vertex processing.
info:  D3D9DeviceEx::ResetSwapChain:
info:    Requested Presentation Parameters
info:      - Width:              1
info:      - Height:             1
info:      - Format:             D3D9Format::X8R8G8B8
info:      - Auto Depth Stencil: false
info:                  ^ Format: D3D9Format::Unknown
info:      - Windowed:           true
warn:  winevulkan detected, disabling exclusive fullscreen support
0024:fixme:vulkan:X11DRV_vkCreateWin32SurfaceKHR Application requires child window rendering, which is not implemented yet!
err:   Failed to create surface
0024:err:dbghelp:pe_load_dbg_file Couldn't find .DBG file "oleaut32.dbg" (L"C:\\Program Files (x86)\\PicaSim")
Memory exception (11) attempting to access: 7E926140 [ip=F7C6AAA6]
0110:err:ntdll:RtlpWaitForCriticalSection section 7BC69360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0110, blocked by 0024, retrying (60 sec)
00f8:err:ntdll:RtlpWaitForCriticalSection section 7BC69360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 00f8, blocked by 0024, retrying (60 sec)
0110:err:ntdll:RtlpWaitForCriticalSection section 7BC69360 "dlls/ntdll/loader.c: loader_section" wait timed out in thread 0110, blocked by 0024, retrying (60 sec)

(and the last line repeats every 60 seconds)

Comment 1 Michael Cronenworth 2020-11-12 15:20:40 UTC
Important note for the future: Read up on Fedora Changes :)

https://fedoraproject.org/wiki/Changes/DXVKwined3d

Try removing the 'wine-dxvk' package or use alternates to promote the native wine d3d DLLs.

Comment 2 Jan "Yenya" Kasprzak 2020-11-12 15:31:09 UTC
Thanks, removing wine-dxvk and wine-dxvk-d3d9 i686 and x86_64 did help. Also, sorry for missing this in the release notes.

That said, the document you linked states the following:

---
There is a slight possibility of user experience degradation compared to wined3d on old Intel iGPUs supporting just a subset of Vulkan specification (Ivy Bridge and Haswell generations). I haven't had any opportunity to test DXVK on such hardware, however, if issues are discovered, check for Vulkan from wine-dxvk package PR ( https://src.fedoraproject.org/rpms/wine-dxvk/pull-request/4#_1__26 ) could be improved to block certain GPU vendors/generations/models.

AMD and/or nVidia GPUs should not be affected, they either do not support Vulkan at all, or they support it fully. 
---

My GPU is AMD, which "should not be affected":

1d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] (rev c7)

Comment 3 Michael Cronenworth 2020-11-12 20:47:41 UTC
I'm glad that helped. The wine and DXVK world are not perfect. They are after all trying to replicate closed-source functionality. Expecting perfection will leave you very disappointed.

I'll reassign this to wine-dxvk, but I also encourage you to open an issue with upstream.

https://github.com/doitsujin/dxvk/issues

Comment 4 František Zatloukal 2020-11-13 12:54:52 UTC
Mhm, it's a problem in wine triggered by dxvk: https://bugs.winehq.org/show_bug.cgi?id=45277 . I guess there is no need to report it to upstream dxvk.

Thanks for re-assigning to me Michael, I'll leave it open until it's fixed wine-side.

Comment 5 Fedora Update System 2020-11-29 19:59:41 UTC
FEDORA-2020-e939f7b8be has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-e939f7b8be

Comment 6 Fedora Update System 2020-11-30 01:48:31 UTC
FEDORA-2020-e939f7b8be has been pushed to the Fedora 33 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-e939f7b8be`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-e939f7b8be

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2020-12-08 01:47:19 UTC
FEDORA-2020-e939f7b8be has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.