750
you are viewing a single comment's thread
view the rest of the comments
[-] TideElysium@lemmy.world 17 points 4 days ago

Plasma does solve some problems itself but: screen recording, global hotkeys, clipboard management to name a few. They all have "solutions", it just sucks to be made to jump through hoops sometimes. There's a lot of desirable things in x11 that while crusty worked well, like xrandr and being able to script monitor config. It is niche! But if you used it, it's annoying to be forced off it

Here is a (biased but decent enough) list https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277

[-] wltr@discuss.tchncs.de 17 points 4 days ago* (last edited 4 days ago)

What exactly about these three? I’m really curious to understand.

I never used X knowingly: by the time I’ve started understanding Linux more or so, I’ve been on Wayland already. So, in a way, I can say I never used X, even being on Linux on and off for almost two decades.

Say, screen recording. It just works for me on Sway (I use wf-recorder) and it just works on Gnome. I have never thought of it as being broken. I could have missed anything though. Not something I use very often.

What global hotkeys do you mean here? Mine work in all apps. So, I assume they’re global. Or is it something different?

Not sure about clipboard: it just works too. There’s this ‘middle mouse click’ shit that I hate, as I accidentally paste some unnecessary information into, say, email. Upon scrolling, and accidentally pressing the scroll wheel. I’d love to disable it globally, but it just there, working. I assume that’s a feature for some folks, but I passionately hate it and have no use for.

[-] kuberoot@discuss.tchncs.de 15 points 4 days ago* (last edited 4 days ago)

Not OP, but wanted to address some questions:

EDIT: I just realized in the linked gist they're basically complaining Wayland doesn't have "builtin" support for things like keylogging, and generally uses portals for features. Yes, some DEs may choose not to implement specific features, and apparently that's Wayland's fault?

Screen recording works, I think it's only existing X software that doesn't. In my experience there's still some jank and limitations that might or might not be related to Wayland. After a few days of runtime with periods of sleep mode, screencasting through the portal seems to break until pipewire is restarted. I don't know if there's a way to capture an application and its audio automatically.

Global hotkeys refer to hotkeys that can be activated while the application isn't focused. Wayland has global hotkeys, but some people don't like the implementation and refuse to use it. OBS, for example, has an unofficial plugin implementing them, but the actual project refuses because they can't display and set hotkeys from their own setting menu, and have no good way to support multiple profiles with separate bindings.

I also don't know what they mean by clipboard management, but I do know there's some jank. As a weirdly specific example, when playing Minecraft with patched glfw with native Wayland support, pasting into chat doesn't work correctly, it seems to always paste the text that was in the clipboard when the game was opened, and not update when copying things from outside the game (but I think it works when copying something inside the game itself). I don't know if this is an actual Wayland issue, or a case of a broken client implementation, but the lack of software support is still a type of issue.

[-] FishFace@piefed.social 6 points 3 days ago

Yes, some DEs may choose not to implement specific features, and apparently that’s Wayland’s fault?

Kind of. For a long time a mainstream setup like Gnome on Wayland lacked features because they weren't yet incorporated into Gnome. But more generally, Wayland deliberately didn't implement a bunch of features that X had, or had external things that accomplished. That pushed the responsibility for implementing it onto each and every window manager. Smaller WMs that would have had all of those features for free on X now have a big burden to achieve the same bar on Wayland, and so many don't manage it. That's due to the choices that went into Wayland.

[-] kuberoot@discuss.tchncs.de 3 points 3 days ago

AFAIK all of Wayland is pushed onto the WM, because Wayland is just a set of protocols. It has some libraries, I think official ones, to help with implementing those protocols, but ultimately that's a design choice that also means WMs don't have to have those features, especially relevant for atypical WMs where the concept of windows might not exist, displays might not be two dimensional, input might be neither a mouse nor a keyboard.

To my understanding, if somebody wants an unusual setup, on Wayland they might need to figure out implementation of protocols for their ideas. On X11, they might not be able to do anything because it enforces certain ideas of how a graphical environment works.

That's simply not a failure of Wayland, it's a tradeoff they chose, and it seems dishonest when people say things "don't work on Wayland" because the responsibility is deliberately moved to a portal or something.

