Xwayland-satellite apps on niri, with a second monitor are unresponsive.

[jamesonBradfield]

specifically Discord isn't responding to clicks, Idk if this has something to do with the coordinate system on niri or what. If this seems to be a niri issue I will post it there.

I am running arch
and using the latest commit of xwayland-satellite.
if there is any logs I can share or more information, please don't hesitate to ask.

[Supreeeme]

I'm not able to reproduce this, it works fine for me. Are you sure you're on the latest commit? What's the position of the second monitor?

[M3t0r]

I've had problems with Audacity and Orca Slicer (and essentially all X apps) on niri a few months ago. Mouse inputs in the top right corner weren't send. I verified that with xev. That included mouse moves, clicks and the like.

I switched a few apps, e.g. I'm using WebCord instead of the official Discord app. And for the few X apps I still use, I start Xwayland myself and run Openbox in it. So I couldn't tell you which versions are affected or if it was fixed in the 0.5 release.

My multi-monitor setup:

$ niri msg outputs | grep -E 'Logical|Scale|Transform'
  Logical position: 1840, 2520
  Logical size: 1804x1203
  Scale: 1.25
  Transform: normal
  Logical position: 1080, 1080
  Logical size: 3440x1440
  Scale: 1
  Transform: normal
  Logical position: 1360, 0
  Logical size: 1920x1080
  Scale: 1
  Transform: normal
  Logical position: 0, 840
  Logical size: 1080x1920
  Scale: 1
  Transform: 270° counter-clockwise

[notpeelz]

I had this issue, but it was because I had my second monitor in the negative coordinate space (which X11 can't do).

[Serverator]

I had this issue, but it was because I had my second monitor in the negative coordinate space (which X11 can't do).

Can confirm. Just encountered the same exact issue, position on my second monitor had negative coordinates on niri, that's why xwayland apps didn't work.

[Supreeeme]

Note that this is a separate issue - negative output coordinates not working properly is #15

[Supreeeme]

Wait actually, I'm not sure what this is - I'll close it in favor of #15. If anyone has mouse issues with not related to negative output coordinates, see if #66 applies.