I was having Vulkan\/Wine interaction issues when I had a minute to play a game the other night and flipped my big laptop (which has Intel\/AMD Polaris12 dual graphics, both running the Mesa stack since AMD dropped Polaris support in amdvlk in the 2023.Q4 release) into a Plasma Wayland session (v5.27) to see if it helped. It did – making it the very first thing I’ve encountered that worked in Wayland and not X – so I’m rolling with the Plasma Wayland session for a couple days to see how things are. I have a little machine I’ve been playing with Hyprland on to check out the Wayland situation, and it’s been closing from “Linux 20 years ago” to “Linux 5 years ago” in terms of brokenness, so it seems plausible that one of the big two would be tolerable now.<\/p>\n\n\n\n
I’m totally onboard that xf86->xorg is an unmaintainable mess for both legacy-codebase and design from a different era reasons, and it would be nice to start with something built on assumptions that match modern reality, but uh\u2026 over a decade in, Wayland is just getting to be less of a “almost<\/em> a tech demo” and more of an “almost there.” If the devs can shut up about some bikeshedding that obstructs common use cases now over concerns about theoretical security issues or compatibility with yet-unimagined future interface models and implement widely-accepted solutions to the last few basic-fucking-features, it might actually matter before it too starts to exhibit wrong ancient assumptions and gets replaced, but it looks like they’ve missed the bus on a couple of those necessary standardizations.<\/p>\n\n\n\n Things I use regularly that are currently broken in KDE’s Plasma Wayland session in Nov. 2023:<\/p>\n\n\n\n The whole situation is silly. It’s a gigantic shell-game of trying to outsource the solutions to problems everyone already knew needed to be solved consistently<\/em> because the ICCM and EWMH stuff for X represented decades of effort to do so, by the people best situated to actually solve the problems at the time when they could be solved in a general way. <\/p>\n\n\n\n I sometimes get the feeling reading the bug trackers that many of the Wayland people are building a display layer suitable for infotainment systems, kiosks, signage, and that sort of thing, and desktop functionality is an unfortunate extra thing some people are trying to force on them – which, financially, may be the case. <\/p>\n","protected":false},"excerpt":{"rendered":" I was having Vulkan\/Wine interaction issues when I had a minute to play a game the other night and flipped my big laptop (which has Intel\/AMD Polaris12 dual graphics, both running the Mesa stack since AMD dropped Polaris support in … Continue reading \n
\n
\n
\n