Replies: 2 comments
same problem with my amd rdna2, i have to use Wine EW-10.10 EW-11.0 works too |
0 replies
|
Same here on my AMD Ryzen AI 7 PRO 350, Zorin 18.1. Tried the AMD and normal build of 11.12, but both hung. EW-10.10 works so that's what I'm currently using. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Installed via AffinityOnLinux. After updating Wine 11.0 → 11.12, Affinity's UI loads but opening a document hangs — canvas never renders, no crash. 11.0 works perfectly; 11.12 and 11.12v4 both hang.
System: Intel Arc A750 (Mesa 26.1.4, Vulkan 1.4) · Ryzen 9 3950X · Manjaro, kernel 7.1.3 · Wayland/Xwayland · Affinity 3.2.3.4646 · ElementalWarrior wine-11.12.
winedbg backtrace — hung thread is Affinity's renderer stuck in a Win32 wait that never returns:
ntdll (wait) ← kernelbase!WaitForMultipleObjects ← libkernel ← libraster ← librenderer
No vkd3d/dxgi/vulkan/d3d frames anywhere — it's a lost wakeup on a Win32 event, not a GPU call.
Ruled out (all still hang on 11.12): vkd3d/Vulkan/GPU driver · OpenCL disabled · all sync backends (fsync, server-side, ntsync w/ /dev/ntsync) · both display drivers (X11 + Wayland) · 11.12v4.
Key clue: forcing software Vulkan (lavapipe), so the Arc is bypassed, makes it intermittent — renders on some launches, hangs on others. On the real Arc driver it hangs almost every time. Looks like a timing-dependent lost-wakeup introduced in 11.12, where the fast hardware path loses the race and the slow software path sometimes wins.
Q: Anyone on Arc/Mesa ANV seeing 11.12 hang where 11.0 works? Known Wine 11.x change (event signaling / scheduler) that could cause this? Full logs + winedbg dump available.
All reactions