https://bugs.winehq.org/show_bug.cgi?id=55995
Bug ID: 55995 Summary: Wine 9.0-rc1 Wayland cursor does not move on some surfaces Product: Wine Version: 9.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: h0tc0d3@gmail.com Distribution: ---
Version: Wine 9.0-rc1 Wayland
Bugs:
1) In games, the cursor moves only in the game menu, but as soon as you load some map, the cursor stops moving. At the same time, if you open the menu, the cursor continues to move in the menu. Game Example: Overwatch 2
``` "${WINE}/bin/wine64" "C:/Program Files (x86)/Overwatch/_retail_/Overwatch.exe" ```
2) The Blizzard Battle.net launcher launches, but there is no window on the screen. Therefore, the Overwatch 2 game can only be launched using the above method, and each time needs enter your username and password.
``` "${WINE}/bin/wine64" "C:/Program Files (x86)/Battle.net/Battle.net.exe" --exec="launch Pro" > /dev/null 2>&1 ```
3) In winecfg if press "Apply" or "OK" button, then winecfg freezes.
4) winecfg does not transmit float state, it runs on the entire screen.
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #1 from Grigory Vasilyev h0tc0d3@gmail.com --- 5) FPS in games locked in 54-55Hz(Wayland) instead 240Hz(xwayland) The problem seems to be caused by swap buffers.
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #2 from Grigory Vasilyev h0tc0d3@gmail.com --- 6) The cursor, if working in games, periodically starts looking at the ceiling or floor. Losing position?
7) In Sway, Overwatch 2 launches in full screen, but only half of the screen is drawn in the center, the rest is black. Image artifacts. It's work fine in Hyprland.
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #3 from Grigory Vasilyev h0tc0d3@gmail.com --- 8) I would like to have raw input. Xwayland somehow knows how to do this, and transmits the cursor offset without using system sensitivity.
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?
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #5 from Grigory Vasilyev h0tc0d3@gmail.com ---
- 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?
Yes, I will provide the log a little later, but the problem, as it turns out, also occurs in X11 xwayland. And it doesn’t matter whether adaptive_sync is on or off.
- Not currently implemented. BTW, are you using a scaled output?
Yes, I use fractional scaling = 1.25
I found how to fix this. You just need to replace dx and dy with dx_unaccel and dy_unaccel respectively. You probably need to add an env check during initialization, for example WINE_WAYLAND_RAW_INPUT and, depending on its value, read normal or unaccel values. https://gitlab.winehq.org/wine/wine/-/blame/master/dlls/winewayland.drv/wayl...
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #6 from Grigory Vasilyev h0tc0d3@gmail.com --- Created attachment 75629 --> https://bugs.winehq.org/attachment.cgi?id=75629 Logs
Wine trace logs
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #7 from Grigory Vasilyev h0tc0d3@gmail.com --- (In reply to alexandros.frantzis from comment #4)
- Please attach a log of the problem with
"WINEDEBUG=+timestamp,+pid,+tid,+waylanddrv,+keyboard WAYLAND_DEBUG=1"
See wine1.log It's Hyprland fractional scale = 1.25
- 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.
Yep, Battle.net use CEF.
- Thanks, I have a fix here:
https://gitlab.winehq.org/wine/wine/-/merge_requests/4668 . Let me know how it works for you.
Thx. Solved.
- 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).
Yep. But we have other bug, drop-down menus are also drawn full screen. Example: changing the windows version in winecfg. https://imgur.com/a/fzMVMtf
- 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?
In all compositors. Sway and Hyprland have frame limit in ~55 frames.
See wine1.log It's Hyprland fractional scale = 1.25
- 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".
See wine1.log It's Hyprland fractional scale = 1.25
- Please attach log as above.
See wine2.log It's sway fractional scale = 1.00
- Not currently implemented. BTW, are you using a scaled output?
See comment above.
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #8 from alexandros.frantzis@collabora.com --- (In reply to Grigory Vasilyev from comment #7)
(In reply to alexandros.frantzis from comment #4)
- Please attach a log of the problem with
"WINEDEBUG=+timestamp,+pid,+tid,+waylanddrv,+keyboard WAYLAND_DEBUG=1"
See wine1.log It's Hyprland fractional scale = 1.25
<snip>
- 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".
See wine1.log It's Hyprland fractional scale = 1.25
Thanks for the logs.
For the two items above, could you please check if setting the DPI in winecfg (tab "Graphics") to 120 (= 96 * 1.25) makes any difference, and also provide the logs with that DPI set if possible? Thanks!
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #9 from alexandros.frantzis@collabora.com --- (In reply to alexandros.frantzis from comment #8)
(In reply to Grigory Vasilyev from comment #7)
(In reply to alexandros.frantzis from comment #4)
- Please attach a log of the problem with
"WINEDEBUG=+timestamp,+pid,+tid,+waylanddrv,+keyboard WAYLAND_DEBUG=1"
See wine1.log It's Hyprland fractional scale = 1.25
<snip> > > > 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". > > See wine1.log > It's Hyprland fractional scale = 1.25 >
Thanks for the logs.
For the two items above, could you please check if setting the DPI in winecfg (tab "Graphics") to 120 (= 96 * 1.25) makes any difference, and also provide the logs with that DPI set if possible? Thanks!
Also please add "+win" to the WINEDEBUG comma-separated string.
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #10 from Grigory Vasilyev h0tc0d3@gmail.com ---
For the two items above, could you please check if setting the DPI in winecfg (tab "Graphics") to 120 (= 96 * 1.25) makes any difference, and also provide the logs with that DPI set if possible? Thanks!
All logs above with DPI = 120.
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #11 from alexandros.frantzis@collabora.com --- (In reply to Grigory Vasilyev from comment #10)
For the two items above, could you please check if setting the DPI in winecfg (tab "Graphics") to 120 (= 96 * 1.25) makes any difference, and also provide the logs with that DPI set if possible? Thanks!
All logs above with DPI = 120.
Ah, thanks. Then could you please try with DPI=96 and hyprland scale 1.0 and see if that helps.
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #12 from Grigory Vasilyev h0tc0d3@gmail.com --- Created attachment 75631 --> https://bugs.winehq.org/attachment.cgi?id=75631 Wine log +win
Wine log +win.
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #13 from Grigory Vasilyev h0tc0d3@gmail.com --- I made a video of the mouse not adjusting properly and being very difficult to stabilize.
https://drive.google.com/file/d/1p4mESWgC5-r9Tq_kXPEKocI5BVAhBdGr/view?usp=s...
Also, bug number 1 only occurs with staging patches. All logs above are from vanilla wine. Therefore, bug number 6 is relevant.
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #14 from Grigory Vasilyev h0tc0d3@gmail.com --- (In reply to alexandros.frantzis from comment #11)
(In reply to Grigory Vasilyev from comment #10)
For the two items above, could you please check if setting the DPI in winecfg (tab "Graphics") to 120 (= 96 * 1.25) makes any difference, and also provide the logs with that DPI set if possible? Thanks!
All logs above with DPI = 120.
Ah, thanks. Then could you please try with DPI=96 and hyprland scale 1.0 and see if that helps.
Solved some of the problems. The cursor has become more controllable, but still looks at the ceiling and floor, and after moving the cursor continues to move for some time and does not stop. With DPI=96 and fractional scale = 1.25 the positions of interactive elements are shifted, for example, buttons are not pressed, input fields are not activated when you click on them.
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #15 from Grigory Vasilyev h0tc0d3@gmail.com --- Created attachment 75633 --> https://bugs.winehq.org/attachment.cgi?id=75633 DPI = 96 Fractional Scale = 1.00
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #16 from Grigory Vasilyev h0tc0d3@gmail.com ---
Solved some of the problems. The cursor has become more controllable
I lied here, it turned out to be the same behavior.
https://bugs.winehq.org/show_bug.cgi?id=55995
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Fixed by SHA1| |a71ec54df817ee721fd1026832d | |968ce234ced9d
--- Comment #17 from Fabian Maurer dark.shadow4@web.de --- Should be fixed by https://gitlab.winehq.org/wine/wine/-/commit/a71ec54df817ee721fd1026832d968c...
https://bugs.winehq.org/show_bug.cgi?id=55995
Grigory Vasilyev h0tc0d3@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|FIXED |---
--- Comment #18 from Grigory Vasilyev h0tc0d3@gmail.com --- (In reply to Fabian Maurer from comment #17)
Should be fixed by https://gitlab.winehq.org/wine/wine/-/commit/ a71ec54df817ee721fd1026832d968ce234ced9d
This solved only one of many problems.
https://bugs.winehq.org/show_bug.cgi?id=55995
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #19 from Austin English austinenglish@gmail.com --- (In reply to Grigory Vasilyev from comment #18)
(In reply to Fabian Maurer from comment #17)
Should be fixed by https://gitlab.winehq.org/wine/wine/-/commit/ a71ec54df817ee721fd1026832d968ce234ced9d
This solved only one of many problems.
Please open new issues for each _individual_ problem.
https://bugs.winehq.org/show_bug.cgi?id=55995
Grigory Vasilyev h0tc0d3@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |UNCONFIRMED
--- Comment #20 from Grigory Vasilyev h0tc0d3@gmail.com --- (In reply to Austin English from comment #19)
(In reply to Grigory Vasilyev from comment #18)
(In reply to Fabian Maurer from comment #17)
Should be fixed by https://gitlab.winehq.org/wine/wine/-/commit/ a71ec54df817ee721fd1026832d968ce234ced9d
This solved only one of many problems.
Please open new issues for each _individual_ problem.
Are you drunk there? The main problem is not solved! Read the title! Only point 3 has been solved!
- In winecfg if press "Apply" or "OK" button, then winecfg freezes.
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #21 from alexandros.frantzis@collabora.com ---
- The cursor, if working in games, periodically starts looking at the ceiling or floor. Losing position?
Please let me know if https://gitlab.winehq.org/wine/wine/-/merge_requests/4680 helps with (6), thanks!
Also, bug number 1 only occurs with staging patches
BTW, I do think that having individual issues would make tracking easier (i.e., each commit could point to more specific bug report). Especially since the "main"/title bug happens with staging only, so I would say it's not in scope for fixing at this point.
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #22 from Grigory Vasilyev h0tc0d3@gmail.com --- (In reply to alexandros.frantzis from comment #21)
- The cursor, if working in games, periodically starts looking at the ceiling or floor. Losing position?
Please let me know if https://gitlab.winehq.org/wine/wine/-/merge_requests/4680 helps with (6), thanks!
Helped with 6. Thx. But I'm worried about the low FPS in wine 9. I added fsync patches and it raised the FPS from 55 to 70, but the problem still remained. What ideas might there be?
Also, bug number 1 only occurs with staging patches
BTW, I do think that having individual issues would make tracking easier (i.e., each commit could point to more specific bug report). Especially since the "main"/title bug happens with staging only, so I would say it's not in scope for fixing at this point.
Yes, I will create separate bug reports.
https://bugs.winehq.org/show_bug.cgi?id=55995
Vijay Kamuju infyquest@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED CC| |infyquest@gmail.com Status|UNCONFIRMED |RESOLVED
--- Comment #23 from Vijay Kamuju infyquest@gmail.com --- Fixed by commit : a71ec54df817ee721fd1026832d968ce234ced9d
https://bugs.winehq.org/show_bug.cgi?id=55995
Grigory Vasilyev h0tc0d3@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |UNCONFIRMED
--- Comment #24 from Grigory Vasilyev h0tc0d3@gmail.com --- (In reply to Vijay Kamuju from comment #23)
Fixed by commit : a71ec54df817ee721fd1026832d968ce234ced9d
Stop drinking at work already! This is a completely different bug that I have never reported and has nothing to do with my bug reports!
https://bugs.winehq.org/show_bug.cgi?id=55995
Grigory Vasilyev h0tc0d3@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #25 from Grigory Vasilyev h0tc0d3@gmail.com --- Separate bug reports:
1) and 6) https://bugs.winehq.org/show_bug.cgi?id=56022 5) FPS Drop https://bugs.winehq.org/show_bug.cgi?id=56012 7) In sway bug https://bugs.winehq.org/show_bug.cgi?id=56021
DPI bug: https://bugs.winehq.org/show_bug.cgi?id=56023
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #26 from alexandros.frantzis@collabora.com --- Thanks for the separate bugs.
Concerning the confusion about the status of this bug: commit a71ec54df817ee721fd1026832d968ce234ced9d actually fixes point (3) from this report and has the related Wine-Bug tag in the commit (we can't have sub-bug granularity, hence it's better to have separate bugs).
Since we can't change the commit, perhaps a reasonable way forward would be to change this bug to indeed be about (3), so we (+commit message) can all agree it's resolved, and create a new bug for (1). If you decide to do so, please mark the new bug with wine-staging as the "Product", since it only happens there (IIUC).
https://bugs.winehq.org/show_bug.cgi?id=55995
--- Comment #27 from Vijay Kamuju infyquest@gmail.com --- Its always recommended not to group all issues in one bug report. Its good that you have opened multiple bugs. If there are any missing issues please raise new bugs. Thanks for testing the wayland driver.
https://bugs.winehq.org/show_bug.cgi?id=55995
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #28 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 9.0-rc2.