https://bugs.winehq.org/show_bug.cgi?id=55995
alexandros.frantzis@collabora.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexandros.frantzis@collabo | |ra.com
--- Comment #4 from alexandros.frantzis@collabora.com --- 1. Please attach a log of the problem with "WINEDEBUG=+timestamp,+pid,+tid,+waylanddrv,+keyboard WAYLAND_DEBUG=1"
2. It's very likely that the Blizzard launcher is using Chromium Embedded Framework, which utilizes cross-process rendering, which is not yet supported by the upstream driver.
3. Thanks, I have a fix here: https://gitlab.winehq.org/wine/wine/-/merge_requests/4668 . Let me know how it works for you.
4. Since with the Wayland driver the toplevel windows are normal Wayland xdg-toplevels, Sway does its normal thing and places them tiled (in contrast to X11/Xwayland windows which are treated specially). If you prefer a "float" state, you will need to tell sway use that state (although that may be tricky at the moment since the Wayland driver doesn't yet set app_id or title).
5. Please attach a log of the problem with "WINEDEBUG=+timestamp,+pid,+tid,+waylanddrv,+keyboard,+vulkan WAYLAND_DEBUG=1". Do you see this issue in other compositors?
6. This would indicate that relative motion is not being properly enabled. Please attach a log with "WINEDEBUG=+timestamp,+pid,+tid,+waylanddrv,+keyboard WAYLAND_DEBUG=1".
7. Please attach log as above.
8. Not currently implemented. BTW, are you using a scaled output?