nwggrid broken with multiple displays

[abb128]

I have a 1920x1200 monitor rotated to portrait orientation (1200x1920) and a regular 1920x1080 monitor on the right side. My display setup in sway config looks like this:

output DP-2 resolution 1920x1200 position 0,0 transform 270
output DP-3 resolution 1920x1080 position 1200,320

Opening nwggrid (or nwgbar) on my DP-3 display opens a 1200x1920 application picker on my 1920x1080 display. This leads to the top and bottom part being out of bounds of the display, meanwhile the left and right sides are not blocked by the transparent window. If opened on my portrait monitor instead, it functions correctly.

I could try to make a screenshot if needed, if I can figure out how to take a screenshot using sway..

[nwg-piotr]

Seems to look perfectly well on my vertical display (DP-1),

output DP-1 resolution 1920x1200 position 0,0 transform 270
output eDP-1 resolution 1920x1080 position 1200,840
output HDMI-A-1 resolution 1920x1080@60Hz position 3120,840

as well as on both horizontal ones.

Which WM do you use?

[abb128]

I'm using sway version 1.4 from apt on Pop OS 20.04 LTS, default sway config except using nwggrid and my monitor setup. I noticed the latest sway is 1.6.1 so I'm wondering if that might actually be it, since the latest one Ubuntu 20.04 provides is 1.4

Here's a screenshot of how it looks when I open it:

[nwg-piotr]

If you want my advice: try building sway from Master following this guide. The latest release sucks on my hybrid AMD laptop, so I use the last tag that worked decently for me.

[edit] Just tried the latest Master, and Chromium with ozone flags still crashes. :/

[abb128]

Some dependencies and packages like wayland-server on Ubuntu 20.04 seem to be too out of date to build sway and wlroots from master or from 1.6.1 release, so I don't think I can do it. It's probably a non-issue on the latest release anyway seeing as it works for you though.

[nwg-piotr]

Well, I'm no longer a developer in this project, as I gave up on C++. We need @Siborgium's opinion. You could try the counterpart I wrote in Go, but I have no idea if it's going to build on Debian.

[Siborgium]

Some dependencies and packages like wayland-server on Ubuntu 20.04 seem to be too out of date to build sway and wlroots from master or from 1.6.1 release,

You could build wayland-server along with the other dependencies too, though at this point using Ubuntu is pointless.

You could try and build nwg-launchers with -Dlayer-shell=disabled, that'd force Sway IPC mechanism instead of layer-shell, which could potentially resolve the issue. I wonder if it's our code that is wrong or it's older Sway version having troubles -- but again, our code simply binds to the screen edges, there are no coordinates and such.

It could also be gtk-layer-shell problem, which is outdated on Ubuntu 20.04 -- uninstall libgtk-layer-shell-dev AND build with -Dlayer-shell=enabled to build it as a subproject.

Unfortunately, I lack the display suitable to set to portrait orientation, so I can't test the case properly.

[abb128]

I tried the Go version on Pop and it didn't seem to wanna build. I also tried messing around with the layer-shell and neither of the two attempts changed anything.

I ended up installing Arch and both nwg-launchers and nwg-drawer seem to work fine now without the issue, even on wayfire.

[nwg-piotr]

I ended up installing Arch

This is always the ultimate solution. :smile: