this post was submitted on 10 Jun 2025
122 points (98.4% liked)

Linux

7839 readers
238 users here now

A community for everything relating to the GNU/Linux operating system

Also check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Samueru_sama@programming.dev -1 points 2 days ago

I bought an AMD gpu to use sway, I feel like the fuckers owe me 50 usd now which is what I payed for the gpu.

https://github.com/swaywm/sway/issues/8000

https://github.com/swaywm/sway/issues/8001

https://github.com/swaywm/sway/issues/8002

https://github.com/swaywm/sway/issues/8191

And it's devs are not willing to fix the most basic issues like correctly handing a fucking environment variable lmao

https://github.com/swaywm/sway/pull/7380#issuecomment-2453356422

Not to mention I have a different issue that I haven't even bothered to report because I already know won't be implemented:

I have 3 displays that right now I use xrandr to merge the 3 displays into one, this is not possible in any wayland compositor today, the closest thing I found was someone suggesting to use gamescope to make a window with the resolution of the 3 displays but that's a hack and doesn't work for me because I need the displays to be merged, not just span a single window across them.

There is also no universal xdotool or similar in wayland to query info about windows, so you have to learn to use the CLI tool provided by each DE/WM and then handle the data, which in the case of sway it is json formatted.

So what used to be a simple xdotool <args> | grep became needlessly overcomplicated and different for each wayland DE/WM.