Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XWayland windows don't receive mouse events if output is above other output #3034

Closed
philipflohr opened this issue Oct 30, 2018 · 4 comments
Closed

Comments

@philipflohr
Copy link

I have the following output configuration:

output eDP-1 scale 1.25
output eDP-1 pos 0 0 res 2560x1440
output DP-5 pos 0 -1080 res 1920x1080

On eDP-1 everything works as expected but there are problems on the other screen.
While all native wayland windows receive all inputs correctly, windows using xwayland do not receive mouse events like click and scroll.

once i set a left to right orientation (swaymsg output DP-5 pos 1920 0 res 1920x1080) everything works as expected

sway version 1.0-beta.1-108-gb90af335 (Oct 30 2018, branch 'master')
sway log: https://nextcloud.voodoomail.de/s/XRpaa6ycMN3LBKs

@emersion
Copy link
Member

emersion commented Oct 30, 2018

Overlapping outputs are not expected to work with Xwayland yet.

See #1666

@philipflohr philipflohr changed the title XWayland windows don't receive keyboard inputs if output is above other output XWayland windows don't receive mouse events if output is above other output Oct 30, 2018
@ianyfan
Copy link
Contributor

ianyfan commented Oct 30, 2018

Duplicate of swaywm/wlroots#958

@ianyfan ianyfan marked this as a duplicate of swaywm/wlroots#958 Oct 30, 2018
@ianyfan ianyfan closed this as completed Oct 30, 2018
@progandy
Copy link
Contributor

Can you set DP-5 to 0/0 and eDP-1 to position 0/1080 instead?

output eDP-1 scale 1.25
output eDP-1 pos 0 1080 res 2560x1440
output DP-5 pos 0 0 res 1920x1080

@fruitloop
Copy link

fruitloop commented Jan 17, 2019

Hi, I've got the same problem.

yes, setting the displays with positive positions does work.
however that means that now my external monitor (which is not always connected)
is the "main" monitor position wise and my internal monitor (Surface Go) is the one that
has an offset.

The problem seems to be the negative offset though.

Edit: my bad, just noticed the other issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

5 participants