Sway: clicks not registering in wine

[alexarice]

• Sway Version: sway version 1.2 (from master)

• Issue: Programs run under wine or by wine seem to not register click events, a cursor can be seen in the window (even a decorated cursor) but clicking on menu items has no effect. Things I have seen this under:

  • winecfg
  • neverwinter nights 2 from GOG store
  • witcher from steam running through steam play

• Debug log and config https://gist.github.com/alexarice/194347760d4adec2f0d8234e337a14cf

• To reproduce:

  • run winecfg
  • notice nothing is clickable in the popup floating window

A note that I can currently work around this for the first 2 by enabling desktop emulation in winecfg. Also both the first 2 work correctly on weston.

[emersion]

Your bug report is missing your config file and debug log. Please add a link to those.

[alexarice]

Your bug report is missing your config file and debug log. Please add a link to those.

Have updated the issue description, sorry about that

[ammgws]

@alexarice Did you get anywhere with this? I think I might be experiencing the same issue.

[alexarice]

I didn't get anywhere

[ghost]

Work around for me was:

1) enable desktop emulation
2) client: open->close->reopen, this also fixes the status bar crashing sway and the screen dead zone created before that (not 100% reproducible) crash
3) switch to another workspace and back

[pavlus]

Have similar issue with IntelliJ IDEA, 1.3 (rc1, rc2) sometimes does not register clicks on pop-up windows (Settings, dialgos, etc)

[HoshiYamazaki]

Have similar issue, but I use two displays, and clicks are not working on only one.

Also disabling decoration etc. in winecfg causes winecfg jump like crazy (not sure if not XWayland bug). I tried that because I supposed that it will be maybe workaround.

[aqxa1]

I've had this issue with Proton in Steam. Switching to a different workspace then back generally works, however, if I disable my secondary monitor, the workaround no longer works. If I instead set the secondary monitor to blank (with dpms off) it works again, so presumably something breaks in the switch from multi-monitor to (temporary) single monitor config.

[biwhite]

Similar issue for me.
Wine app such as winecfg or wine steam game running under proton or running under wine manually, after it opens no input being received.
Full screen wine app shows decorated mouse moving around but no clicks.
No keyboard input working.
winecfg window doesn't show any mouse or accept keyboard input. No workaround found for me yet.
Running app with virtual desktop appending '/desktop 1024x768' to the command changes behaviour to no mouse tracking, decorated or otherwise!

[aqxa1]

Okay, so in my case, the problem only occurs with some games, all of which seem to be using hardware cursors (but it doesn't affect all games with hardware cursors):

Broken:

• CLANNAD
• The Witcher 3

Works:

• The Witcher - Enhanced Edition
• Kingdom Come: Deliverance

I suspect my issue is different. From memory, I do remember the more severe issue occurring in the past (that can't be recovered from by switching workspaces). I'm currently using an all git Wayland stack, so the more severe issue may already be fixed.

EDIT: Okay so The Witcher 3 functions properly without the workspace trick, if I launch from a single monitor configuration. CLANNAD also initially works with this tactic, but if you try and close the game, a dialog window pops over the main game, which can't be clicked. Once this occurs, you can't regain cursor access (and the workspace trick seems to only work with multiple outputs active, even if the switch is between two workspaces of the same output). The cursor also briefly shifts back to the non-hardware cursor when ever you click something in CLANNAD (which doesn't occur with the workspace switch workaround). Strange bug.

[Allyriadil]

For me it happens when I run two applications in a WINE prefix. It works perfectly on Xorg but on wayland the second application doesn't accept any mouseclicks, the mouse also seems to go through the application.

[fuzunspm]

if i set capture mouse in winecfg it works but i also need to emulate virtual desktop otherwise most wine applications can't create a window on sway

[fauu]

I have a similar issue. One of the earlier comments here helped me discover that in my case it's somehow related to multiple displays. In sway config I have my laptop display LVDS-1 centered above my external display HDMI-A-1:

output LVDS-1 position 157,0
output HDMI-A-1 position 0,768

In this default state wine GUI applications work correctly. Now however, when I turn off the laptop display:

swaymsg "output LVDS-1 toggle"

and launch winecfg, the window displays correctly, but the cursor disappears as soon as it enters the window, and no mouse interaction is possible. Except for when I press my Mod key and start dragging the window — in that case the window moves correctly, and the dragging cursor is visible for as long as I'm moving the window.

If I toggle the output again to turn it on, and relaunch winecfg, then it works properly again.

I can sometimes get it to work properly even with LVDS-1 toggled off by relaunching winecfg after toggling LVDS-1 twice.

It also seems to work properly when the remaining output is the top one, meaning two scenarios: 1) when I toggle off HDMI-A-1 and launch winecfg on LVDS-1, and 2) when I swap the displays in terms of y position so that HDMI-A-1 is on top, and then proceed with the default scenario (toggle off LVDS-1 and launch winecfg).

[aqxa1]

Tomb Raider: Legend (7000) is another game with click registering issues. In this case, setting virtual desktop mode worked around the problem.

[spikecodes]

Running Rocket League with Legendary gives this problem too :/ no mouse clicking works.

[spikecodes]

Not sure what is different but I have updated my system since then and Rocket League runs flawlessly on Sway now!

[WhyNotHugo]

Having this same issue on sway 1.5.1 on Arch. Using wine-staging 5.21.

Even winecfg picks up no mouse events nor keyboard events. My sway config is here.

When opening winecfg, sway logs this:

Nov 14 12:55:45 victory sway[608]: 00:04:48.431 [ERROR] [xwayland/xwm.c:1398] xcb error: op ChangeProperty (no minor), code Window (no extension), sequence 1885, value 10485763

[GorrillaRibs]

Also having this issue on sway 1.5.1 and wlroots 0.12 on arch, but only on one display - I have 2 screens (laptop built-in @ 1920x1080) and external HDMI @ 3440x1440) and wine works fine on the built in display (eDP-1) but not on the external, regardless of which display its launched on.