[-] TideElysium@lemmy.world 2 points 3 days ago

It is a trade-off they chose yeah, but for people on anything but KDE (really, though hyprland sway and gnome do most too) they've forced them to either catch up or die. I don't know that that's indicative of a great replacement project. For reference, I use Wayland & KDE fine, but if x11 had HDR I'd switch back to my i3 setup.

[-] kuberoot@discuss.tchncs.de 1 points 3 days ago

they've forced them to either catch up or die

I think the "die" part is a bit of an overexaggeration, it's true that they need to implement protocols if they want the features those protocols exist to provide, but the X way seems to have caused more problems in the long run. Niche projects will attract people who want that niche, hopefully despite missing features, and some people who can help implement those features.

It's worth noting that DEs can do things like use XDG portal implementations from another DE, I think it might've been Niri that does that.

if x11 had HDR I'd switch back to my i3 setup.

Then I can wish you that you get a worthy compositor/DE/whatever to replace i3 on Wayland. Either that or i3 somehow getting a Wayland implementation. I'm lucky in that I was comfortable on plasma with X, so switching to Wayland was mostly painless, though there were significantly more issues back then.

[-] TideElysium@lemmy.world 2 points 2 days ago

It is an exaggeration in that Wayland isn't outright killing x, but a lot of the talk surrounding both is that it's supposed to. I'm not going to defend the state of X and the problems it's caused because it's a fugly old project, just when you look at something like pulse -> pipe wire, there wasn't a big paradigm shift with it. It did the same job and better (to my knowledge!).

I didn't know that DEs could use others portal implementations, that seems neat?

Yeah it's the specifics of that that's the issue for me though. I tried hyprland and many things are really cool about it but lots of things just break, and maintaining separate configs for what feels like core features was annoying. Then you get things like HDR performing differently between it and plasma, something that I'd hoped Wayland would just own. I'll probably try niri and sway at some point, they both look cool

[-] kuberoot@discuss.tchncs.de 1 points 2 days ago

It is an exaggeration in that Wayland isn't outright killing x, but a lot of the talk surrounding both is that it's supposed to.

I interpreted that killing to refer to niche DEs rather than X, and while that isn't happening yet, yeah, I imagine a future where software stops supporting X entirely.

maintaining separate configs for what feels like core features was annoying

That part specifically sounds like the fault of the specific DE? Wayland might be split into protocols, and some functionality might be handled by the portal, but ultimately it's the compositor handling how it's all implemented, and the configuration could well all be in one place.

[-] TideElysium@lemmy.world 2 points 1 day ago

Yeah, I guess I see the two as linked. I don't think i3 is going to reimplement itself to stay available, nor would I expect them to

Also yes I phrased myself very badly there: it's a decision hyprland has made, where there are separate first party packages for core functionality that need their own configs. I'm sure it's to allow for your own drop in replacements it just felt clunky to me. I don't really have an issue with Wayland's actual composition beyond I get lower input latency on X (which seems to put me in the minority), but they are both substantially lower and nicer to use than windows so I don't care

[-] kuberoot@discuss.tchncs.de 1 points 1 day ago

Regarding input latency, last I saw some testing suggests mixed results on performance, with X still being more consistent with slightly better performance overall, so it might still be winning in that regard. I haven't tested it myself, but also didn't notice problems when switching to Wayland, so maybe I was lucky again.

[-] TideElysium@lemmy.world 2 points 14 hours ago

Again, it's within the realms of not mattering to me since both beat Windows, but it would be another thing I would welcome back. And for a lot of people, Wayland is more responsive

[-] mittorn@masturbated.one 0 points 3 days ago