my display config is:

output eDP-1 subpixel none
output HDMI-A-1 subpixel none
output eDP-1 pos 0,0
output HDMI-A-1 pos 0,-1440

it also seems to work if I disable the internal screen and then start wine, so it seems related to having multiple displays? Is only one of them passed to xwayland? (so only coordinates on that display are valid?) Does anyone have any advice on how to begin debugging this?

EDIT:

Actually this seems to apply to all xwayland programs - xcalc for example only accepts mouse input on the internal display, but not the external, so at least on my system the issue isn't limited to wine.

[Emantor]

Also having this issue on sway 1.5.1 and wlroots 0.12 on arch, but only on one display - I have 2 screens (laptop built-in @ 1920x1080) and external HDMI @ 3440x1440) and wine works fine on the built in display (eDP-1) but not on the external, regardless of which display its launched on.

my display config is:

output eDP-1 subpixel none
output HDMI-A-1 subpixel none
output eDP-1 pos 0,0
output HDMI-A-1 pos 0,-1440

it also seems to work if I disable the internal screen and then start wine, so it seems related to having multiple displays? Is only one of them passed to xwayland? (so only coordinates on that display are valid?) Does anyone have any advice on how to begin debugging this?

EDIT:

Actually this seems to apply to all xwayland programs - xcalc for example only accepts mouse input on the internal display, but not the external, so at least on my system the issue isn't limited to wine.

Negative coordinates are not supported by Xwayland, see this issue on the xwayland bug tracker.

Edit: Looking at the issue again this could be fixed on Xwayland master, however the fix is not contained in the latest 1.20.10 release.

[GorrillaRibs]

ah, duh - that makes sense. The issue seems fixed for me when I fixed up my display config without negative coordinates, tested with xcalculator and winecfg.

Thanks!

[sloonz]

Same issue, easy to reproduce.

First, configuration. I have an external display configuration on my laptop :

set $left_output HDMI-A-1
set $right_output eDP-1

output $left_output position 0,0 mode 1366x768
output $right_output position 1366,0 mode 1920x1080

The issue can only reproduced if the external display (here HDMI-A-1) is not plugged-in when sway starts ; the issue disappears as soon as I plug in the external display. So to summarize : the issue appears when a display is configured but not present.

As for the issue itself…

This is just running wine notepad, standard wine build without fancy patches (not even staging, pacman -S wine on archlinux). Obviously someone here (Sway ? Xwayland ? Wine itself ?) seems pretty confused by the geometry of the display. In this image, I right-clicked on the black area and the dropdown menu appeared on the left part of the screen.