@kuberoot @FishFace
Yes, but this makes wayland good for everyrhing except normal desktop. It's pretty good for VR/spatial desktops (where we do not want to deal with 2d coordinates), for some embedded setups where we only need to manage output to multiple displays or draw some overlays. But on normal desktop we need draw UI (wayland cannot do drawing at all!), position windows (limited), capture screen (actually done outside of wayland???) warp mouse (broken?), inject events for automation (yes, ei exist, but looks like very optional...), set screen resolution and layout (actually made different in every implementation?), manage clipboard (still depends on compositor?)
So, wayland actually does almost nothing for desktop :(

[-] kuberoot@discuss.tchncs.de 1 points 3 days ago

Sure, Wayland "actually does nothing", if you only and specifically mean things that are built into Wayland and only Wayland, the core project, itself.

Meanwhile, as an actual user of a normal desktop on Wayland I can capture the screen, mouse warping works, I have an autoclicker, my screens have resolution, layout and scaling set, my clipboard and clipboard history work (with individual exceotions, accessible from a command line tool too). Hell, I even have HDR on because I found out it just works nowadays, even though my display is probably ass for HDR, but SDR content seems to look no different with it enabled.

Window positioning is something that's not finished, because the developers are trying to figure out a good way to do it and are taking a long time.

Not sure what you mean by "drawing", is it some pedantic bullshit again about how Wayland itself doesn't dictate how you render stuff? Because I certainly have all kinds of GUIs running on my computer.

So if you want a system that is hardcoded to only support things that are common nowadays and that will start breaking down in the next 10 years as things change and the code becomes impossible to maintain, maybe go contribute to XLibre. I will meanwhile patiently enjoy Wayland getting better, even if it might take years, because I have hope that this approach will work.

[-] Wildmimic@anarchist.nexus 2 points 3 days ago

Regarding the clipboard - there are practically 2 clipboards, i can paste different things based on whether i used ctrl-c/v or selecting text with the mouse and middle-clicking. I often fall into this trap, anf i would prefer it to be unified.

[-] j3tt@lemmy.world 2 points 3 days ago

I recently noticed, that on Fedora Silverblue with Gnome, middle-click-paste does not work. Not sure, how and why it has beend disabled. I am glad it still works on Debian stable with an older version of Gnome.

[-] wltr@discuss.tchncs.de 1 points 3 days ago

Thanks for letting me know! I hope there would be some middle ground for this feature at some point, with reliable ways of disabling / enabling it. Personally, I believe that it doesn’t need to be enabled by default, as average users don’t need it. And those who need it wouldn’t have any issues with enabling it once. (Assuming it’s reliable.) But I don’t mind otherwise, if I could just disable it. For some reason, I couldn’t.

[-] Azzu@leminal.space 6 points 3 days ago

I guess those 3 are solved by KDE then. I only know Wayland through KDE and the 3 work perfectly fine for me, I didn't even have to think about them when I used them.

[-] TideElysium@lemmy.world 3 points 3 days ago

Try copying to your clipboard in vim without a plugin, or try starting to record without a (very shaky) OBS plugin. I'm not saying Wayland broke into my house and burgled me but their decision to create everything as distant APIs means that all the smaller DE/WMs have to implement it in a certain way. KDE does a great job of this, but I now have to choose between using HDR on KDE and having things that used to work fineon something like i3

[-] Postimo@lemmy.zip 2 points 3 days ago

I feel like it's all made more frustrating to me too because it seems so many of the problems are in service of answering a threat vector I just don't give a shit about.

[-] TideElysium@lemmy.world 2 points 3 days ago

Yeah.. it almost makes me wish for an "unsafe mode" where Wayland allows all the things it didn't allow for the sake of security, but given there was a way to run x11 rootless and many people didn't, I'm guessing that would just make everyone use it in that way However, the security stuff feels so hypothetical to me right now. I'm on Wayland purely because it supports HDR, I can't easily cite a single other benefit for myself

[-] WhyJiffie@sh.itjust.works 1 points 3 days ago

I can record my wayland session in OBS without any plugins. here it was working fine even in plasma 5

[-] TideElysium@lemmy.world 2 points 3 days ago

Sorry, I meant trigger it with a hot key. Thanks to pipewire, the actual screen recording is in a pretty good place now, providing the permission stuff is implemented correctly But because OBS hasn't registered its capacity for hotkeys via Wayland, they don't work globally. I'm sure it's not a crazy addition to the codebase, it just feels like a step back to me

this post was submitted on 17 Nov 2026
750 points (97.2% liked)

linuxmemes

33506 readers
819 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry of any kind will not be tolerated. This is an LGBTQ+-friendly community -- if that is a problem for you, you should leave.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves / tolerates / hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 3 years ago
    MODERATORS